Public report of Elders/Cronus, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 01:20 UTC · Survey ID cd_bbd2d6622a1e4521bf745604b27ab327

Elders/Cronus

Measured 22 October 2026, 01:17 UTC, at code version adbc00b

Code coverage: not measuredTest distribution: not measuredSupply-chain provenance & signing: not measured

Code coverage is not measured: No coverage collector is wired up.

Test distribution is not measured: Tests outside the analyzed solution.

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 41out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 7 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Security and Compliance 89 Strong Architecture 83 Adequate Domain Modelling 83 Strong Performance 73 Strong Production Readiness 56 Adequate Code Health 35 Weak Maturity 28 Weak

A small codebase: 12,337 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Maturity, 28

Findings by how serious they are

325 critical 192 serious 133 minor

3 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 01:17 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

73of 79 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
633of 650 findings point to an exact file and line, so you can open each one in the code. The other 17 concern the repository as a whole, such as missing documentation.
79dimensions across 7 lenses, read from 12,337 lines of product code in 6 projects.
Chapters

Executive summary

Elders/Cronus scores 41 out of 100 and is rated Weak, while five of its seven lenses score higher still: Security and Compliance at 89, Domain Modelling at 83 and Performance at 73, all rated Strong, and Architecture at 83 and Production Readiness at 56, both rated Adequate.

The score is lower than those five because the weakest lens counts most, and here that is Maturity, which scores 28 and is rated Weak. Its Knowledge Freshness dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 64 Orphaned file finding(s) in Knowledge Freshness and to record your significant design decisions, and if Maturity rose to 70, the score would rise from 41 to about 52.

325 findings are critical: 318 in Explicit Debt, three in Static Analysis (SAST), two in Dependency Vulnerabilities and two in Project dependency cycles.

Watchdog couldn't measure Dependency Hygiene and IL Efficiency in this code, so those dimensions are left out of the score. The product code is 12,337 lines, which would take an estimated 0.1 person-years, around €21,000, to rebuild.

Code Health 35 Weak, capped by Explicit Debt and Nullable reference types Architecture 83 Adequate, capped by Project Cohesion Maturity 28 Weak, capped by Knowledge Freshness, Architecture documentation and Documentation accuracy Production Readiness 56 Adequate, capped by Library API & versioning Security and Compliance 89 Strong Domain Modelling 83 Strong Performance 73 Strong

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Maturity 28 · counts for 46%Code Health 35 · counts for 25%Production Readiness 56 · counts for 14%Performance 73 · counts for 8%Domain Modelling 83 · counts for 4%Architecture 83 · counts for 2%Security and Compliance 89 · counts for 1%

If Maturity rose from 28 to 70, the lowest score rated Strong, the score would rise from 41 to about 52.

Code composition: what the lines of code are
Business logic 20%Supporting code 54%Tests 26%
New since the last survey: 72 findings

These 72 critical or serious findings weren't in the previous survey, on 7 October 2026.

  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Cluster/Job/CronusJob.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/EventStore/Players/PublicEventsPlayer.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/MessageProcessing/AggregateCommitPublisher.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Migrations/AggregateCommitMigrationWorkflow.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Migrations/CronusMigrator.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Migrations/MigrationWorkflowBase.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Projections/ProjectionRepository.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs
  • Explicit Debt · EmptyCatchBlock src/Elders.Cronus/Workflow/ExceptionEaterWorkflow.cs
  • Explicit Debt · Dead code: OneHour src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs
  • Explicit Debt · Dead code: EightHours src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs
  • Explicit Debt · Dead code: RealyLongTime src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs
  • Explicit Debt · Dead code: DiagnosticsUnhandledExceptionKey src/Elders.Cronus/Workflow/DiagnosticsWorkflow.cs
  • Explicit Debt · Dead code: LoadAggregateCommitsAsync src/Elders.Cronus.Tests/InMemory/InMemoryEventStorePlayer.cs
  • Supply-chain Provenance & Signing · REDACTED
  • Cancellation propagation · Async method without CancellationToken: OnAppendAsync src/Elders.Cronus/EventStore/CronusAggregateCommitInterceptor.cs
  • Cancellation propagation · Async method without CancellationToken: OnAppendingAsync src/Elders.Cronus/EventStore/CronusAggregateCommitInterceptor.cs
  • Cancellation propagation · Async method without CancellationToken: AppendAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
  • Cancellation propagation · Async method without CancellationToken: AppendAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
  • Cancellation propagation · Async method without CancellationToken: DeleteAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
  • Cancellation propagation · Async method without CancellationToken: LoadAggregateEventRaw src/Elders.Cronus/EventStore/CronusEventStore.cs
  • Cancellation propagation · Async method without CancellationToken: LoadAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
  • Cancellation propagation · Async method without CancellationToken: LoadWithPagingAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
  • Cancellation propagation · Async method without CancellationToken: IndexAsync src/Elders.Cronus/EventStore/Index/ProjectionIndex.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs
  • Cancellation propagation · Async method without CancellationToken: StartAsync src/Elders.Cronus/Hosting/CronusHost.cs
  • Cancellation propagation · Async method without CancellationToken: StopAsync src/Elders.Cronus/Hosting/CronusHost.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/DynamicMessageHandle.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/DynamicMessageIndex.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/MessageHandleWorkflow.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/CopyEventStore.cs
  • Cancellation propagation · Async method without CancellationToken: MigrateAsync src/Elders.Cronus/Migrations/CronusMigrator.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/ValidateEventStore.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync src/Elders.Cronus/Projections/ProjectionRepository.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync src/Elders.Cronus/Projections/ProjectionRepository.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync src/Elders.Cronus/Projections/ProjectionRepositoryWithFallback.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync src/Elders.Cronus/Projections/ProjectionRepositoryWithFallback.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Cluster/Job/CronusJob.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/EventStore/Players/PublicEventsPlayer.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/MessageProcessing/AggregateCommitPublisher.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Migrations/AggregateCommitMigrationWorkflow.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Migrations/CronusMigrator.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Migrations/MigrationWorkflowBase.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Projections/ProjectionRepository.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs
  • Exception handling · Swallowed exception (empty catch) src/Elders.Cronus/Workflow/ExceptionEaterWorkflow.cs
  • Async & latency hygiene · Sync-over-async blocking src/Elders.Cronus/Hosting/CronusHost.cs
  • Async & latency hygiene · Sync-over-async blocking src/Elders.Cronus/Hosting/ProjectionsStartup.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/AutoUpdates/AutoUpdateSaga.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/RetryPolicy.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/RetryPolicy.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/CronusHost.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeatService.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/Migrations/CopyEventStore.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/Migrations/ValidateEventStore.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs
  • Async & latency hygiene · Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 4 findings

These 4 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.

  • Coupling · Off the main sequence: Elders.Cronus(net8.0)
  • Supply-chain Provenance & Signing REDACTED
  • Exception handling · Swallowed exception (caught, then discarded) src/Elders.Cronus/Projections/ProjectionVersions.cs
  • Exception handling · Swallowed exception (caught, then discarded) src/Elders.Cronus/Projections/Versioning/MarkupInterfaceProjectionVersioningPolicy.cs
Rebuild cost: about €21,000 · Estimate
Cost to rebuild€7,000 to €35,000, for 117 to 373 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemHigh, 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 41. 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.
SizeSmall: 12,337 lines of product code, of which 40% is declarations and boilerplate, 33% straight logic and 27% logic with branches
Comment linesThe estimate prices 11,306 lines. Comment lines count towards the size of 12,337 lines but aren't priced as work.

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with ProjectionRepository.cs, PublisherBase.cs, RetryPolicy.cs.
Raises the score by about 9 points · Medium effort · Knowledge Freshness
2
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.
Raises the score by about 6 points · Medium effort · Architecture documentation
3
Reconcile the README with reality: docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`; docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`; docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`; docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`; docs/getting-started/quick-start/setup.md installs the package `Cronus` (`dotnet add package Cronus`), but no project or props file references it.
Raises the score by about 6 points · Medium effort · Documentation accuracy

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €21,000 to build again, about 0.1 person-years of work. Its weakest lens is Maturity, at 28 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 64 Orphaned file finding(s) in Knowledge Freshness. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for medium effort, because it clears the 64 Knowledge Freshness findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch Elders.Cronus Cronus

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

33 modules, with 86 dependencies between them. 2 loops run through 18 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Elders.Cronus.AspNetCore.Exceptions2 Elders.Cronus.Hosting3 Elders.Cronus.Projections.Cassandra.EventSourcing4 Elders.Cronus.Userfull5 Elders.Cronus.Workflow6 System7 Elders.Cronus.AtomicAction8 Elders.Cronus.EventStore.Players9 Elders.Cronus.FaultHandling10 Elders.Cronus.IntegrityValidation11 Elders.Cronus.Migrations12 Elders.Cronus.Projections.Cassandra13 Elders.Cronus.Discoveries14 Elders.Cronus.FaultHandling.Strategies15 Elders.Cronus.Projections.Rebuilding16 Elders.Cronus.Multitenancy17 Elders.Cronus.Projections.Versioning18 Elders.Cronus.Projections19 Elders.Cronus.EventStore.Index20 Elders.Cronus.EventStore21 Elders.Cronus.EventStore.Integrity22 Elders.Cronus.MessageProcessing23 Elders.Cronus.Cluster.Job24 Elders.Cronus25 Elders.Cronus.Cluster.Job.InMemory26 Elders.Cronus.DangerZone27 Elders.Cronus.EventStore.AutoUpdater.Commands28 Elders.Cronus.EventStore.AutoUpdater.Events29 Elders.Cronus.EventStore.Index.Handlers30 Elders.Cronus.Hosting.Heartbeat31 Elders.Cronus.AutoUpdates32 Elders.Cronus.EventStore.AutoUpdater33 (global)
1 Elders.Cronus.AspNetCore.Exceptions
2 Elders.Cronus.Hosting
3 Elders.Cronus.Projections.Cassandra.EventSourcing
4 Elders.Cronus.Userfull
5 Elders.Cronus.Workflow
6 System
7 Elders.Cronus.AtomicAction2
8 Elders.Cronus.EventStore.Players1253
9 Elders.Cronus.FaultHandling2
10 Elders.Cronus.IntegrityValidation1
11 Elders.Cronus.Migrations3113
12 Elders.Cronus.Projections.Cassandra11
13 Elders.Cronus.Discoveries1221
14 Elders.Cronus.FaultHandling.Strategies6
15 Elders.Cronus.Projections.Rebuilding3416236117
16 Elders.Cronus.Multitenancy412
17 Elders.Cronus.Projections.Versioning1621142318
18 Elders.Cronus.Projections214125
19 Elders.Cronus.EventStore.Index61321116
20 Elders.Cronus.EventStore115
21 Elders.Cronus.EventStore.Integrity126
22 Elders.Cronus.MessageProcessing212411
23 Elders.Cronus.Cluster.Job11
24 Elders.Cronus11232411
25 Elders.Cronus.Cluster.Job.InMemory46
26 Elders.Cronus.DangerZone1
27 Elders.Cronus.EventStore.AutoUpdater.Commands44
28 Elders.Cronus.EventStore.AutoUpdater.Events55
29 Elders.Cronus.EventStore.Index.Handlers915
30 Elders.Cronus.Hosting.Heartbeat12
31 Elders.Cronus.AutoUpdates11
32 Elders.Cronus.EventStore.AutoUpdater1552
33 (global)1
Uses a module listed above itPart of a loopThe module itself
1 Elders.Cronus.AspNetCore.Exceptions2 Elders.Cronus.Hosting3 Elders.Cronus.Projections.Cassandra.EventSourcing4 Elders.Cronus.Userfull5 Elders.Cronus.Workflow6 System7 Elders.Cronus.AtomicAction8 Elders.Cronus.EventStore.Players9 Elders.Cronus.FaultHandling10 Elders.Cronus.IntegrityValidation11 Elders.Cronus.Migrations12 Elders.Cronus.Projections.Cassandra13 Elders.Cronus.Discoveries14 Elders.Cronus.FaultHandling.Strategies15 Elders.Cronus.Projections.Rebuilding16 Elders.Cronus.Multitenancy17 Elders.Cronus.Projections.Versioning18 Elders.Cronus.Projections19 Elders.Cronus.EventStore.Index20 Elders.Cronus.EventStore21 Elders.Cronus.EventStore.Integrity22 Elders.Cronus.MessageProcessing23 Elders.Cronus.Cluster.Job24 Elders.Cronus25 Elders.Cronus.Cluster.Job.InMemory26 Elders.Cronus.DangerZone27 Elders.Cronus.EventStore.AutoUpdater.Commands28 Elders.Cronus.EventStore.AutoUpdater.Events29 Elders.Cronus.EventStore.Index.Handlers30 Elders.Cronus.Hosting.Heartbeat31 Elders.Cronus.AutoUpdates32 Elders.Cronus.EventStore.AutoUpdater33 (global)Elders.Cronus.AspNetCore.Exceptions1Elders.Cronus.Hosting2Elders.Cronus.Projections.Cassandra.EventSourcing3Elders.Cronus.Userfull4Elders.Cronus.Workflow5System6Elders.Cronus.AtomicAction7Elders.Cronus.EventStore.Players8Elders.Cronus.FaultHandling9Elders.Cronus.IntegrityValidation10Elders.Cronus.Migrations11Elders.Cronus.Projections.Cassandra12Elders.Cronus.Discoveries13Elders.Cronus.FaultHandling.Strategies14Elders.Cronus.Projections.Rebuilding15Elders.Cronus.Multitenancy16Elders.Cronus.Projections.Versioning17Elders.Cronus.Projections18Elders.Cronus.EventStore.Index19Elders.Cronus.EventStore20Elders.Cronus.EventStore.Integrity21Elders.Cronus.MessageProcessing22Elders.Cronus.Cluster.Job23Elders.Cronus24Elders.Cronus.Cluster.Job.InMemory25Elders.Cronus.DangerZone26Elders.Cronus.EventStore.AutoUpdater.Commands27Elders.Cronus.EventStore.AutoUpdater.Events28Elders.Cronus.EventStore.Index.Handlers29Elders.Cronus.Hosting.Heartbeat30Elders.Cronus.AutoUpdates31Elders.Cronus.EventStore.AutoUpdater32(global)33212532131131112216341623611741216211423182141256132111611512621241111112324114614455915121115521

At a glance — Code Health · 35% · Weak · gated by D17, X5 ·

The Good
D1 · .NET / C# Cyclomatic Complexity 9.4 D2 · .NET / C# Cognitive Complexity 8.5 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 9.3 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0
The Bad
IC1 · Repo Incompleteness & stubs 6.9 X1 · Repo Async correctness 6.9 X18 · Repo Disposal-pattern correctness 5.2 X20 · Repo Mistyped argument guard 5.2 X4 · Repo Structured logging 6.8
The Ugly
D17 · .NET / C# Explicit Debt 0.0 X2 · Repo Cancellation propagation 4.8 X3 · Repo Exception handling 4.7 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 83% · Adequate · gated by D26 ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D27 · .NET / C# Navigability 8.4 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 8.9 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0
The Bad
AX2 · Repo Stateful singletons 5.9
The Ugly
D26 · .NET / C# Project Cohesion 3.3

At a glance — Maturity · 28% · Weak · gated by D34, M2, M4 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 10.0 D19 · .NET / C# Documentation Quality 9.0 D21 · .NET / C# Naming Consistency 8.0 D24 · .NET / C# Comment Value 8.4 M3 · Repo Folder & project structure 10.0
The Ugly
D34 · .NET / C# Knowledge Freshness 0.0 M1 · Repo Documentation (README) 4.7 M2 · Repo Architecture documentation 0.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 56% · Adequate · gated by P10 ·

The Good
D11 · .NET / C# Test Reliability 10.0 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 8.4 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 9.0 P6 · Repo Release Hygiene 10.0
The Bad
P4 · Repo Deployment & Rollback 5.0
The Ugly
P10 · Repo Library API & versioning 2.0 P3 · Repo Security & performance tooling 4.0

At a glance — Security · 89% · Strong ·

The Good
D28 · .NET / C# Secrets (history) 10.0 D30 · .NET / C# Dependency Vulnerabilities 8.6 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
D29 · .NET / C# Static Analysis (SAST) 6.0

At a glance — Domain Modelling · 83% · Strong ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 10.0 DM5 · Repo Encapsulated state 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 9.6
The Bad
DM11 · Repo Constructible invalid state 5.3

At a glance — Performance · 73% · Strong ·

The Good
PF1 · Repo Benchmark discipline 9.5
The Bad
PF2 · Repo Allocation hygiene 6.8 PF3 · Repo Async & latency hygiene 6.5

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection3High / Critical
A03:2025 — Software Supply Chain Failures3High / Critical

Roadmap

Begin by addressing the largest code quality gaps, specifically resolving the 64 orphaned files in Knowledge Freshness and the 305 write-only private fields in Explicit Debt. Next, establish architectural clarity by documenting significant design decisions in a dedicated ADR folder and correcting documentation inaccuracies to ensure the README aligns with the current codebase. Finally, clean up the remaining Explicit Debt by removing empty catch blocks to improve error handling robustness.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with ProjectionRepository.cs, PublisherBase.cs, RetryPolicy.cs.+9.0 ptsMediumKnowledge Freshness
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+6.3 ptsMediumArchitecture documentation
Reconcile the README with reality: docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`; docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`; docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`; docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`; docs/getting-started/quick-start/setup.md installs the package `Cronus` (`dotnet add package Cronus`), but no project or props file references it.+6.3 ptsMediumDocumentation accuracy
Resolve the 13 EmptyCatchBlock finding(s) in Explicit Debt — start with ProgressTracker.cs (2), CronusJob.cs, PublicEventsPlayer.cs.+5.0 ptsMediumExplicit Debt
Resolve the 1 redundant comment finding(s) in Comment Value — start with CronusPublisher.cs.+2.4 ptsLowComment Value
Resolve the 305 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PublisherTestsCollection.cs (26), When_switching_a_projection_to_non_versionable.cs (12), When_service_is_registered_via_discovery.cs (10).+8.8 ptsHighExplicit Debt
Expand the README with getting-started, architecture overview and a project map.+3.4 ptsMediumDocumentation (README)
Resolve the 2 Low XML-doc coverage finding(s) in Documentation Quality — start with Elders.Cronus.csproj, Elders.Cronus.Performance.csproj.+1.5 ptsLowDocumentation Quality

File quality

Per-file score 0–10 — a quality signature. Of 131 files carrying findings, judged against the Production bar: 2% slop · 66% mixed · 32% near-clean.

FileScoreBandWorst signal
src/Elders.Cronus.Tests/SingletonPerTenantTests.cs2.5SlopExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus/Projections/ProjectionRepository.cs3.0SlopExplicit Debt: EmptyCatchBlock
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
src/Elders.Cronus.Tests/Projections/When_projection_version_with_status_building_is_outside_of_the_timebox.cs4.0MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Discoveries/When_service_is_registered_via_discovery.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Discoveries/When_service_overrides_already_registered_via_discovery.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Middleware/When_transfering_to_another_middleware.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_switching_a_projection_to_non_versionable.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/PublisherTests/PublisherTestsCollection.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_projection_hash_is_calculated.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/EventStream.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_loading_aggregate_root_from_event_store.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_adding_a_building_version_to_a_live_collection.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_adding_a_live_version.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_adding_a_live_version_to_a_versions_collection.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_adding_a_live_version_twice.cs5.2MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_adding_a_building_verrsion.cs5.3MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_adding_a_canceled_version.cs5.3MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_adding_a_live_version_to_a_versions_collectionth.cs5.3MixedExplicit Debt: WriteOnlyPrivateField
src/Elders.Cronus.Tests/Projections/When_adding_a_timedout_version.cs5.3MixedExplicit Debt: WriteOnlyPrivateField

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 325

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.

Serious — 192

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.

Minor — 133

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 3

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

Watchdog 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. 73 of 79 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 79 dimensions across the health lenses
D1D2D3D4D5D6D11D13D14D15D16D17D18D19D21D24D26D27D28D29D30D34D35D43D44AX1AX10AX2AX3AX5AX6AX8DM1DM10DM11DM5DM8DM9ED5GD1IC1M1M2M3M4P1P10P2P3P4P6PF1PF2PF3X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 633 of 650 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a1612f-9a83-7def-b104-f8a86696141d.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D12 Dependency Hygiene — not measured this run — Watchdog 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.
  • 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.
  • D39 IL Efficiency — not measured this run — Watchdog 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 36 further occurrence(s) are not listed individually; the score already reflects all 76.
  • 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.
  • X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 11 further occurrence(s) are not listed individually; the score already reflects all 51.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • 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.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • 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.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (6): D19, D21, D24, D26, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity9.4 / 10Stronggated by 5 serious findings✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Prevented

5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RebuildProjection_Job.RunJobAsync at 18.

RebuildProjection_Job.RunJobAsync (cyclomatic 18)src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:60
ProjectionVersions.Add (cyclomatic 17)src/Elders.Cronus/Projections/ProjectionVersions.cs:58
RebuildProjectionSequentially_Job.RunJobAsync (cyclomatic 17)src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:64
CronusHost.Start (cyclomatic 16)src/Elders.Cronus/Hosting/CronusHost.cs:187
CronusHost.Stop (cyclomatic 16)src/Elders.Cronus/Hosting/CronusHost.cs:206

What to do

  1. Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RebuildProjection_Job.RunJobAsync (cyclomatic 18), ProjectionVersions.Add (cyclomatic 17), RebuildProjectionSequentially_Job.RunJobAsync (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity8.5 / 10Strong✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Prevented

7 method(s) exceeded the cognitive complexity threshold of 15; the worst was CronusOptionsProviderBase.TryValidateObjectRecursive at 36.

CronusOptionsProviderBase.TryValidateObjectRecursive (cognitive 36)src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:69
RebuildProjectionSequentially_Job.RunJobAsync (cognitive 32)src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:64
ProjectionRepository.SaveAsync (cognitive 29)src/Elders.Cronus/Projections/ProjectionRepository.cs:38
RebuildProjection_Job.RunJobAsync (cognitive 27)src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:60
RetryableOperation.TryExecute (cognitive 21)src/Elders.Cronus/Userfull/RetryableOperation.cs:32

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 7 bodies over 15 down to 15 or less in Cognitive Complexity — start with CronusOptionsProviderBase.TryValidateObjectRecursive (cognitive 36), RebuildProjectionSequentially_Job.RunJobAsync (cognitive 32), ProjectionRepository.SaveAsync (cognitive 29). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cognitive Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication9.3 / 10Stronggated by 19 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Verified

19 duplicated block group(s) detected.

Duplicated block (13 lines × 2) · ×3src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:24
Duplicated block (12 lines × 2) · ×3src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:74
Duplicated block (7 lines × 2) · ×3src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:88
Duplicated block (20 lines × 2)src/Elders.Cronus/PublisherBase.cs:288
Duplicated block (14 lines × 2)src/Elders.Cronus/Projections/ProjectionRepository.cs:79

+ 8 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with RebuildProjectionSequentially_Job.cs, CronusOptionsProviderBase.cs, ProjectionRepository.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with RebuildProjectionSequentially_Job.cs, EventStoreIndexManagerAppService.cs, PublisherBase.cs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with RebuildIndex_MessageCounter_Job.cs, RebuildProjectionSequentially_JobData.cs, RebuildProjectionSequentially_Job.cs. — One of this dimension's main actionable groups (3 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

6 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 56 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 flaky across 1 measured tier(s). unit: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 137 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 124 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No source file's living knowledge is concentrated in a single author. Counted over 64 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md.

D17 · Explicit Debt0.0 / 10Critical✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

371 deducted debt markers + 10 dead symbols across 12337 LoC in the .NET projects (23.1/KLoC) → score 0.0.

WriteOnlyPrivateField · ×305src/Elders.Cronus.Tests/Discoveries/When_discoving_jobs_from_discoveryContext.cs:17
EmptyCatchBlock · ×13src/Elders.Cronus/Cluster/Job/CronusJob.cs:77
Whole file has no live code — 1 debt marker inside it · ×15src/Elders.Cronus.Tests/InMemory/InMemoryIndexStore.cs:1
TodoComment · ×13src/Elders.Cronus/AutoUpdates/AutoUpdateSaga.cs:11
Dead code: OneHour · ×10src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs:12

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 305 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PublisherTestsCollection.cs (26), When_switching_a_projection_to_non_versionable.cs (12), When_service_is_registered_via_discovery.cs (10). — One of this dimension's main actionable groups (305 issue-level).
  2. Resolve the 13 EmptyCatchBlock finding(s) in Explicit Debt — start with ProgressTracker.cs (2), CronusJob.cs, PublicEventsPlayer.cs. — One of this dimension's main actionable groups (13 issue-level).
  3. Resolve the 15 Whole file has no live code finding(s) in Explicit Debt — start with InMemoryIndexStore.cs, InMemoryPublisher.cs, When_loading_aggregate_root_with_entity_from_event_store.cs. — One of this dimension's main actionable groups (15 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

6 projects, 840 source files, 16001 hand-written lines of code (12337 production / 3664 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 4 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityStronggated by 2 serious findings◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

Cronus's documentation is clear and complete for its readers: the repository root README gives a strong overview of what the framework is and why it matters, plus links to project boards and GitBook docs. The docs directory contains focused READMEs for each module (cluster, concepts, domain modeling, migrations, event store, etc.) and a comprehensive getting-started guide with realistic business requirements, plus detailed architecture documents covering Application Services, Gateways, Ports, Projections, Sagas, and Triggers. A single XML-doc coverage figure shows 150/1606 documentation for the Cronus.net8.0 assembly (Elders.Cronus) at 9%, which is below the ~2% threshold but not yet outdated; the docs directory itself is well documented.

Low XML-doc coverage: Elders.Cronus(net8.0) · ×2src/Elders.Cronus/Elders.Cronus.csproj

What to do

  1. Resolve the 2 Low XML-doc coverage finding(s) in Documentation Quality — start with Elders.Cronus.csproj, Elders.Cronus.Performance.csproj. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming ConsistencyStrong◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Verified

2 naming inconsistencies across 200 sampled symbols.

The concept of a projection hash is named inconsistently. One field uses the generic name 'hash' while the other uses 'shuffledHash'. While 'shuffledHash' is more descriptive of the specific test scenario, 'hash' is ambiguous in a context where multiple hash-related concepts might exist, and the naming convention for the variable itself differs (simple noun vs adjective-noun).
Inconsistent naming of test setup fields. The codebase uses 'context' for the setup object in some tests (e.g., `When_build_aggregate_root...`) and 'of' for the 'Because' clause in others (e.g., `When_breaking_middleware`). However, in `When_adding_a_live_version_to_a_versions_collectionth`, the field is named 'context' but appears to be a typo for 'collection' or similar, and in `When_adding_a_live_version_twice`, the 'Because' field is named 'of' while in `When_breaking_middleware` it is also 'of'. The inconsistency lies in the mix of 'context' and 'of' for BDD-style setup fields, and the typo 'collectionth' in one field name. Additionally, 'nextVersion' is used in one test while 'startingTimestamp' is used in another, which are different concepts but follow no consistent pattern for test-specific variables.

What to do

  1. Resolve the 1 The concept of a projection hash is named inconsistently. One field uses… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 Inconsistent naming of test setup fields. The codebase uses 'context'… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment ValueStrong◐ Sampled · advisory

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

58 valuable / 1 redundant across 200 sampled comments; 1 shown with locations.

redundant commentsrc/Elders.Cronus/MessageProcessing/CronusPublisher.cs:46

What to do

  1. Resolve the 1 redundant comment finding(s) in Comment Value — start with CronusPublisher.cs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion3.3 / 10Weak✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 3.3 / 10 · rule-coverage 100% · ceiling Documented

1 of 3 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability8.4 / 10Strong✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Documented

73 % of calls cross a namespace and 15 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

Pass-through layersrc/Elders.Cronus/Discoveries/DiscoveryContext.cs:9

What to do

  1. Resolve the 1 Pass-through layer finding(s) in Navigability — start with DiscoveryContext.cs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)6.0 / 10Adequate✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 3 high, 0 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities8.6 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 2 high, 1 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

64 of 64 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Elders.Cronus/Projections/ProjectionRepository.cs. Counted over 64 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×64src/Elders.Cronus/Projections/ProjectionRepository.cs:1
Dormant codebase

What to do

  1. Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with ProjectionRepository.cs, PublisherBase.cs, RetryPolicy.cs. — One of this dimension's main actionable groups (64 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition8.9 / 10Strong✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons5.9 / 10Adequate✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `CronusHeartbeat` is a singleton (one shared instance) but mutates instance state outside any lock (options, tenants; e.g. `options` at line 63). — src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:12
  • `CronusBooter` is a singleton (one shared instance) but mutates instance state outside any lock (tenantOptions; e.g. `tenantOptions` at line 59). — src/Elders.Cronus/Hosting/CronusBooter.cs:11
  • `DefaultCronusContextFactory` is a singleton (one shared instance) but mutates instance state outside any lock (tenantsOptions; e.g. `tenantsOptions` at line 80). — src/Elders.Cronus/MessageProcessing/CronusContextFactory.cs:15

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

  • The namespaces Elders.Cronus ↔ Elders.Cronus.Cluster.Job ↔ Elders.Cronus.Discoveries ↔ Elders.Cronus.EventStore ↔ Elders.Cronus.EventStore.Index ↔ Elders.Cronus.EventStore.Players ↔ Elders.Cronus.IntegrityValidation ↔ Elders.Cronus.MessageProcessing ↔ Elders.Cronus.Migrations ↔ Elders.Cronus.Multitenancy ↔ Elders.Cronus.Projections ↔ Elders.Cronus.Projections.Cassandra ↔ Elders.Cronus.Projections.Rebuilding ↔ Elders.Cronus.Projections.Versioning depend on each other. The lightest dependency in the cycle is Elders.Cronus → Elders.Cronus.Cluster.Job (Elders.Cronus.CronusHost → Elders.Cronus.Cluster.Job.JobManager, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Elders.Cronus/Hosting/CronusHost.cs:4
  • The namespaces (global) ↔ Elders.Cronus.EventStore.AutoUpdater ↔ Elders.Cronus.EventStore.AutoUpdater.Commands ↔ Elders.Cronus.EventStore.AutoUpdater.Events depend on each other. The lightest dependency in the cycle is (global) → Elders.Cronus.EventStore.AutoUpdater (AutoUpdate → Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterStatus, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterState.cs:1

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

DM11 · Constructible invalid state5.3 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

  • `AutoUpdater`'s public constructor takes `bc` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `AutoUpdater` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdater.cs:13
  • `ProjectionVersionManager`'s public constructor takes `hash` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ProjectionVersionManager` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs:11

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

DM9 · Scattered domain decisions9.6 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

  • Elders.Cronus.Projections.ProjectionStatus's [Fixing, New] are judged in Elders.Cronus.Projections.ProjectionVersions, Elders.Cronus.Projections.Versioning.ProjectionVersionManager — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.

What to do

  • Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
ED5 · Idempotency8.4 / 10Strong◐ Sampled · advisory

Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.

Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.

  • `AutoUpdater.AutoUpdaterApplicationService.HandleAsync` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. (×3) — src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:14, src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:30, src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:56
  • `Versioning.ProjectionVersionManagerAppService.HandleAsync` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Elders.Cronus/Projections/Versioning/ProjectionVersionManagerAppService.cs:61

What to do

  • Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — src/Elders.Cronus/Cluster/Job/InMemory/InMemoryCronusJobRunner.cs:10, src/Elders.Cronus/PublisherBase.cs:80, src/Elders.Cronus.Performance/LoggingBenchmark.cs:54

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs6.9 / 10Adequate✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `MyLogger` has 3 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — src/Elders.Cronus.Performance/LoggingBenchmark.cs:52
  • `BeginScope` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Elders.Cronus.Performance/LoggingBenchmark.cs:54
  • `IsEnabled` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Elders.Cronus.Performance/LoggingBenchmark.cs:55
  • `LogCore` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/Elders.Cronus.Performance/LoggingBenchmark.cs:59
  • `JobManager` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Elders.Cronus/Cluster/Job/InMemory/InMemoryCronusJobRunner.cs:10
  • `PingAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Elders.Cronus/Cluster/Job/InMemory/NoClusterOperations.cs:8
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×34) — src/Elders.Cronus.Performance/LoggingBenchmark.cs:5, src/Elders.Cronus.Performance/Program.cs:4, src/Elders.Cronus.Performance/Program.cs:5, …

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)4.7 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

  • The root README is 119 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.

What to do

  • Expand the README with getting-started, architecture overview and a project map.
  • 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.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 3 of 3 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • 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 structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/cronus-framework/configuration.md:148
  • docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/cronus-framework/configuration.md:148
  • docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/cronus-framework/configuration.md:172
  • docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/cronus-framework/configuration.md:172
  • docs/getting-started/quick-start/setup.md installs the package `Cronus` (`dotnet add package Cronus`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/quick-start/setup.md:25
  • docs/getting-started/quick-start/setup.md installs the package `Cronus.Transport.RabbitMQ` (`dotnet add package Cronus.Transport.RabbitMQ`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/quick-start/setup.md:29
  • docs/getting-started/quick-start/setup.md installs the package `Cronus.Persistence.Cassandra` (`dotnet add package Cronus.Persistence.Cassandra`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/quick-start/setup.md:30
  • docs/getting-started/quick-start/setup.md installs the package `Cronus.Serialization.NewtonsoftJson` (`dotnet add package Cronus.Serialization.NewtonsoftJson`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/quick-start/setup.md:31
  • docs/getting-started/quick-start/setup.md installs the package `Microsoft.Extensions.Hosting` (`dotnet add package Microsoft.Extensions.Hosting`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/quick-start/setup.md:32

What to do

  • Reconcile the README with reality: docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`; docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`; docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`; docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`; docs/getting-started/quick-start/setup.md installs the package `Cronus` (`dotnet add package Cronus`), but no project or props file references it.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning2.0 / 10Critical✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

  • 762/798 types (95%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
  • No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.

What to do

  • Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
  • Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
P2 · Observability9.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

What to do

  • Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 867 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.

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF1 · Benchmark discipline9.5 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

PF2 · Allocation hygiene6.8 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 21 use(s) across 12,437 production line(s) (~1.7/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
PF3 · Async & latency hygiene6.5 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • 2 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — src/Elders.Cronus/Hosting/CronusHost.cs:172, src/Elders.Cronus/Hosting/ProjectionsStartup.cs:17
  • `await updater.ApplyAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/AutoUpdates/AutoUpdateSaga.cs:24
  • `await repository.LoadAsync<AutoUpdater>(command.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×4) — src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:16, src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:32, src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:48, …
  • `await indexStore.ApendAsync(indexRecord)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs:48
  • `await countTask` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:71
  • `await resetTask` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:72
  • `await retryPolicy.ExecuteActionAsync(() => workflow.RunAsync(execution.Context))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs:26
  • `await func()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/FaultHandling/RetryPolicy.cs:165
  • `await Task.Delay(delay)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/FaultHandling/RetryPolicy.cs:207
  • `await rpcHost.StartAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/Hosting/CronusHost.cs:120
  • `await Task.Delay(TimeSpan.FromSeconds(options.IntervalInSeconds), stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:45
  • `await base.StopAsync(stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeatService.cs:49
  • `await source.EnumerateEventStore(@operator, playerOptions)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Elders.Cronus/Migrations/CopyEventStore.cs:24, src/Elders.Cronus/Migrations/ValidateEventStore.cs:27
  • `await OptionsChangedBootstrapProjectionsForTenantAsync(newOptions)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:35
  • `await Task.WhenAll(tenantBootstrapTasks)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:51, src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:103

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
X1 · Async correctness6.9 / 10Adequate✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. — src/Elders.Cronus/Hosting/CronusHost.cs:172
  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. — src/Elders.Cronus/Hosting/ProjectionsStartup.cs:17

What to do

  • Sync-over-async (deadlock risk)
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `pingSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 41). Every use of it in `RunJobAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var pingSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:41
  • `pingSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 91). Every use of it in `RunJobAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var pingSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:91

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.8 / 10Weak✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 9/57 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/Elders.Cronus/DangerZone/DangerZoneExecutor.cs:26, src/Elders.Cronus/EventStore/AggregateRepository.cs:67, src/Elders.Cronus/EventStore/CronusAggregateCommitInterceptor.cs:15, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

  • The guard on line 13 rejects `status` and line 14 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(status)` is true of a value that is NOT null: it is satisfied by an EMPTY `status`, and on that path `status` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterStatus.cs:14
  • The guard on line 61 rejects `value` and line 62 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(value)` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Elders.Cronus/EventStore/PagingOptions.cs:62
  • The guard on line 69 rejects `tenant` and line 69 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(tenant)` is true of a value that is NOT null: it is satisfied by an EMPTY `tenant`, and on that path `tenant` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Elders.Cronus/MessageProcessing/CronusContextFactory.cs:69
  • The guard on line 17 rejects `contractId` and line 17 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(contractId)` is true of a value that is NOT null: it is satisfied by an EMPTY `contractId`, and on that path `contractId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Elders.Cronus/Projections/EventStoreIndexEventTypeId.cs:17
  • The guard on line 47 rejects `contractId` and line 47 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(contractId)` is true of a value that is NOT null: it is satisfied by an EMPTY `contractId`, and on that path `contractId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Elders.Cronus/Projections/EventStoreIndexEventTypeId.cs:47
  • The guard on line 188 rejects `projectionName` and line 188 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(projectionName)` is true of a value that is NOT null: it is satisfied by an EMPTY `projectionName`, and on that path `projectionName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Elders.Cronus/Projections/ProjectionRepository.cs:188
  • The guard on line 15 rejects `status` and line 16 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(status)` is true of a value that is NOT null: it is satisfied by an EMPTY `status`, and on that path `status` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/Elders.Cronus/Projections/ProjectionStatus.cs:16
  • The guard on line 18 rejects `hash` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(hash)` is true of a value that is NOT null: it is satisfied by an EMPTY `hash`, and on that path `hash` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. (×2) — src/Elders.Cronus/Projections/Versioning/Commands/FixProjectionVersion.cs:18, src/Elders.Cronus/Projections/Versioning/Commands/NewProjectionVersion.cs:18

What to do

  • Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling4.7 / 10Weak✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×13) — src/Elders.Cronus/Cluster/Job/CronusJob.cs:77, src/Elders.Cronus/EventStore/Players/PublicEventsPlayer.cs:34, src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:51, …

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

X4 · Structured logging6.8 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×4) — src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs:43, src/Elders.Cronus/EventStore/LoggingAggregateRepository.cs:51, src/Elders.Cronus/Migrations/CronusMigrator.cs:35, …

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This method contradicts itself about `projection`: line 123 assigns it with `as IProjectionDefinition`, which hands back null rather than throwing when the value is not a `IProjectionDefinition`, but line 125 then dereferences it directly as `projection.GetProjectionIds` 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 `projection` once before the first use and handle the null case, or cast with `(IProjectionDefinition)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Elders.Cronus/Projections/ProjectionRepository.cs:125
  • This method contradicts itself about `iterator`: line 58 assigns it with `as IEnumerator<WorkflowBase<TContext>>`, which hands back null rather than throwing when the value is not a `IEnumerator<WorkflowBase<TContext>>`, but line 63 then dereferences it directly as `iterator.MoveNext` 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 `iterator` once before the first use and handle the null case, or cast with `(IEnumerator<WorkflowBase<TContext>>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Elders.Cronus/Workflow/WorkflowBase.cs:63
  • 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). 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 `?.`.
  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health35%Weak — gated by D17, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture83%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity28%Weak — gated by D34, M2, M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness56%Adequate — gated by P10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security89%StrongStrongest area.
Domain Modelling83%StrongSolid.
Performance73%StrongSolid.
Unscored — 4 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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.
  • X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 48 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • 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.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • 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.
  • D10 Test Quality — ~4032 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (12,337 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+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (Elders.Cronus), which is a layered codebase, not two contexts. 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"]`.
  • D25 ADR Conformance — no ADRs to check
  • 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.
  • 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.
  • D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
  • D9 Test Distribution — 1 test project(s) found on disk but excluded from the analyzed solution.
  • DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
  • DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 12 event handler(s); 16 CQRS handler(s)
  • ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 6 projection(s); an append-only event-store seam (IEventStore/Append-of-events)
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • 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.
  • X6 Hand-rolled structured-format parsing — 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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 325 finding(s)
D17 · Explicit Debt · WriteOnlyPrivateField · ×305
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_discoving_jobs_from_discoveryContext.cs:17 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_service_is_registered_via_discovery.cs:13 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_service_is_registered_via_discovery.cs:42 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_service_overrides_already_registered_via_discovery.cs:13 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_service_overrides_already_registered_via_discovery.cs:49 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/EventStream.cs:12 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/EventStream.cs:36 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Hosting/When_adding_event_to_aggregateCommit.cs:11 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_loading_aggregate_root_from_event_store.cs:20 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_saving_aggregate_root_in_event_store.cs:15 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__AggregateCommit__has_duplicate_revisions.cs:13 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__AggregateCommit__has_missing_revisions.cs:14 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__AggregateCommit__has_unordered_revisions.cs:13 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__AggregateCommit__has_unordered_revisions_and_resolving_them.cs:13 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__EventStreamPolicy_is_applied_to_a_correct__EventStream__.cs:13 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When_comparing_two__IntegrityRules__are_identical.cs:11 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_attaching_multiple_middlewares.cs:10 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_breaking_middleware.cs:11 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_executing_middleware_tree.cs:9 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_executing_single_middleware.cs:9 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_transfering_to_another_middleware.cs:11 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_transfering_to_another_middleware.cs:59 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_transfering_to_another_middleware_and_there_is_no_followup_middleware.cs:11 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Migrations/When_adding_event_to_aggregateCommit.cs:14 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Elders.Cronus.Tests/Migrations/When_evalueting_if_migration_should_apply.cs:14 — private Establish context — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • + 280 more in this group — see findings.md.
D17 · Explicit Debt · EmptyCatchBlock · ×13
  • EmptyCatchBlock src/Elders.Cronus/Cluster/Job/CronusJob.cs:77 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/EventStore/Players/PublicEventsPlayer.cs:34 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:51 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/MessageProcessing/AggregateCommitPublisher.cs:34 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/MessageProcessing/ErrorContext.cs:45 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Migrations/AggregateCommitMigrationWorkflow.cs:30 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Migrations/CronusMigrator.cs:35 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs:38 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Migrations/MigrationWorkflowBase.cs:32 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Projections/ProjectionRepository.cs:162 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:143 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:170 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Elders.Cronus/Workflow/ExceptionEaterWorkflow.cs:21 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
AX3 · Project dependency cycles · Namespace dependency cycle · ×2
  • Namespace dependency cycle src/Elders.Cronus/Hosting/CronusHost.cs:4 — The namespaces Elders.Cronus ↔ Elders.Cronus.Cluster.Job ↔ Elders.Cronus.Discoveries ↔ Elders.Cronus.EventStore ↔ Elders.Cronus.EventStore.Index ↔ Elders.Cronus.EventStore.Players ↔ Elders.Cronus.IntegrityValidation ↔ Elders.Cronus.MessageProcessing ↔ Elders.Cronus.Migrations ↔ Elders.Cronus.Multitenancy ↔ Elders.Cronus.Projections ↔ Elders.Cronus.Projections.Cassandra ↔ Elders.Cronus.Projections.Rebuilding ↔ Elders.Cronus.Projections.Versioning depend on each other. The lightest dependency in the cycle is Elders.Cronus → Elders.Cronus.Cluster.Job (Elders.Cronus.CronusHost → Elders.Cronus.Cluster.Job.JobManager, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterState.cs:1 — The namespaces (global) ↔ Elders.Cronus.EventStore.AutoUpdater ↔ Elders.Cronus.EventStore.AutoUpdater.Commands ↔ Elders.Cronus.EventStore.AutoUpdater.Events depend on each other. The lightest dependency in the cycle is (global) → Elders.Cronus.EventStore.AutoUpdater (AutoUpdate → Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterStatus, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 192 finding(s)
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: WipeDataAsync src/Elders.Cronus/DangerZone/DangerZoneExecutor.cs:26 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SaveInternalAsync src/Elders.Cronus/EventStore/AggregateRepository.cs:67 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnAppendAsync src/Elders.Cronus/EventStore/CronusAggregateCommitInterceptor.cs:15 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnAppendingAsync src/Elders.Cronus/EventStore/CronusAggregateCommitInterceptor.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AppendAsync src/Elders.Cronus/EventStore/CronusEventStore.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AppendAsync src/Elders.Cronus/EventStore/CronusEventStore.cs:31 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteAsync src/Elders.Cronus/EventStore/CronusEventStore.cs:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadAggregateEventRaw src/Elders.Cronus/EventStore/CronusEventStore.cs:55 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadAsync src/Elders.Cronus/EventStore/CronusEventStore.cs:67 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadWithPagingAsync src/Elders.Cronus/EventStore/CronusEventStore.cs:79 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: IndexAsync src/Elders.Cronus/EventStore/Index/ProjectionIndex.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ExecuteActionAsync src/Elders.Cronus/FaultHandling/RetryPolicy.cs:149 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: StartAsync src/Elders.Cronus/Hosting/CronusHost.cs:85 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: StopAsync src/Elders.Cronus/Hosting/CronusHost.cs:131 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/DynamicMessageHandle.cs:12 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/DynamicMessageIndex.cs:12 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/MessageHandleWorkflow.cs:63 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/CopyEventStore.cs:16 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: MigrateAsync src/Elders.Cronus/Migrations/CronusMigrator.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs:15 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/ValidateEventStore.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BootstrapAsync src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:39 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BootstrapProjectionsForTenantAsync src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OptionsChangedBootstrapProjectionsForTenantAsync src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:86 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
PF3 · Async & latency hygiene · Awaits without ConfigureAwait(false) · ×19
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/AutoUpdates/AutoUpdateSaga.cs:24 — `await updater.ApplyAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:16 — `await repository.LoadAsync<AutoUpdater>(command.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:32 — `await repository.LoadAsync<AutoUpdater>(command.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:48 — `await repository.LoadAsync<AutoUpdater>(command.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:58 — `await repository.LoadAsync<AutoUpdater>(command.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs:48 — `await indexStore.ApendAsync(indexRecord)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:71 — `await countTask` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:72 — `await resetTask` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs:26 — `await retryPolicy.ExecuteActionAsync(() => workflow.RunAsync(execution.Context))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/RetryPolicy.cs:165 — `await func()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/RetryPolicy.cs:207 — `await Task.Delay(delay)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/CronusHost.cs:120 — `await rpcHost.StartAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:45 — `await Task.Delay(TimeSpan.FromSeconds(options.IntervalInSeconds), stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeatService.cs:49 — `await base.StopAsync(stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/Migrations/CopyEventStore.cs:24 — `await source.EnumerateEventStore(@operator, playerOptions)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/Migrations/ValidateEventStore.cs:27 — `await source.EnumerateEventStore(@operator, playerOptions)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:35 — `await OptionsChangedBootstrapProjectionsForTenantAsync(newOptions)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:51 — `await Task.WhenAll(tenantBootstrapTasks)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:103 — `await Task.WhenAll(tenantBootstrapTasks)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
D17 · Explicit Debt · Whole file has no live code · ×15
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemory/InMemoryIndexStore.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 5 debt markers inside it src/Elders.Cronus.Tests/InMemory/InMemoryPublisher.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 5 debt markers (5 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 5 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 3 debt markers inside it src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_loading_aggregate_root_with_entity_from_event_store.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 3 debt markers (3 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 3 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 2 debt markers inside it src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_loading_events_for_replay.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 2 debt markers (2 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 2 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_checking_a_locked_resource.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_checking_a_not_locked_resource.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_checking_for_expired_locked_resource.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_locking_resource.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_unlocking_a_locked_resource.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_unlocking_a_specific_locked_resource.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 6 debt markers inside it src/Elders.Cronus.Tests/When_resolve_scoped_component_out_of_scope.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 6 debt markers (6 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 6 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus/Discoveries/ProjectionPlayerDiscovery.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 4 debt markers inside it src/Elders.Cronus/MessageProcessing/CronusPublisher.cs:11 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 4 debt markers (4 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 4 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 2 debt markers inside it src/Elders.Cronus/Projections/InMemory/InMemoryProjectionStore.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 2 debt markers (2 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 2 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
  • Whole file has no live code — 1 debt marker inside it src/Elders.Cronus/Projections/Versioning/InMemoryProjectionVersionStore.cs:10 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · TodoComment · ×13
  • TodoComment src/Elders.Cronus/AutoUpdates/AutoUpdateSaga.cs:11 — // TODO: in future we can have scheduled messages — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/Discoveries/CronusHostDiscovery.cs:42 — // TODO: Check if this is alrady registered in the foreach above. If yes we can remove this line. Elase we have to figure out what is going on — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdater.cs:56 — // TODO: failed status? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterState.cs:72 — // TODO: think for retries? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterState.cs:80 — // TODO: in future we might execute in parallel — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/EventStore/Players/ReplayPublicEvents_Job.cs:48 — //TODO: Document which headers are essential or make another ctor for CronusMessage with byte[] — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/Hosting/ICronusStartup.cs:8 — // TODO: Make this async — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/Hosting/ICronusStartup.cs:15 — //TODO: also make this async :) kali — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/Hosting/SingletonPerTenantContainer.cs:29 — // TODO: mynkow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/Projections/ProjectionRepository.cs:44 — // TODO: inspect the type if it implements IProjectionDefinition — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/Projections/ProjectionVersions.cs:152 — // TODO: This will crash with null ref — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/Projections/ProjectionVersions.cs:164 — // TODO: This will crash with null ref — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs:94 — // TODO: check if the timebox really has expired LOL :), Believe me, do it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
X3 · Exception handling · Swallowed exception (empty catch) · ×13
  • Swallowed exception (empty catch) src/Elders.Cronus/Cluster/Job/CronusJob.cs:77 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/EventStore/Players/PublicEventsPlayer.cs:34 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:51 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/MessageProcessing/AggregateCommitPublisher.cs:34 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/MessageProcessing/ErrorContext.cs:45 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Migrations/AggregateCommitMigrationWorkflow.cs:30 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Migrations/CronusMigrator.cs:35 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs:38 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Migrations/MigrationWorkflowBase.cs:32 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Projections/ProjectionRepository.cs:162 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:143 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:170 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Elders.Cronus/Workflow/ExceptionEaterWorkflow.cs:21 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D17 · Explicit Debt · Dead code · ×10
  • Dead code: OneHour src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs:12 — Field OneHour — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: EightHours src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs:14 — Field EightHours — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: RealyLongTime src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs:16 — Field RealyLongTime — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: DiagnosticsUnhandledExceptionKey src/Elders.Cronus/Workflow/DiagnosticsWorkflow.cs:36 — Field DiagnosticsUnhandledExceptionKey — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: OverriderDiscoveredModel src/Elders.Cronus.Tests/Discoveries/Models.cs:13 — NamedType OverriderDiscoveredModel — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus.Tests(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: LoadAggregateCommitsAsync src/Elders.Cronus.Tests/InMemory/InMemoryEventStorePlayer.cs:27 — Method LoadAggregateCommitsAsync — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus.Tests(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: TestEventStorePlayer src/Elders.Cronus.Tests/Migrations/TestModel/TestEventStorePlayer.cs:9 — NamedType TestEventStorePlayer — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus.Tests(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: Class1 src/Elders.Cronus.Tests/Performance/Class1.cs:3 — NamedType Class1 — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus.Tests(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: When__SingletonPerTenantContainer__is_used src/Elders.Cronus.Tests/SingletonPerTenantTests.cs:9 — NamedType When__SingletonPerTenantContainer__is_used — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus.Tests(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: When__SingletonPerTenantContainer__is_disposed src/Elders.Cronus.Tests/SingletonPerTenantTests.cs:31 — NamedType When__SingletonPerTenantContainer__is_disposed — Roslyn's SymbolFinder walked every project the solution loads, including Elders.Cronus.Tests(net8.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×9
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterStatus.cs:14 — The guard on line 13 rejects `status` and line 14 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(status)` is true of a value that is NOT null: it is satisfied by an EMPTY `status`, and on that path `status` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/EventStore/PagingOptions.cs:62 — The guard on line 61 rejects `value` and line 62 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(value)` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/MessageProcessing/CronusContextFactory.cs:69 — The guard on line 69 rejects `tenant` and line 69 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(tenant)` is true of a value that is NOT null: it is satisfied by an EMPTY `tenant`, and on that path `tenant` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/EventStoreIndexEventTypeId.cs:17 — The guard on line 17 rejects `contractId` and line 17 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(contractId)` is true of a value that is NOT null: it is satisfied by an EMPTY `contractId`, and on that path `contractId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/EventStoreIndexEventTypeId.cs:47 — The guard on line 47 rejects `contractId` and line 47 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(contractId)` is true of a value that is NOT null: it is satisfied by an EMPTY `contractId`, and on that path `contractId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/ProjectionRepository.cs:188 — The guard on line 188 rejects `projectionName` and line 188 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(projectionName)` is true of a value that is NOT null: it is satisfied by an EMPTY `projectionName`, and on that path `projectionName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/ProjectionStatus.cs:16 — The guard on line 15 rejects `status` and line 16 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(status)` is true of a value that is NOT null: it is satisfied by an EMPTY `status`, and on that path `status` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/Versioning/Commands/FixProjectionVersion.cs:18 — The guard on line 18 rejects `hash` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(hash)` is true of a value that is NOT null: it is satisfied by an EMPTY `hash`, and on that path `hash` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/Versioning/Commands/NewProjectionVersion.cs:18 — The guard on line 18 rejects `hash` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(hash)` is true of a value that is NOT null: it is satisfied by an EMPTY `hash`, and on that path `hash` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
D17 · Explicit Debt · CommentedOutCode · ×8
  • CommentedOutCode src/Elders.Cronus.Tests/Projections/When_projection_version_with_status_building_is_outside_of_the_timebox.cs:74 — 7 consecutive commented-code lines
  • CommentedOutCode src/Elders.Cronus/EventStore/Integrity/EventStreamIntegrityPolicy.cs:44 — 4 consecutive commented-code lines
  • CommentedOutCode src/Elders.Cronus/EventStore/Integrity/EventStreamIntegrityPolicy.cs:51 — 4 consecutive commented-code lines
  • CommentedOutCode src/Elders.Cronus/Projections/ProjectionVersion.cs:36 — 4 consecutive commented-code lines
  • CommentedOutCode src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:63 — 5 consecutive commented-code lines
  • CommentedOutCode src/Elders.Cronus/FaultHandling/Strategies/Incremental.cs:56 — 3 consecutive commented-code lines
  • CommentedOutCode src/Elders.Cronus/Hosting/AssemblyLoader.cs:53 — 3 consecutive commented-code lines
  • CommentedOutCode src/Elders.Cronus/Multitenancy/DefaultTenantResolver.cs:19 — 3 consecutive commented-code lines
ED5 · Idempotency · Non-idempotent mutation · ×4
  • Non-idempotent mutation: AutoUpdater.AutoUpdaterApplicationService.HandleAsync src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:14 — `AutoUpdater.AutoUpdaterApplicationService.HandleAsync` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: AutoUpdater.AutoUpdaterApplicationService.HandleAsync src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:30 — `AutoUpdater.AutoUpdaterApplicationService.HandleAsync` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: AutoUpdater.AutoUpdaterApplicationService.HandleAsync src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:56 — `AutoUpdater.AutoUpdaterApplicationService.HandleAsync` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: Versioning.ProjectionVersionManagerAppService.HandleAsync src/Elders.Cronus/Projections/Versioning/ProjectionVersionManagerAppService.cs:61 — `Versioning.ProjectionVersionManagerAppService.HandleAsync` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
AX2 · Stateful singletons · Stateful singleton · ×3
  • Stateful singleton: CronusHeartbeat src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:12 — `CronusHeartbeat` is a singleton (one shared instance) but mutates instance state outside any lock (options, tenants; e.g. `options` at line 63).
  • Stateful singleton: CronusBooter src/Elders.Cronus/Hosting/CronusBooter.cs:11 — `CronusBooter` is a singleton (one shared instance) but mutates instance state outside any lock (tenantOptions; e.g. `tenantOptions` at line 59).
  • Stateful singleton: DefaultCronusContextFactory src/Elders.Cronus/MessageProcessing/CronusContextFactory.cs:15 — `DefaultCronusContextFactory` is a singleton (one shared instance) but mutates instance state outside any lock (tenantsOptions; e.g. `tenantsOptions` at line 80).
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:24 — src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:24-36 | src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:22-34 — before extracting anything, compare `src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs` and `src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:95 — src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:95-107 | src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:110-122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:95` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Elders.Cronus/Projections/ProjectionRepository.cs:209 — src/Elders.Cronus/Projections/ProjectionRepository.cs:209-221 | src/Elders.Cronus/Projections/ProjectionRepository.cs:251-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Elders.Cronus/Projections/ProjectionRepository.cs:209` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:74 — src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:74-85 | src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:77-88 — before extracting anything, compare `src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs` and `src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/Elders.Cronus/EventStore/Index/EventStoreIndexManagerAppService.cs:32 — src/Elders.Cronus/EventStore/Index/EventStoreIndexManagerAppService.cs:32-43 | src/Elders.Cronus/EventStore/Index/EventStoreIndexManagerAppService.cs:55-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `RebuildIndexCommand` in one and `FinalizeEventStoreIndexRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 2) src/Elders.Cronus/PublisherBase.cs:221 — src/Elders.Cronus/PublisherBase.cs:221-232 | src/Elders.Cronus/Workflow/DiagnosticsWorkflow.cs:96-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Elders.Cronus/PublisherBase.cs:221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:88 — src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:88-94 | src/Elders.Cronus/Projections/Rebuilding/ProjectionVersionHelper.cs:120-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_JobData.cs:20 — src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_JobData.cs:20-26 | src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_JobData.cs:23-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:218 — src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:218-224 | src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:201-207 — before extracting anything, compare `src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs` and `src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
GD1 · Unfinished & placeholder code · Unfinished stub · ×3
  • Unfinished stub — throws NotImplementedException src/Elders.Cronus/Cluster/Job/InMemory/InMemoryCronusJobRunner.cs:10 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Elders.Cronus/PublisherBase.cs:80 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Elders.Cronus.Performance/LoggingBenchmark.cs:54 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×3
  • Sync-over-async blocking — 2 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Elders.Cronus/Hosting/CronusHost.cs:172 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Elders.Cronus/Hosting/ProjectionsStartup.cs:17 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
D19 · Documentation Quality · Low XML-doc coverage · ×2
  • Low XML-doc coverage: Elders.Cronus(net8.0) src/Elders.Cronus/Elders.Cronus.csproj — Elders.Cronus(net8.0): 9 % XML-doc coverage (150/1606).
  • Low XML-doc coverage: Elders.Cronus.Performance(net8.0) src/Elders.Cronus.Performance/Elders.Cronus.Performance.csproj — Elders.Cronus.Performance(net8.0): 0 % XML-doc coverage (0/16).
DM11 · Constructible invalid state · Constructible in an invalid state · ×2
  • Constructible in an invalid state: AutoUpdater src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdater.cs:13 — `AutoUpdater`'s public constructor takes `bc` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `AutoUpdater` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: ProjectionVersionManager src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs:11 — `ProjectionVersionManager`'s public constructor takes `hash` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ProjectionVersionManager` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/Elders.Cronus.Performance/LoggingBenchmark.cs:54 — `BeginScope` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Elders.Cronus/Cluster/Job/InMemory/InMemoryCronusJobRunner.cs:10 — `JobManager` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Hollow method · ×2
  • Hollow method — returns a constant without doing the work src/Elders.Cronus.Performance/LoggingBenchmark.cs:55 — `IsEnabled` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work src/Elders.Cronus/Cluster/Job/InMemory/NoClusterOperations.cs:8 — `PingAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×2
  • Sync-over-async (deadlock risk) src/Elders.Cronus/Hosting/CronusHost.cs:172 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
  • Sync-over-async (deadlock risk) src/Elders.Cronus/Hosting/ProjectionsStartup.cs:17 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×2
  • Disposable created and abandoned in the method that made it src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:41 — `pingSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 41). Every use of it in `RunJobAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var pingSource = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:91 — `pingSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 91). Every use of it in `RunJobAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var pingSource = …;`), which releases it at the end of the scope on every path including a throw.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×2
  • Symbol treated as nullable, then dereferenced unguarded src/Elders.Cronus/Projections/ProjectionRepository.cs:125 — This method contradicts itself about `projection`: line 123 assigns it with `as IProjectionDefinition`, which hands back null rather than throwing when the value is not a `IProjectionDefinition`, but line 125 then dereferences it directly as `projection.GetProjectionIds` 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 `projection` once before the first use and handle the null case, or cast with `(IProjectionDefinition)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Elders.Cronus/Workflow/WorkflowBase.cs:63 — This method contradicts itself about `iterator`: line 58 assigns it with `as IEnumerator<WorkflowBase<TContext>>`, which hands back null rather than throwing when the value is not a `IEnumerator<WorkflowBase<TContext>>`, but line 63 then dereferences it directly as `iterator.MoveNext` 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 `iterator` once before the first use and handle the null case, or cast with `(IEnumerator<WorkflowBase<TContext>>)` so the failure is reported where it happens — rather than leaving the two readings side by side.
D1 · Cyclomatic Complexity · RebuildProjection_Job.RunJobAsync (cyclomatic 18) · ×1
  • RebuildProjection_Job.RunJobAsync (cyclomatic 18) src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:60 — RebuildProjection_Job.RunJobAsync has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ProjectionVersions.Add (cyclomatic 17) · ×1
  • ProjectionVersions.Add (cyclomatic 17) src/Elders.Cronus/Projections/ProjectionVersions.cs:58 — ProjectionVersions.Add has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RebuildProjectionSequentially_Job.RunJobAsync (cyclomatic 17) · ×1
  • RebuildProjectionSequentially_Job.RunJobAsync (cyclomatic 17) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:64 — RebuildProjectionSequentially_Job.RunJobAsync has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CronusHost.Start (cyclomatic 16) · ×1
  • CronusHost.Start (cyclomatic 16) src/Elders.Cronus/Hosting/CronusHost.cs:187 — CronusHost.Start has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (CronusHost.Stop) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · CronusHost.Stop (cyclomatic 16) · ×1
  • CronusHost.Stop (cyclomatic 16) src/Elders.Cronus/Hosting/CronusHost.cs:206 — CronusHost.Stop has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (CronusHost.Start) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D17 · Explicit Debt · HackComment · ×1
  • HackComment src/Elders.Cronus.Tests/Migrations/TestModel/TestEventStorePlayer.cs:30 — // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · CronusOptionsProviderBase.TryValidateObjectRecursive (cognitive 36) · ×1
  • CronusOptionsProviderBase.TryValidateObjectRecursive (cognitive 36) src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:69 — CronusOptionsProviderBase.TryValidateObjectRecursive has cognitive complexity 36 (threshold 15). Of this number, 35 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RebuildProjectionSequentially_Job.RunJobAsync (cognitive 32) · ×1
  • RebuildProjectionSequentially_Job.RunJobAsync (cognitive 32) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:64 — RebuildProjectionSequentially_Job.RunJobAsync has cognitive complexity 32 (threshold 15). Most of this is not in the body itself: 14 of the 32 points are its own statements and the rest belongs to one function literal inside it that branches (line 99). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ProjectionRepository.SaveAsync (cognitive 29) · ×1
  • ProjectionRepository.SaveAsync (cognitive 29) src/Elders.Cronus/Projections/ProjectionRepository.cs:38 — ProjectionRepository.SaveAsync has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RebuildProjection_Job.RunJobAsync (cognitive 27) · ×1
  • RebuildProjection_Job.RunJobAsync (cognitive 27) src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:60 — RebuildProjection_Job.RunJobAsync has cognitive complexity 27 (threshold 15). Of this number, 21 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RetryableOperation.TryExecute (cognitive 21) · ×1
  • RetryableOperation.TryExecute (cognitive 21) src/Elders.Cronus/Userfull/RetryableOperation.cs:32 — RetryableOperation.TryExecute has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RetryPolicy.ExecuteActionAsync (cognitive 20) · ×1
  • RetryPolicy.ExecuteActionAsync (cognitive 20) src/Elders.Cronus/FaultHandling/RetryPolicy.cs:149 — RetryPolicy.ExecuteActionAsync has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ProjectionRepository.SaveAsync (cognitive 20) · ×1
  • ProjectionRepository.SaveAsync (cognitive 20) src/Elders.Cronus/Projections/ProjectionRepository.cs:104 — ProjectionRepository.SaveAsync has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) src/Elders.Cronus/PublisherBase.cs:288 — src/Elders.Cronus/PublisherBase.cs:288-307 | src/Elders.Cronus/PublisherBase.cs:322-341 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Elders.Cronus/PublisherBase.cs:288` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) src/Elders.Cronus/Projections/ProjectionRepository.cs:79 — src/Elders.Cronus/Projections/ProjectionRepository.cs:79-92 | src/Elders.Cronus/Projections/ProjectionRepository.cs:133-146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Elders.Cronus/Projections/ProjectionRepository.cs:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 4) · ×1
  • Duplicated block (17 lines × 4) src/Elders.Cronus/EventStore/AutoUpdater/Events/AutoUpdateFailed.cs:21 — src/Elders.Cronus/EventStore/AutoUpdater/Events/AutoUpdateFailed.cs:21-37 | src/Elders.Cronus/EventStore/AutoUpdater/Events/AutoUpdateFinished.cs:20-36 | src/Elders.Cronus/EventStore/AutoUpdater/Events/AutoUpdateRequested.cs:21-37 | src/Elders.Cronus/EventStore/AutoUpdater/Events/AutoUpdateTriggered.cs:21-37 — before extracting anything, compare `src/Elders.Cronus/EventStore/AutoUpdater/Events/AutoUpdateFailed.cs` and `src/Elders.Cronus/EventStore/AutoUpdater/Events/AutoUpdateFinished.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:18 — src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:18-30 | src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:65-76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:18` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:15` calls `CronusHostOptions`, `GetSection`, `Bind` and `src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:64` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:192 — src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:192-201 | src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:175-184 — before extracting anything, compare `src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs` and `src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:173` calls `OnReplayCompletedAsync`, `ConfigureAwait` and `src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:190` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) src/Elders.Cronus/Userfull/LateBoundMethod.cs:14 — src/Elders.Cronus/Userfull/LateBoundMethod.cs:14-22 | src/Elders.Cronus/Userfull/LateBoundMethod.cs:34-42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) src/Elders.Cronus/Projections/Versioning/Commands/FixProjectionVersion.cs:25 — src/Elders.Cronus/Projections/Versioning/Commands/FixProjectionVersion.cs:25-35 | src/Elders.Cronus/Projections/Versioning/Commands/NewProjectionVersion.cs:25-35 | src/Elders.Cronus/Projections/Versioning/Commands/RegisterProjection.cs:26-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Elders.Cronus/Projections/Versioning/Commands/RegisterProjection.cs:23` calls `ReplayEventsOptions` and `src/Elders.Cronus/Projections/Versioning/Commands/FixProjectionVersion.cs:22` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) src/Elders.Cronus/Projections/Versioning/Events/ProjectionVersionRequestTimedout.cs:19 — src/Elders.Cronus/Projections/Versioning/Events/ProjectionVersionRequestTimedout.cs:19-29 | src/Elders.Cronus/Projections/Versioning/Events/ProjectionVersionRequested.cs:21-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Elders.Cronus/Projections/Versioning/Events/ProjectionVersionRequested.cs:33` calls `DataMember` and `src/Elders.Cronus/Projections/Versioning/Events/ProjectionVersionRequestTimedout.cs:31` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) src/Elders.Cronus/MessageProcessing/ApplicationServiceSubscriberWorkflow.cs:25 — src/Elders.Cronus/MessageProcessing/ApplicationServiceSubscriberWorkflow.cs:25-30 | src/Elders.Cronus/MessageProcessing/EventStoreIndexSubscriberWorkflow.cs:31-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Elders.Cronus/MessageProcessing/ApplicationServiceSubscriberWorkflow.cs:25` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:34 — src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:34-38 | src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:80-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:41` calls `RegisterMissingModels` and `src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:85` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
D9 · Test Distribution · Tests outside the analyzed solution · ×1
  • Tests outside the analyzed solution — 1 .NET test project(s) exist on disk but aren't in the .NET solution that was analyzed (e.g. Elders.Cronus.Tests.Sanity.csproj), so they aren't built or gated with the production code and can't be assessed here. If this .NET code is part of the product, add those projects to the solution or point Watchdog at a solution that includes them; if it is a client/compatibility harness beside a product written in another language, nothing is wrong here and this row can be ignored.
IC1 · Incompleteness & stubs · Skeleton type · ×1
  • Skeleton type — most members are unfinished src/Elders.Cronus.Performance/LoggingBenchmark.cs:52 — `MyLogger` has 3 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented.
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body — does nothing with its inputs src/Elders.Cronus.Performance/LoggingBenchmark.cs:59 — `LogCore` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 133 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×64
  • Orphaned file src/Elders.Cronus/Projections/ProjectionRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/PublisherBase.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/FaultHandling/RetryPolicy.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/Versioning/HashCodeUtility.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Hosting/CronusHost.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/ProjectionRepositoryWithFallback.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/ProjectionVersions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/Versioning/Handlers/ProjectionBuilder.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Discoveries/CronusHostDiscovery.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Hosting/CronusServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/EventStore/Players/ReplayPublicEvents_Job.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/EventStore/AggregateRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Hosting/SubscriberCollectionServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Workflow/DiagnosticsWorkflow.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/Rebuilding/ProjectionVersionHelper.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Projections/ProjectionVersion.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/FaultHandling/RetryStrategy.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 39 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Commented-out code · ×34
  • Commented-out code src/Elders.Cronus.Performance/LoggingBenchmark.cs:5 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus.Performance/Program.cs:4 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus.Performance/Program.cs:5 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus.Performance/Program.cs:7 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus.Performance/Program.cs:12 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/Cluster/Job/ICronusJob.cs:13 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/Cluster/Job/ICronusJob.cs:14 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/Discoveries/ProjectionPlayerDiscovery.cs:11 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/Discoveries/ProjectionPlayerDiscovery.cs:16 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:32 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:73 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:74 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:48 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:49 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:68 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:69 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:151 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/RetryingEventArgs.cs:18 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:63 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:64 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:65 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:66 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:67 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/Strategies/FixedInterval.cs:61 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Elders.Cronus/FaultHandling/Strategies/FixedInterval.cs:62 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • + 9 more in this group — see findings.md.
M4 · Documentation accuracy · README/code drift · ×9
  • README/code drift docs/cronus-framework/configuration.md:148 — docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/cronus-framework/configuration.md:148 — docs/cronus-framework/configuration.md documents the setting `Cronus:Persistence:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/cronus-framework/configuration.md:172 — docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:ReplicationFactor`, but no code or configuration file names `ReplicationFactor`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/cronus-framework/configuration.md:172 — docs/cronus-framework/configuration.md documents the setting `Cronus:Projections:Cassandra:Datacenters`, but no code or configuration file names `Datacenters`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/getting-started/quick-start/setup.md:25 — docs/getting-started/quick-start/setup.md installs the package `Cronus` (`dotnet add package Cronus`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/getting-started/quick-start/setup.md:29 — docs/getting-started/quick-start/setup.md installs the package `Cronus.Transport.RabbitMQ` (`dotnet add package Cronus.Transport.RabbitMQ`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/getting-started/quick-start/setup.md:30 — docs/getting-started/quick-start/setup.md installs the package `Cronus.Persistence.Cassandra` (`dotnet add package Cronus.Persistence.Cassandra`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/getting-started/quick-start/setup.md:31 — docs/getting-started/quick-start/setup.md installs the package `Cronus.Serialization.NewtonsoftJson` (`dotnet add package Cronus.Serialization.NewtonsoftJson`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/getting-started/quick-start/setup.md:32 — docs/getting-started/quick-start/setup.md installs the package `Microsoft.Extensions.Hosting` (`dotnet add package Microsoft.Extensions.Hosting`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X10 · Duplicated predicate · Duplicated predicate · ×5
  • Duplicated predicate src/Elders.Cronus/EventStore/AggregateRepository.cs:69 — `aggregateRoot.UncommittedEvents is null || aggregateRoot.UncommittedEvents.Any() == false` appears character-identically in 2 files — src/Elders.Cronus/EventStore/AggregateRepository.cs, src/Elders.Cronus/MessageProcessing/AggregateRepositoryAndEventPublisher.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:210 — `fromCluster.IsCompleted && fromCluster.Timestamp < fromLocal.Timestamp || fromCluster.Version < fromLocal.Version` appears character-identically in 2 files — src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs, src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:29 — `startRebuildAt.AddMinutes(5) > DateTime.UtcNow && @event.Timebox.HasExpired == false` appears character-identically in 2 files — src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs, src/Elders.Cronus/Projections/Versioning/Handlers/ProjectionBuilder.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Elders.Cronus/Projections/ProjectionVersions.cs:82 — `version.Status == ProjectionStatus.Fixing || version.Status == ProjectionStatus.New` appears character-identically in 2 files — src/Elders.Cronus/Projections/ProjectionVersions.cs, src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Elders.Cronus/Projections/Rebuilding/ProjectionVersionHelper.cs:87 — `x.IsGenericType && x.GetGenericTypeDefinition() == ieventHandler` appears character-identically in 2 files — src/Elders.Cronus/Projections/Rebuilding/ProjectionVersionHelper.cs, src/Elders.Cronus/Projections/Versioning/ProjectionHasher.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X4 · Structured logging · Interpolated log message defeats structured logging · ×4
  • Interpolated log message defeats structured logging src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs:43 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Elders.Cronus/EventStore/LoggingAggregateRepository.cs:51 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Elders.Cronus/Migrations/CronusMigrator.cs:35 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Elders.Cronus/Projections/ProjectionRepository.cs:74 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch src/Elders.Cronus/Projections/ProjectionVersions.cs:177 — `IsVersionable` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/Elders.Cronus/Projections/Versioning/MarkupInterfaceProjectionVersioningPolicy.cs:13 — `IsVersionable` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
D21 · Naming Consistency · The concept of a projection hash is named inconsistently. One field uses the generic name 'hash' while the other uses 'shuffledHash'. While 'shuffledHash' is more descriptive of the specific test scenario, 'hash' is ambiguous in a context where multiple hash-related concepts might exist, and the naming convention for the variable itself differs (simple noun vs adjective-noun). · ×1
  • The concept of a projection hash is named inconsistently. One field uses the generic name 'hash' while the other uses 'shuffledHash'. While 'shuffledHash' is more descriptive of the specific test scenario, 'hash' is ambiguous in a context where multiple hash-related concepts might exist, and the naming convention for the variable itself differs (simple noun vs adjective-noun). — Use a consistent naming pattern for hash fields, such as 'ProjectionHash' or 'Hash', and avoid abbreviating or adding context-specific adjectives unless the distinction is semantically critical to the variable's role across the codebase. If 'shuffledHash' is unique to that test, 'hash' in the other location should likely be more specific (e.g., 'OriginalHash' or 'BaseHash') to avoid ambiguity. (symbols: Elders.Cronus.Projections.When_projection_version_with_status_building_is_outside_of_the_timebox.hash, Elders.Cronus.Tests.Projections.When_projection_hash_is_calculated_and_handlers_are_shuffled.shuffledHash)
D21 · Naming Consistency · Inconsistent naming of test setup fields. The codebase uses 'context' for the setup object in some tests (e.g., `When_build_aggregate_root...`) and 'of' for the 'Because' clause in others (e.g., `When_breaking_middleware`). However, in `When_adding_a_live_version_to_a_versions_collectionth`, the field is named 'context' but appears to be a typo for 'collection' or similar, and in `When_adding_a_live_version_twice`, the 'Because' field is named 'of' while in `When_breaking_middleware` it is also 'of'. The inconsistency lies in the mix of 'context' and 'of' for BDD-style setup fields, and the typo 'collectionth' in one field name. Additionally, 'nextVersion' is used in one test while 'startingTimestamp' is used in another, which are different concepts but follow no consistent pattern for test-specific variables. · ×1
  • Inconsistent naming of test setup fields. The codebase uses 'context' for the setup object in some tests (e.g., `When_build_aggregate_root...`) and 'of' for the 'Because' clause in others (e.g., `When_breaking_middleware`). However, in `When_adding_a_live_version_to_a_versions_collectionth`, the field is named 'context' but appears to be a typo for 'collection' or similar, and in `When_adding_a_live_version_twice`, the 'Because' field is named 'of' while in `When_breaking_middleware` it is also 'of'. The inconsistency lies in the mix of 'context' and 'of' for BDD-style setup fields, and the typo 'collectionth' in one field name. Additionally, 'nextVersion' is used in one test while 'startingTimestamp' is used in another, which are different concepts but follow no consistent pattern for test-specific variables. — Standardize BDD test field names. Use 'context' for the setup object and 'because' or 'action' for the action being tested, rather than abbreviating to 'of'. Fix the typo 'collectionth' to 'collection' or a more descriptive name. Ensure test-specific variables like 'nextVersion' or 'startingTimestamp' are named consistently with their role (e.g., 'expectedVersion', 'initialTimestamp'). (symbols: Elders.Cronus.Projections.When_adding_a_live_version_to_a_versions_collectionth.context, Elders.Cronus.Tests.When_build_aggregate_root_from_history_without_the_initial_event.context, Elders.Cronus.Tests.When__SingletonPerTenantContainer__is_used.context, Elders.Cronus.Tests.ValidatorsAndResolvers.When_comparing_two__IntegrityRules__are_identical.context, Elders.Cronus.Tests.Middleware.When_breaking_middleware.of, Elders.Cronus.Projections.When_adding_a_live_version_twice.of, Elders.Cronus.Tests.Projections.When_comparing_lt_projection_version_with_same_revisions.of, Elders.Cronus.Projections.When_adding_a_canceled_version.should_not_be__canceled__.of, Elders.Cronus.Projections.When_switching_a_projection_to_non_versionable1.should_not_be__outdated__.of, Elders.Cronus.Tests.Projections.When_comparing_gt_projection_version_with_different_hashes.should_be_able_to_compare_with_gt.of, Elders.Cronus.Tests.Projections.When_comparing_lt_projection_version_with_different_hashes.should_be_able_to_compare_with_lt.of, Elders.Cronus.Tests.Middleware.When_transfering_to_another_middleware.thirdToken, Elders.Cronus.Tests.Middleware.TestMiddleware.token, Elders.Cronus.Tests.InMemoryEventStoreSuite.When_loading_aggregate_root_from_event_store.should_instansiate_aggregate_root.context, Elders.Cronus.Projections.When_adding_a_live_version_twice.nextVersion, Elders.Cronus.Projections.Rebuilding.ProgressTracker.startingTimestamp, Elders.Cronus.Projections.Rebuilding.RebuildProjection_Job.signalPublisher, Elders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job.projectionVersionHelper, Elders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job.player, Elders.Cronus.Projections.Versioning.ProjectionHasher.hashCache, Elders.Cronus.Projections.Versioning.ProjectionVersionHelper.HasReplayTimeout, Elders.Cronus.Projections.Versioning.PauseProjectionVersion.Id, Elders.Cronus.Projections.Versioning.PauseProjectionVersion.ToString, Elders.Cronus.Projections.Versioning.ProjectionVersionRequested.Version, Elders.Cronus.Projections.Versioning.ProjectionVersionRequestCanceled.Timestamp, Elders.Cronus.Projections.Versioning.ProjectionVersionRequestHeartbeat.Tenant, Elders.Cronus.Projections.Versioning.ProjectionVersionRequestPaused.HandleAsync, Elders.Cronus.Projections.Versioning.ProjectionVersionManagerAppService.HandleAsync, Elders.Cronus.Projections.Versioning.TimeoutProjectionVersionRequest.HandleAsync, Elders.Cronus.Projections.Versioning.VersionRequestTimebox, Elders.Cronus.Projections.Versioning.NewProjectionVersion.IsNowLive, Elders.Cronus.Projections.Versioning.NewProjectionVersion.ReplayEventsOptions, Elders.Cronus.Projections.Versioning.CancelProjectionVersionRequest.Version, Elders.Cronus.Projections.Versioning.PauseProjectionVersion.Id, Elders.Cronus.Projections.Versioning.PauseProjectionVersion.ToString, Elders.Cronus.Projections.Versioning.ProjectionVersionRequested.Version, Elders.Cronus.Projections.Versioning.ProjectionVersionRequestCanceled.Timestamp, Elders.Cronus.Projections.Versioning.ProjectionVersionRequestHeartbeat.Tenant, Elders.Cronus.Projections.Versioning.ProjectionVersionRequestPaused.HandleAsync, Elders.Cronus.Projections.Versioning.ProjectionVersionManagerAppService.HandleAsync, Elders.Cronus.Projections.Versioning.TimeoutProjectionVersionRequest.HandleAsync, Elders.Cronus.Projections.Versioning.VersionRequestTimebox, Elders.Cronus.Projections.Versioning.NewProjectionVersion.IsNowLive, Elders.Cronus.Projections.Versioning.NewProjectionVersion.ReplayEventsOptions, Elders.Cronus.Projections.Versioning.CancelProjectionVersionRequest.Version)
D24 · Comment Value · redundant comment · ×1
  • redundant comment src/Elders.Cronus/MessageProcessing/CronusPublisher.cs:46 — "AddTrackHeaders(Dictionary<string, string> messageHeaders, CronusMessage triggeredBy)" — keep - explains why headers are added for a specific event type
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 3 project(s) overshoot their size bounds, lowering Project Cohesion to 3.3/10. The most over is `Elders.Cronus(net8.0)` (12249 LoC, 381 public types across 32 namespaces). Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
D27 · Navigability · Pass-through layer · ×1
  • Pass-through layer src/Elders.Cronus/Discoveries/DiscoveryContext.cs:9 — DiscoveryContext: all 3 public methods forward their arguments unchanged to Assemblies and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call Assemblies directly, or give the layer a job.
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 64 of 64 significant files have no living knowledge — the codebase as a whole is dormant, not 64 separate risks. Counted over 64 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
DM9 · Scattered domain decisions · Rule about [Fixing, New] decided in 2 places · ×1
  • Rule about [Fixing, New] decided in 2 places — Elders.Cronus.Projections.ProjectionStatus's [Fixing, New] are judged in Elders.Cronus.Projections.ProjectionVersions, Elders.Cronus.Projections.Versioning.ProjectionVersionManager — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
M1 · Documentation (README) · Thin README · ×1
  • Thin README — The root README is 119 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — 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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — 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.
P10 · Library API & versioning · Large public API surface · ×1
  • Large public API surface — 762/798 types (95%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P10 · Library API & versioning · No explicit versioning · ×1
  • No explicit versioning — No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 867 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.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 9/57 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ad65e3d0e62f4ff2bacd9c53e11af909/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ad65e3d0e62f4ff2bacd9c53e11af909/tree.json --exit-code 0 --source .0artifacts/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .3artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list src/Elders.Cronus.sln package --vulnerable --include-transitive --format json3artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—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 Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1612f-9a83-7def-b104-f8a86696141d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 325 · Warnings: 192 · Recommendations: 133 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 01:17 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md