Public report of reactiveui/Akavache, published 16 November 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert 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, 16 November 2026, 22:17 UTC · Survey ID cd_f55f177530e34e2abca61784bf7c49f0
reactiveui/Akavache
Measured 16 November 2026, 22:16 UTC, at code version 1ae4758
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
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.
A medium codebase: 20,757 lines of product code in 246 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Maturity, 51.5
Findings by how serious they are
30 critical202 serious68 minor
6 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 22:16 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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work 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 ▸
55of 55 dimensions measured by tools.
288of 300 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
55dimensions across 6 lenses, read from 20,757 lines of product code in 246 projects.
reactiveui/Akavache falls short of our standard for production, in part because the documentation refers to four things that don't exist. It scores 59.6 out of 100 and is rated Adequate, and nine of its 30 critical findings are security problems in the build pipeline.
Maturity, at 51.5, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6.7 points. Bringing the documentation in line with the code comes next, worth about 6.5 points. Raising Maturity to 70 would lift the score to about 66.2.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk. The 15 analysis rules switched off in the settings need switching back on in the settings file.
The product code is 20,757 lines, about €82,000 to rebuild.
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 forThe 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.
If Maturity rose from 51.5 to 70, the lowest score rated Strong, the score would rise from 59.6 to about 66.2.
Code composition: what the lines of code are
Business logic 8%Supporting code 14%Tests 79%
Rebuild cost: about €82,000 · Estimate
Cost to rebuild
€27,000 to €140,000, for 453 to 1,440 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 20,757 lines of product code, of which 37% is declarations and boilerplate, 27% straight logic and 36% logic with branches
Comment lines
The estimate prices 13,287 lines. Comment lines count towards the size of 20,757 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price 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
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.
Reconcile the README with reality: docs/BENCHMARK_REPORT.md names .NET 9, but the projects target .NET 10, 11; docs/installation.md names .NET 8, but the projects target .NET 10, 11; docs/performance.md names .NET 9, but the projects target .NET 10, 11; docs/platform-notes.md names .NET 9, but the projects target .NET 10, 11.
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with SqliteBlobCache.cs, SqlitePclRawConnection.cs.
Raises the score by about 2.1 points · Low effort · Explicit Debt
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 €82,000 to build again, about 0.6 person-years of work. Its weakest lens is Maturity, at 51.5 (Adequate). 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
Record your significant design decisions. Of all the actions in this report, it raises the score most for the work it takes: about 6.7 points for medium effort. 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, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
27 modules, with 24 dependencies between them. 2 loops run through 4 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.
Akavache.Reactive.Settings uses Akavache.Reactive.Settings.Core, so a change to Akavache.Reactive.Settings.Core can break Akavache.Reactive.Settings, while a change to Akavache.Reactive.Settings can't break Akavache.Reactive.Settings.Core.
Position
Below the diagonal: Akavache.Reactive.Settings uses a module listed above it, which is the healthy direction.
Akavache.Settings uses Akavache.Settings.Core, so a change to Akavache.Settings.Core can break Akavache.Settings, while a change to Akavache.Settings can't break Akavache.Settings.Core.
Position
Below the diagonal: Akavache.Settings uses a module listed above it, which is the healthy direction.
Akavache.Core uses Akavache.Settings, so a change to Akavache.Settings can break Akavache.Core, while a change to Akavache.Core can't break Akavache.Settings.
Position
Below the diagonal: Akavache.Core uses a module listed above it, which is the healthy direction.
Akavache.Reactive.Core uses Akavache.Reactive.Settings, so a change to Akavache.Reactive.Settings can break Akavache.Reactive.Core, while a change to Akavache.Reactive.Core can't break Akavache.Reactive.Settings.
Position
Below the diagonal: Akavache.Reactive.Core uses a module listed above it, which is the healthy direction.
15→17 Akavache.Reactive.Core uses Akavache.Reactivepart of a loop✕
Connections
12 pairs of types, where a type in Akavache.Reactive.Core uses a type in Akavache.Reactive.
Akavache.Reactive.Core uses Akavache.Reactive, so a change to Akavache.Reactive can break Akavache.Reactive.Core, while a change to Akavache.Reactive.Core can't break Akavache.Reactive.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Akavache.Reactive uses Akavache.Reactive.Settings, so a change to Akavache.Reactive.Settings can break Akavache.Reactive, while a change to Akavache.Reactive can't break Akavache.Reactive.Settings.
Position
Below the diagonal: Akavache.Reactive uses a module listed above it, which is the healthy direction.
Akavache.Reactive uses Akavache.Reactive.Core, so a change to Akavache.Reactive.Core can break Akavache.Reactive, while a change to Akavache.Reactive can't break Akavache.Reactive.Core.
Position
Below the diagonal: Akavache.Reactive uses a module listed above it, which is the healthy direction.
Akavache.EncryptedSqlite3 uses Akavache.Core.Observables, so a change to Akavache.Core.Observables can break Akavache.EncryptedSqlite3, while a change to Akavache.EncryptedSqlite3 can't break Akavache.Core.Observables.
Position
Below the diagonal: Akavache.EncryptedSqlite3 uses a module listed above it, which is the healthy direction.
Akavache.EncryptedSqlite3 uses Akavache, so a change to Akavache can break Akavache.EncryptedSqlite3, while a change to Akavache.EncryptedSqlite3 can't break Akavache.
Position
Below the diagonal: Akavache.EncryptedSqlite3 uses a module listed above it, which is the healthy direction.
Akavache.NewtonsoftJson uses Akavache, so a change to Akavache can break Akavache.NewtonsoftJson, while a change to Akavache.NewtonsoftJson can't break Akavache.
Position
Below the diagonal: Akavache.NewtonsoftJson uses a module listed above it, which is the healthy direction.
Akavache.Reactive.Drawing uses Akavache.Reactive, so a change to Akavache.Reactive can break Akavache.Reactive.Drawing, while a change to Akavache.Reactive.Drawing can't break Akavache.Reactive.
Position
Below the diagonal: Akavache.Reactive.Drawing uses a module listed above it, which is the healthy direction.
Akavache.Reactive.EncryptedSqlite3 uses Akavache.Reactive.Core.Observables, so a change to Akavache.Reactive.Core.Observables can break Akavache.Reactive.EncryptedSqlite3, while a change to Akavache.Reactive.EncryptedSqlite3 can't break Akavache.Reactive.Core.Observables.
Position
Below the diagonal: Akavache.Reactive.EncryptedSqlite3 uses a module listed above it, which is the healthy direction.
Akavache.Reactive.EncryptedSqlite3 uses Akavache.Reactive, so a change to Akavache.Reactive can break Akavache.Reactive.EncryptedSqlite3, while a change to Akavache.Reactive.EncryptedSqlite3 can't break Akavache.Reactive.
Position
Below the diagonal: Akavache.Reactive.EncryptedSqlite3 uses a module listed above it, which is the healthy direction.
Akavache.Reactive.NewtonsoftJson uses Akavache.Reactive, so a change to Akavache.Reactive can break Akavache.Reactive.NewtonsoftJson, while a change to Akavache.Reactive.NewtonsoftJson can't break Akavache.Reactive.
Position
Below the diagonal: Akavache.Reactive.NewtonsoftJson uses a module listed above it, which is the healthy direction.
Akavache.Reactive.Sqlite3 uses Akavache.Reactive.Core.Observables, so a change to Akavache.Reactive.Core.Observables can break Akavache.Reactive.Sqlite3, while a change to Akavache.Reactive.Sqlite3 can't break Akavache.Reactive.Core.Observables.
Position
Below the diagonal: Akavache.Reactive.Sqlite3 uses a module listed above it, which is the healthy direction.
Akavache.Reactive.Sqlite3 uses Akavache.Reactive, so a change to Akavache.Reactive can break Akavache.Reactive.Sqlite3, while a change to Akavache.Reactive.Sqlite3 can't break Akavache.Reactive.
Position
Below the diagonal: Akavache.Reactive.Sqlite3 uses a module listed above it, which is the healthy direction.
Akavache.Reactive.SystemTextJson uses Akavache.Reactive, so a change to Akavache.Reactive can break Akavache.Reactive.SystemTextJson, while a change to Akavache.Reactive.SystemTextJson can't break Akavache.Reactive.
Position
Below the diagonal: Akavache.Reactive.SystemTextJson uses a module listed above it, which is the healthy direction.
Akavache.Sqlite3 uses Akavache.Core.Observables, so a change to Akavache.Core.Observables can break Akavache.Sqlite3, while a change to Akavache.Sqlite3 can't break Akavache.Core.Observables.
Position
Below the diagonal: Akavache.Sqlite3 uses a module listed above it, which is the healthy direction.
Akavache.SystemTextJson uses Akavache, so a change to Akavache can break Akavache.SystemTextJson, while a change to Akavache.SystemTextJson can't break Akavache.
Position
Below the diagonal: Akavache.SystemTextJson uses a module listed above it, which is the healthy direction.
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 category
Findings
Severity
A05:2025 — Injection
9
High / Critical
A03:2025 — Software Supply Chain Failures
4
Medium
Roadmap
Top priorities: 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; Reconcile the README with reality: docs/BENCHMARK_REPORT.md names .NET 9, but the projects target .NET 10, 11; docs/installation.md names .NET 8, but the projects target .NET 10, 11; docs/performance.md names .NET 9, but the projects target .NET 10, 11; docs/platform-notes.md names .NET 9, but the projects target .NET 10, 11; Resolve the 12 redundant comment finding(s) in Comment Value — start with CoreUtilityTests.cs (2), UniversalSerializer.cs, NewtonsoftSerializer.cs.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
Reconcile the README with reality: docs/BENCHMARK_REPORT.md names .NET 9, but the projects target .NET 10, 11; docs/installation.md names .NET 8, but the projects target .NET 10, 11; docs/performance.md names .NET 9, but the projects target .NET 10, 11; docs/platform-notes.md names .NET 9, but the projects target .NET 10, 11.
Test Quality: No assertions: UpdateExpirationWithTypeShouldNoopWhenKeyMissing
REDACTED
7.2
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
7.2
Mixed
Static Analysis (SAST): High: REDACTED
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 — 30
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 — 202
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 — 68
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 6
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 55 dimensions across the health lenses
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
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, 288 of 300 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.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry), so no test ever ran. This is OUR limitation, not a defect in the repo — it is excluded from the score. We track the analyzer-image gap so it can be closed.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. License scan produced no result — the tool ran but wrote no JSON report (no package reference resolved); the offline NuGet fallback resolved nothing.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/Akavache.Core/Akavache.csproj' with message: The target platform identifier android was not recognized.
D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (20,757 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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"]`.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Akavache.Core/AkavacheBuilderExtensions.cs`, `src/Akavache.Core/AkavacheSqliteException.cs`, `src/Akavache.Core/CacheDatabase.cs`, `src/Akavache.Core/CacheEntry.cs`, `src/Akavache.Core/CheckpointMode.cs`, … (+100 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (src/samples/AkavacheTodoWpf/App.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/samples/AkavacheTodoMaui/AkavacheTodoMaui.csproj, src/samples/AkavacheTodoWpf/AkavacheTodoWpf.csproj, src/benchmarks/Akavache.Benchmarks/Akavache.Benchmarks.csproj, src/tests/Akavache.Core.Tests/Akavache.Core.Tests.csproj, src/tests/Akavache.Core.Tests.Parallel/Akavache.Core.Tests.Parallel.csproj and 38 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
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").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
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.
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.
0 method(s) exceeded the cognitive complexity threshold of 15.
✓ On the Gold path — maintain.
Detailed fixes: d2_recommendation.md.
Do you agree with this assessment?
D3 · God Classes8.7 / 10Strong✓ 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.
Resolve the 6 TooManyMethods finding(s) in God Classes — start with InMemoryBlobCacheBase.cs, SqliteBlobCache.cs, SqlitePclRawConnection.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with SqlitePclRawConnection.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
30 duplicated block group(s) detected. 6.4 % of the production lines (1,325 of 20,757) are in a reported copy. A further 40 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 33 of the 70 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 35 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with AkavacheBuilderExtensions.cs (6), SqliteBlobCache.cs (2). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with SettingsStorage.cs, AkavacheBuilderExtensions.cs, MainViewModel.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with AkavacheBuilderExtensions.cs, MainViewModel.cs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.9 / 10Stronggated by 2 serious findings✓ 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.
Off the main sequence: Akavache(net10.0) · ×2src/Akavache.Core/Akavache.csproj:1
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling — start with Akavache.csproj, Akavache.Reactive.csproj. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with AkavacheBuilder.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.7 / 10Stronggated by 70 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 40 zero-assertion, 1 racing the wall clock, 33 whose failure is swallowed by a catch-all, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2096 tests.
No assertions: Subscribe_RaceFailDuringTryPark_DeliversErrorViaSubscribeAfterPark · ×36src/tests/Akavache.Core.Tests.Parallel/GatedByInitObservableTests.cs:585
Test cannot fail: InMemoryBlobCache_HighVolumeStressTest_ShouldNotThrowIndexOutOfRangeException · ×33src/tests/Akavache.Core.Tests.Parallel/ConcurrencyTests.cs:114
Races the wall clock: DateTimeSerializationEdgeCasesShouldBeHandledCorrectlysrc/tests/shared/TestBases/DateTimeTestBase.cs:165
What to do
Resolve the 36 No assertions finding(s) in Test Quality — start with HttpServiceTests.cs (5), SqliteOperationQueueTests.cs (5), InMemoryBlobCacheBaseTests.cs (4). — One of this dimension's main actionable groups (36 warning-level).
Resolve the 33 Test cannot fail finding(s) in Test Quality — start with BitmapImageExtensionsTests.cs (8), ImageCacheExtensionsTests.cs (7), RelativeTimeExtensionsTests.cs (5). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 1 Races the wall clock finding(s) in Test Quality — start with DateTimeTestBase.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
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.
No source file's living knowledge is concentrated in a single author. Counted over 60 of the 97 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
45 deducted debt markers + unmeasured dead symbols across 20757 LoC in the .NET projects (1.3/KLoC) → score 7.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (15). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with SqliteBlobCache.cs, SqlitePclRawConnection.cs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
246 projects, 6562 source files, 68351 hand-written lines of code (20757 production / 47594 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), 449 inter-project edges (build status unknown — did not finish).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×15src/Akavache.Core/AkavacheBuilderExtensions.cs:110
What to do
Resolve the 12 redundant comment finding(s) in Comment Value — start with CoreUtilityTests.cs (2), UniversalSerializer.cs, NewtonsoftSerializer.cs. — One of this dimension's main actionable groups (12 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
0 of 43 projects flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
D27 · Navigability6.5 / 10Adequate✓ 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.
63 % of calls cross a namespace and 14 % go through an interface, but 66 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.
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.
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).
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 108 file(s) — `src/Akavache.Core/AkavacheBuilderExtensions.cs` (lines 11–13), `src/Akavache.Core/AkavacheSqliteException.cs` (lines 6–8), `src/Akavache.Core/CacheDatabase.cs` (lines 9–11, lines 109–121), `src/Akavache.Core/CacheEntry.cs` (lines 6–8), `src/Akavache.Core/CheckpointMode.cs` (lines 6–8), … (+103 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 14 of those file(s) — `src/Akavache.Core/Core/Observables/FirstMatchFromCandidatesObservable.cs`, `src/Akavache.Core/Core/Observables/GatedByInitObservable.cs`, `src/Akavache.Core/Core/Observables/SelectConstantObservable.cs`, `src/Akavache.Core/InMemoryBlobCache.cs`, `src/Akavache.Core/InMemoryBlobCacheBase.cs`, … (+9 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
REDACTED
What to do
No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 60 of the 97 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 43 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.
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.
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.
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.
`NotificationService` is a singleton (one shared instance) but mutates instance state outside any lock (_currentSettings, _disposed; e.g. `_currentSettings` at line 142). — src/samples/AkavacheTodoMaui/Services/NotificationService.cs:12
`NotificationService` is a singleton (one shared instance) but mutates instance state outside any lock (_currentSettings; e.g. `_currentSettings` at line 211). — src/samples/AkavacheTodoWpf/Services/NotificationService.cs:15
`AkavacheBuilderExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_sqliteProvider; e.g. `_sqliteProvider` at line 45). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:14
`AkavacheBuilderExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_sqliteProvider; e.g. `_sqliteProvider` at line 46). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs:14
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
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 Akavache ↔ Akavache.Core depend on each other. The lightest dependency in the cycle is Akavache → Akavache.Core (Akavache.CacheDatabase → Akavache.Core.FileLocationOption, 2 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/Akavache.Core/CacheDatabase.cs:19
The namespaces Akavache.Reactive ↔ Akavache.Reactive.Core depend on each other. The lightest dependency in the cycle is Akavache.Reactive → Akavache.Reactive.Core (Akavache.Reactive.CacheDatabase → Akavache.Reactive.Core.FileLocationOption, 2 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/Akavache.Core/CacheDatabase.cs:19
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.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
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.
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.
`IBlobCache` declares 35 members under just 13 distinct name(s): `Serializer`, `Scheduler`, `ForcedDateTimeKind`, `Insert`, `Insert`, `Insert`, `Insert`, `Insert`, `Insert`, `Insert`, `Insert`, `Get`, `Get`, `Get`, `Get`, `GetAll`, `GetAllKeys`, `GetAllKeys`, `GetCreatedAt`, `GetCreatedAt`, `GetCreatedAt`, `GetCreatedAt`, `Flush`, `Flush`, `Invalidate`, `Invalidate`, `Invalidate`, `Invalidate`, `InvalidateAll`, `InvalidateAll`, `Vacuum`, `UpdateExpiration`, `UpdateExpiration`, `UpdateExpiration`, `UpdateExpiration`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 35 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 35 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/Akavache.Core/IBlobCache.cs:15
`IHttpService` declares 24 members under just 1 distinct name(s): `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 24 separate responsibilities: a caller binds to 1 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 24 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/Akavache.HttpDownloader/IHttpService.cs:16
What to do
Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
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.
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
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.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
docs/BENCHMARK_REPORT.md names .NET 9, but the projects target .NET 10, 11. 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/BENCHMARK_REPORT.md:21
docs/installation.md names .NET 8, but the projects target .NET 10, 11. 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/installation.md:45
docs/performance.md names .NET 9, but the projects target .NET 10, 11. 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/performance.md:78
docs/platform-notes.md names .NET 9, but the projects target .NET 10, 11. 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/platform-notes.md:7
What to do
Reconcile the README with reality: docs/BENCHMARK_REPORT.md names .NET 9, but the projects target .NET 10, 11; docs/installation.md names .NET 8, but the projects target .NET 10, 11; docs/performance.md names .NET 9, but the projects target .NET 10, 11; docs/platform-notes.md names .NET 9, but the projects target .NET 10, 11.
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.
Do you agree with this assessment?
P10 · Library API & versioning9.9 / 10Exemplary✓ 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's code 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.
`Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net10.0-android)`, `Akavache.EncryptedSqlite3.Reactive(net10.0-android)`, `Akavache.HttpDownloader.Reactive(net10.0-android)`, `Akavache.NewtonsoftJson.Reactive(net10.0-android)`, `Akavache.Sqlite3.Reactive(net10.0-android)`, `Akavache.SystemTextJson.Reactive(net10.0-android)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Akavache.Core/InMemoryBlobCache.cs:23
`Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net47)`, `Akavache.EncryptedSqlite3.Reactive(net47)`, `Akavache.HttpDownloader.Reactive(net47)`, `Akavache.NewtonsoftJson.Reactive(net47)`, `Akavache.Sqlite3.Reactive(net47)`, `Akavache.SystemTextJson.Reactive(net47)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Akavache.Core/InMemoryBlobCache.cs:23
`Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net471)`, `Akavache.EncryptedSqlite3.Reactive(net471)`, `Akavache.HttpDownloader.Reactive(net471)`, `Akavache.NewtonsoftJson.Reactive(net471)`, `Akavache.Sqlite3.Reactive(net471)`, `Akavache.SystemTextJson.Reactive(net471)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Akavache.Core/InMemoryBlobCache.cs:23
`Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net472)`, `Akavache.EncryptedSqlite3.Reactive(net472)`, `Akavache.HttpDownloader.Reactive(net472)`, `Akavache.NewtonsoftJson.Reactive(net472)`, `Akavache.Sqlite3.Reactive(net472)`, `Akavache.SystemTextJson.Reactive(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Akavache.Core/InMemoryBlobCache.cs:23
`Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net48)`, `Akavache.EncryptedSqlite3.Reactive(net48)`, `Akavache.HttpDownloader.Reactive(net48)`, `Akavache.NewtonsoftJson.Reactive(net48)`, `Akavache.Sqlite3.Reactive(net48)`, `Akavache.SystemTextJson.Reactive(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Akavache.Core/InMemoryBlobCache.cs:23
`Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net481)`, `Akavache.EncryptedSqlite3.Reactive(net481)`, `Akavache.HttpDownloader.Reactive(net481)`, `Akavache.NewtonsoftJson.Reactive(net481)`, `Akavache.Sqlite3.Reactive(net481)`, `Akavache.SystemTextJson.Reactive(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Akavache.Core/InMemoryBlobCache.cs:23
`Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.EncryptedSqlite3.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.HttpDownloader.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.NewtonsoftJson.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.Sqlite3.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.SystemTextJson.Reactive(net10.0-windows10.0.19041.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Akavache.Core/InMemoryBlobCache.cs:23
`Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.EncryptedSqlite3.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.HttpDownloader.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.NewtonsoftJson.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.Sqlite3.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.SystemTextJson.Reactive(net11.0-windows10.0.19041.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Akavache.Core/InMemoryBlobCache.cs:23
What to do
Make `Akavache.Reactive.InMemoryBlobCache` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `Akavache.Reactive.InMemoryBlobCache` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `Akavache.Reactive.InMemoryBlobCache` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `Akavache.Reactive.InMemoryBlobCache` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `Akavache.Reactive.InMemoryBlobCache` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `Akavache.Reactive.InMemoryBlobCache` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `Akavache.Reactive.InMemoryBlobCache` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `Akavache.Reactive.InMemoryBlobCache` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
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.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
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.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
a CREATE TABLE statement here creates the schema at runtime, and this repository keeps no migration history — there's no upgrade path for an existing production database. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` or a migrations bundle) so schema changes are versioned and applied safely. — src/Akavache.Sqlite3/SqlitePclRawConnection.cs:43
What to do
Adopt a versioned schema-migration mechanism (DbUp, FluentMigrator, Evolve, EF Core migrations) and create every table in a migration, so the production schema can evolve safely and reproducibly.
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.
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 each language's code 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).
`_workerExited.Wait()` 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/Akavache.Sqlite3/SqliteOperationQueue.cs:286, src/Akavache.Sqlite3/SqliteOperationQueue.cs:301
Only 3/6 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
`await using … = ReadOnlyMemoryStreamCompat.OpenRead(compressedImage)` 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/Akavache.Drawing/BitmapBufferExtensions.cs:37, src/Akavache.Drawing/BitmapBufferExtensions.cs:52
`await using … = new(InitialCapacity)` 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/Akavache.Drawing/BitmapImageExtensions.cs:39
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
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.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×2) — src/samples/AkavacheTodoMaui/App.xaml.cs:72, src/samples/AkavacheTodoWpf/MainWindow.xaml.cs:60
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.
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.
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.
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 0/16 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. (×16) — src/Akavache.Core/Settings/SettingsStorageAsyncExtensions.cs:27, src/Akavache.Core/UniversalSerializer.cs:200, src/Akavache.Settings/AkavacheBuilderAsyncExtensions.cs:44, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
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.
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×4) — src/Akavache.Core/Core/Observables/FirstMatchFromCandidatesObservable.cs:85, src/Akavache.Core/Core/Observables/FirstMatchFromCandidatesObservable.cs:120, src/Akavache.Core/Core/Observables/FirstMatchFromCandidatesObservable.cs:234, …
`catch (ArgumentOutOfRangeException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Akavache.Core/Helpers/DateTimeHelpers.cs:209
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). — src/Akavache.Sqlite3/SqliteBlobCache.cs:846
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. — src/Akavache.Sqlite3/SqlitePclRawConnection.cs:1082
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.
~0.9 `!` suppressions per 1k syntax nodes — 65 suppression(s) across the 70132 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
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.
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.
P12 CI test-gate honesty — 2 observation(s) recorded · 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.
X10 Duplicated predicate — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 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 — 57 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.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — 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.
D11 Test Reliability — Test reliability not measured — analyzer environment
D12 Dependency Hygiene — Dependency hygiene not measured
D14 License Compliance — Licence collector did not produce a result
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.
D21 Naming Consistency — N/A — too few peers to establish a naming convention (5767 declarations, no unit with a dominant convention).
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
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) — 105 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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 — analyzer environment
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
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.
AnalyzerSeverityNone .editorconfig:25— S108 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:26— S1117 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:27— S1133 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:28— S1450 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:29— S2436 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:30— S2589 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:31— S3011 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:32— S3236 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:33— S3267 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:34— S3358 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:35— S3776 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:36— S4136 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:37— S8969 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:799— IDE0011 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:824— IDE0280 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
Namespace dependency cycle src/Akavache.Core/CacheDatabase.cs:19— The namespaces Akavache ↔ Akavache.Core depend on each other. The lightest dependency in the cycle is Akavache → Akavache.Core (Akavache.CacheDatabase → Akavache.Core.FileLocationOption, 2 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/Akavache.Core/CacheDatabase.cs:19— The namespaces Akavache.Reactive ↔ Akavache.Reactive.Core depend on each other. The lightest dependency in the cycle is Akavache.Reactive → Akavache.Reactive.Core (Akavache.Reactive.CacheDatabase → Akavache.Reactive.Core.FileLocationOption, 2 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.
EmptyCatchBlock src/Akavache.Sqlite3/SqliteBlobCache.cs:846— 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/Akavache.Sqlite3/SqlitePclRawConnection.cs:1082— 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.
NoWarnInCsproj src/Directory.Build.props:140— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Directory.Build.props:140— CA1812 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
No assertions: Subscribe_RaceFailDuringTryPark_DeliversErrorViaSubscribeAfterPark src/tests/Akavache.Core.Tests.Parallel/GatedByInitObservableTests.cs:585— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldFlush src/tests/Akavache.Core.Tests.Parallel/Sqlite3SecureBlobCacheWrapperTests.cs:219— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldVacuum src/tests/Akavache.Core.Tests.Parallel/Sqlite3SecureBlobCacheWrapperTests.cs:238— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldUpdateExpiration src/tests/Akavache.Core.Tests.Parallel/Sqlite3SecureBlobCacheWrapperTests.cs:256— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: UpdateExpirationWithTypeShouldNoopWhenKeyMissing src/tests/Akavache.Core.Tests/InMemoryBlobCacheBaseTests.cs:1040— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: UpdateExpirationShouldNoopWhenKeyMissing src/tests/Akavache.Core.Tests/InMemoryBlobCacheBaseTests.cs:1067— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: UpdateExpirationKeysShouldNoopWhenKeysMissing src/tests/Akavache.Core.Tests/InMemoryBlobCacheBaseTests.cs:1079— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: UpdateExpirationKeysWithTypeShouldNoopWhenKeysMissing src/tests/Akavache.Core.Tests/InMemoryBlobCacheBaseTests.cs:1089— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: RequestCacheShouldNotGrowUnbounded src/tests/Akavache.Core.Tests/RequestCacheTests.cs:383— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldFlush src/tests/Akavache.Core.Tests/SecureBlobCacheWrapperTests.cs:202— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldUpdateExpiration src/tests/Akavache.Core.Tests/SecureBlobCacheWrapperTests.cs:219— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: FlushShouldWork src/tests/Akavache.EncryptedSqlite3.Tests.Parallel/EncryptedSqliteBlobCacheDirectTests.cs:455— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: EncryptedDisposeTolerantOfAllTeardownFailures src/tests/Akavache.EncryptedSqlite3.Tests.Parallel/EncryptedSqliteBlobCacheTests.cs:428— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShutdownAndWait_FireAndForget_CompletesCleanly src/tests/Akavache.EncryptedSqlite3.Tests.Parallel/EncryptedSqliteOperationQueueCoverageTests.cs:227— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Dispose_MultipleSequential_IsIdempotent src/tests/Akavache.EncryptedSqlite3.Tests.Parallel/EncryptedSqliteOperationQueueCoverageTests.cs:250— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Dispose_ConcurrentViaDedicatedThreads_NoDeadlock src/tests/Akavache.EncryptedSqlite3.Tests.Parallel/EncryptedSqliteOperationQueueCoverageTests.cs:313— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: MakeWebRequestWithNullContentShouldExecuteNoContentBranch src/tests/Akavache.HttpDownloader.Tests/HttpServiceTests.cs:727— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: MakeWebRequestWithContentShouldExecuteContentBranch src/tests/Akavache.HttpDownloader.Tests/HttpServiceTests.cs:752— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: MakeWebRequestWithContentShouldAssignStringContentAndSend src/tests/Akavache.HttpDownloader.Tests/HttpServiceTests.cs:838— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: MakeWebRequestWithContentAndRetriesShouldExecuteDeferBody src/tests/Akavache.HttpDownloader.Tests/HttpServiceTests.cs:862— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: MakeWebRequestWithNullContentAndRetriesShouldExecuteDeferBody src/tests/Akavache.HttpDownloader.Tests/HttpServiceTests.cs:884— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: SecureBlobCacheWrapperShouldForwardVacuum src/tests/Akavache.Integration.Tests/AkavacheBuilderTests.cs:356— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: SecureBlobCacheWrapperShouldSupportDispose src/tests/Akavache.Integration.Tests/AkavacheBuilderTests.cs:371— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: SaveImageWithExpirationShouldWork src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:474— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: DisposeSettingsStoreAsyncShouldCompleteWhenNoneRegistered src/tests/Akavache.Settings.Tests/AkavacheBuilderAsyncExtensionsSmokeTests.cs:29— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Test cannot fail: InMemoryBlobCache_HighVolumeStressTest_ShouldNotThrowIndexOutOfRangeException src/tests/Akavache.Core.Tests.Parallel/ConcurrencyTests.cs:114— This test's act runs inside `catch (Exception)` at line 148 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. Adding an assertion inside that region does not fix it: the assertion throws, and the same catch swallows it exactly like the exception it replaced. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: TryDeserializeBsonFormatShouldHandleDateTimeWithUtcKind src/tests/Akavache.Integration.Tests/UniversalSerializerBsonFormatTests.cs:62— This test's act runs inside `catch (Exception)` at line 86 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. Adding an assertion inside that region does not fix it: the assertion throws, and the same catch swallows it exactly like the exception it replaced. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: TryDeserializeBsonFormatShouldHandleDateTimeWithLocalKind src/tests/Akavache.Integration.Tests/UniversalSerializerBsonFormatTests.cs:94— This test's act runs inside `catch (Exception)` at line 116 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. Adding an assertion inside that region does not fix it: the assertion throws, and the same catch swallows it exactly like the exception it replaced. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: TryDeserializeBsonFormatShouldHandleDateTimeWithUnspecifiedKind src/tests/Akavache.Integration.Tests/UniversalSerializerBsonFormatTests.cs:124— This test's act runs inside `catch (Exception)` at line 146 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. Adding an assertion inside that region does not fix it: the assertion throws, and the same catch swallows it exactly like the exception it replaced. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: SecurityUtilities_ShouldHandleNullAndEmptyInputs src/tests/Akavache.Core.Tests.Parallel/SecurityUtilitiesTests.cs:253— This test's act runs inside `catch (Exception)` at line 279 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 12 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: InsertShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.HttpDownloader.Tests/RelativeTimeExtensionsTests.cs:106— This test's act runs inside `catch (Exception)` at line 120 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: InsertObjectShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.HttpDownloader.Tests/RelativeTimeExtensionsTests.cs:128— This test's act runs inside `catch (Exception)` at line 142 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: DownloadUrlStringShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.HttpDownloader.Tests/RelativeTimeExtensionsTests.cs:150— This test's act runs inside `catch (Exception)` at line 167 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: DownloadUrlUriShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.HttpDownloader.Tests/RelativeTimeExtensionsTests.cs:175— This test's act runs inside `catch (Exception)` at line 189 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: SaveLoginShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.HttpDownloader.Tests/RelativeTimeExtensionsTests.cs:197— This test's act runs inside `catch (Exception)` at line 210 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: BsonSerializer_ThrowsOnCircularReference src/tests/Akavache.Integration.Tests.Parallel/BsonSerializerEdgeCaseTests.cs:48— This test's act runs inside `catch (Exception)` at line 59 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImageShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:122— This test's act runs inside `catch (Exception)` at line 134 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImageWithDimensionsShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:142— This test's act runs inside `catch (Exception)` at line 154 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImageFromUrlShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:162— This test's act runs inside `catch (Exception)` at line 178 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImageFromUrlWithUriShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:186— This test's act runs inside `catch (Exception)` at line 199 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImageFromUrlWithKeyShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:207— This test's act runs inside `catch (Exception)` at line 223 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImageFromUrlWithKeyAndUriShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:231— This test's act runs inside `catch (Exception)` at line 244 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: SaveImageShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:252— This test's act runs inside `catch (Exception)` at line 265 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: ImageToBytesShouldThrowArgumentNullExceptionWhenImageIsNull src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:287— This test's act runs inside `catch (Exception)` at line 299 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImagesShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/ImageCacheExtensionsTests.cs:113— This test's act runs inside `catch (Exception)` at line 126 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: PreloadImagesFromUrlsShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/ImageCacheExtensionsTests.cs:134— This test's act runs inside `catch (Exception)` at line 147 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImageWithFallbackShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/ImageCacheExtensionsTests.cs:155— This test's act runs inside `catch (Exception)` at line 168 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: LoadImageFromUrlWithFallbackShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/ImageCacheExtensionsTests.cs:190— This test's act runs inside `catch (Exception)` at line 204 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: CreateAndCacheThumbnailShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/ImageCacheExtensionsTests.cs:227— This test's act runs inside `catch (Exception)` at line 240 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: GetImageSizeShouldThrowArgumentNullExceptionWhenCacheIsNull src/tests/Akavache.Integration.Tests/ImageCacheExtensionsTests.cs:248— This test's act runs inside `catch (Exception)` at line 260 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
CoverageExclusion src/Akavache.Core/AkavacheBuilderExtensions.cs:147— method GetIsolatedCacheDirectory — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/AkavacheBuilderExtensions.cs:192— method GetLegacyCacheDirectory — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Helpers/ArgumentValidation.cs:20— class ArgumentValidation — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Helpers/DisposeHelper.cs:14— class DisposeHelper — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Helpers/IsolatedStorageFileExtensions.cs:30— method ResolveIsolatedCachePath — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/CallerArgumentExpressionAttribute.cs:22— class CallerArgumentExpressionAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/DoesNotReturnAttribute.cs:21— class DoesNotReturnAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/DoesNotReturnIfAttribute.cs:21— class DoesNotReturnIfAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/HashCode.cs:20— struct HashCode — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/Index.cs:26— struct Index — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/IsExternalInit.cs:23— class IsExternalInit — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/MemberNotNullAttribute.cs:10— class MemberNotNullAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/NotNullAttribute.cs:24— class NotNullAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/RequiresDynamicCodeAttribute.cs:22— class RequiresDynamicCodeAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/RequiresUnreferencedCodeAttribute.cs:24— class RequiresUnreferencedCodeAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/Akavache.Core/Polyfills/UnconditionalSuppressMessageAttribute.cs:21— class UnconditionalSuppressMessageAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
X2 · Cancellation propagation· Async method without CancellationToken · ×16
Async method without CancellationToken: InitializeAsync src/Akavache.Core/Settings/SettingsStorageAsyncExtensions.cs:27— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: TryFindDataWithAlternativeKeysAsync src/Akavache.Core/UniversalSerializer.cs:200— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteSettingsStoreAsync src/Akavache.Settings/AkavacheBuilderAsyncExtensions.cs:44— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DisposeSettingsStoreAsync src/Akavache.Settings/AkavacheBuilderAsyncExtensions.cs:67— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetOrFetchObject src/benchmarks/Akavache.Benchmarks/CacheDatabaseComprehensiveBenchmarks.cs:131— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAndFetchLatest src/benchmarks/Akavache.Benchmarks/CacheDatabaseComprehensiveBenchmarks.cs:147— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: BulkOperations src/benchmarks/Akavache.Benchmarks/CacheDatabaseComprehensiveBenchmarks.cs:383— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RandomRead src/benchmarks/Akavache.Benchmarks/CacheDatabaseReadBenchmarks.cs:135— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: BulkRead src/benchmarks/Akavache.Benchmarks/CacheDatabaseReadBenchmarks.cs:152— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: BulkGet_Plain src/benchmarks/Akavache.Benchmarks/SqliteBackendBenchmarks.cs:132— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: BulkGet_Encrypted src/benchmarks/Akavache.Benchmarks/SqliteBackendBenchmarks.cs:139— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllKeys_Plain src/benchmarks/Akavache.Benchmarks/SqliteBackendBenchmarks.cs:146— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllKeys_Encrypted src/benchmarks/Akavache.Benchmarks/SqliteBackendBenchmarks.cs:153— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnWindowDestroying src/samples/AkavacheTodoMaui/App.xaml.cs:72— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExecuteSave src/samples/AkavacheTodoMaui/ViewModels/EditTodoViewModel.cs:115— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExecuteCancel src/samples/AkavacheTodoMaui/ViewModels/EditTodoViewModel.cs:162— No CancellationToken parameter — this work can't be stopped early once started.
Duplicated block (12 lines × 2) src/Akavache.Sqlite3/SqliteBlobCache.cs:301— src/Akavache.Sqlite3/SqliteBlobCache.cs:301-312 | src/Akavache.Sqlite3/SqliteBlobCache.cs:354-365 — 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.
Duplicated block (12 lines × 2) src/Akavache.Sqlite3/SqliteBlobCache.cs:324— src/Akavache.Sqlite3/SqliteBlobCache.cs:324-340 | src/Akavache.Sqlite3/SqliteBlobCache.cs:383-394 — 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.
Duplicated block (12 lines × 2) src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36— src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36-47 | src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs:36-48 — `src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs` and `src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 78 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36— src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36-47 | src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs:36-48 — `src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs` and `src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 78 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36— src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36-47 | src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs:36-48 — `src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs` and `src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 78 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36— src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36-47 | src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs:36-48 — `src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs` and `src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 78 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36— src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36-47 | src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs:36-48 — `src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs` and `src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 78 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36— src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:36-47 | src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs:36-48 — `src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs` and `src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 78 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
TooManyMethods: InMemoryBlobCacheBase src/Akavache.Core/InMemoryBlobCacheBase.cs— TooManyMethods — 427 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EncryptedSqliteBlobCache src/Akavache.Sqlite3/SqliteBlobCache.cs— TooManyMethods — 361 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SqlitePclRawConnection src/Akavache.Sqlite3/SqlitePclRawConnection.cs— TooManyMethods — 591 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UniversalSerializer src/Akavache.Core/UniversalSerializer.cs— TooManyMethods — 355 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: HttpService src/Akavache.HttpDownloader/HttpService.cs— TooManyMethods — 163 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SecureBlobCacheWrapper src/Akavache.Core/Core/SecureBlobCacheWrapper.cs— TooManyMethods — 87 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Swallowed exception (caught, then discarded) src/Akavache.Core/Core/Observables/FirstMatchFromCandidatesObservable.cs:85— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Akavache.Core/Core/Observables/FirstMatchFromCandidatesObservable.cs:120— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Akavache.Core/Core/Observables/FirstMatchFromCandidatesObservable.cs:234— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Akavache.Core/Core/Observables/FirstMatchFromCandidatesObservable.cs:317— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Akavache.Core/Helpers/DateTimeHelpers.cs:209— `catch (ArgumentOutOfRangeException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
TodoComment src/samples/AkavacheTodoMaui/MainPage.xaml:153— <!-- Todo List --> — 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/samples/AkavacheTodoWpf/MainWindow.xaml:322— <!-- Todo List --> — 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/samples/AkavacheTodoMaui/MainPage.xaml:178— <!-- Todo Content --> — 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/samples/AkavacheTodoWpf/MainWindow.xaml:353— <!-- Todo Content --> — 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.
Awaits without ConfigureAwait(false) — Only 3/6 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
Awaits without ConfigureAwait(false) src/Akavache.Drawing/BitmapBufferExtensions.cs:37— `await using … = ReadOnlyMemoryStreamCompat.OpenRead(compressedImage)` 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/Akavache.Drawing/BitmapBufferExtensions.cs:52— `await using … = ReadOnlyMemoryStreamCompat.OpenRead(compressedImage)` 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/Akavache.Drawing/BitmapImageExtensions.cs:39— `await using … = new(InitialCapacity)` 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)`.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) src/Akavache.Settings/Core/SettingsStorage.cs:174— src/Akavache.Settings/Core/SettingsStorage.cs:174-183 | src/Akavache.Settings/Core/SettingsStorage.cs:229-240 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/Akavache.SystemTextJson.Bson/AkavacheBuilderExtensions.cs:60— src/Akavache.SystemTextJson.Bson/AkavacheBuilderExtensions.cs:60-70 | src/Akavache.SystemTextJson/AkavacheBuilderExtensions.cs:58-67 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:512— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:512-521 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:443-452 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
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/Akavache.Sqlite3/SqliteOperationQueue.cs:286— `_workerExited.Wait()` 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/Akavache.Sqlite3/SqliteOperationQueue.cs:301— `_workerExited.Wait()` 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).
Stateful singleton: NotificationService src/samples/AkavacheTodoMaui/Services/NotificationService.cs:12— `NotificationService` is a singleton (one shared instance) but mutates instance state outside any lock (_currentSettings, _disposed; e.g. `_currentSettings` at line 142).
Stateful singleton: NotificationService src/samples/AkavacheTodoWpf/Services/NotificationService.cs:15— `NotificationService` is a singleton (one shared instance) but mutates instance state outside any lock (_currentSettings; e.g. `_currentSettings` at line 211).
AX2 · Stateful singletons· Process-global static state · ×2
Process-global static state: AkavacheBuilderExtensions src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:14— `AkavacheBuilderExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_sqliteProvider; e.g. `_sqliteProvider` at line 45). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: AkavacheBuilderExtensions src/Akavache.Sqlite3/AkavacheBuilderExtensions.cs:14— `AkavacheBuilderExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_sqliteProvider; e.g. `_sqliteProvider` at line 46). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
XxxComment src/benchmarks/Akavache.Benchmarks/CacheDatabaseReadBenchmarks.cs:77— // XXX: This is an evil hack, but it's okay for a unit test — 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.
XxxComment src/tests/shared/Helpers/IntegrationTestHelper.cs:40— // XXX: This is an evil hack, but it's okay for a unit test — 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.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) src/Akavache.Settings/AkavacheBuilderExtensions.cs:336— src/Akavache.Settings/AkavacheBuilderExtensions.cs:336-353 | src/Akavache.Settings/AkavacheBuilderExtensions.cs:401-418 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:685— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:685-702 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:554-571 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) src/Akavache.NewtonsoftJson/AkavacheBuilderExtensions.cs:57— src/Akavache.NewtonsoftJson/AkavacheBuilderExtensions.cs:57-67 | src/Akavache.NewtonsoftJson/AkavacheBuilderExtensions.cs:106-117 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/samples/AkavacheTodoMaui/Services/NotificationService.cs:214— src/samples/AkavacheTodoMaui/Services/NotificationService.cs:214-224 | src/samples/AkavacheTodoWpf/Services/NotificationService.cs:308-318 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (6 lines × 3) src/Akavache.Sqlite3/SqliteBlobCache.cs:460— src/Akavache.Sqlite3/SqliteBlobCache.cs:460-465 | src/Akavache.Sqlite3/SqliteBlobCache.cs:633-638 | src/Akavache.Sqlite3/SqliteBlobCache.cs:688-693 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) src/Akavache.Sqlite3/SqliteBlobCache.cs:182— src/Akavache.Sqlite3/SqliteBlobCache.cs:182-187 | src/Akavache.Sqlite3/SqliteBlobCache.cs:228-233 | src/Akavache.Sqlite3/SqliteBlobCache.cs:252-257 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Akavache.Sqlite3/SqliteBlobCache.cs:234` calls `MaterializeKeys` and `src/Akavache.Sqlite3/SqliteBlobCache.cs:258` 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.
Duplicated block (13 lines × 2) src/Akavache.Settings/AkavacheBuilderExtensions.cs:337— src/Akavache.Settings/AkavacheBuilderExtensions.cs:337-349 | src/Akavache.Settings/AkavacheBuilderExtensions.cs:402-414 — 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.
Duplicated block (13 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:73— src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:73-85 | src/samples/AkavacheTodoWpf/ViewModels/TodoItemViewModel.cs:114-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:73` 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 (11 lines × 2) src/Akavache.Core/InMemoryBlobCacheBase.cs:76— src/Akavache.Core/InMemoryBlobCacheBase.cs:76-86 | src/Akavache.Core/InMemoryBlobCacheBase.cs:127-137 — 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/Akavache.Core/InMemoryBlobCacheBase.cs:76` 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.
Duplicated block (11 lines × 2) src/Akavache.Sqlite3/SqliteBlobCache.cs:529— src/Akavache.Sqlite3/SqliteBlobCache.cs:529-539 | src/Akavache.Sqlite3/SqliteBlobCache.cs:555-565 — 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· Edited copy of a member (41 corresponding lines) · ×2
Edited copy of a member (41 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:45— src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:45-85 | src/samples/AkavacheTodoWpf/ViewModels/TodoItemViewModel.cs:71-126 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (41 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:402— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:402-442 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:344-384 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (18 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/EditTodoViewModel.cs:94— src/samples/AkavacheTodoMaui/ViewModels/EditTodoViewModel.cs:94-111 | src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:259-276 — 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. 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 (18 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:54— src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:54-71 | src/samples/AkavacheTodoWpf/ViewModels/TodoItemViewModel.cs:80-97 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:53` calls `Create` and `src/samples/AkavacheTodoWpf/ViewModels/TodoItemViewModel.cs:79` 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.
Off the main sequence: Akavache(net10.0) src/Akavache.Core/Akavache.csproj:1— Akavache(net10.0): abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: Akavache.Reactive(net10.0) src/Akavache.Reactive/Akavache.Reactive.csproj:1— Akavache.Reactive(net10.0): abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
async void method: OnWindowDestroying src/samples/AkavacheTodoMaui/App.xaml.cs:72— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnClosing src/samples/AkavacheTodoWpf/MainWindow.xaml.cs:60— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
Swallowed exception (empty catch) src/Akavache.Sqlite3/SqliteBlobCache.cs:846— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/Akavache.Sqlite3/SqlitePclRawConnection.cs:1082— 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.
Races the wall clock: DateTimeSerializationEdgeCasesShouldBeHandledCorrectly src/tests/shared/TestBases/DateTimeTestBase.cs:165— This test reads `DateTime.Today` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
FileTooLong: Akavache.Sqlite3/SqlitePclRawConnection.cs src/Akavache.Sqlite3/SqlitePclRawConnection.cs— FileTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 95 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) src/Akavache.Sqlite3/SqliteBlobCache.cs:409— src/Akavache.Sqlite3/SqliteBlobCache.cs:409-430 | src/Akavache.Sqlite3/SqliteBlobCache.cs:449-482 | src/Akavache.Sqlite3/SqliteBlobCache.cs:528-545 | src/Akavache.Sqlite3/SqliteBlobCache.cs:549-572 | src/Akavache.Sqlite3/SqliteBlobCache.cs:622-641 | src/Akavache.Sqlite3/SqliteBlobCache.cs:645-673 | src/Akavache.Sqlite3/SqliteBlobCache.cs:677-711 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Duplicated block (14 lines × 4) src/Akavache.Sqlite3/SqliteBlobCache.cs:452— src/Akavache.Sqlite3/SqliteBlobCache.cs:452-465 | src/Akavache.Sqlite3/SqliteBlobCache.cs:552-565 | src/Akavache.Sqlite3/SqliteBlobCache.cs:625-638 | src/Akavache.Sqlite3/SqliteBlobCache.cs:680-693 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Akavache.Sqlite3/SqliteBlobCache.cs:452` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/Akavache.Sqlite3/SqliteBlobCache.cs:415— src/Akavache.Sqlite3/SqliteBlobCache.cs:415-420 | src/Akavache.Sqlite3/SqliteBlobCache.cs:651-656 — 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.
Duplicated block (6 lines × 5) src/Akavache.Sqlite3/SqliteBlobCache.cs:415— src/Akavache.Sqlite3/SqliteBlobCache.cs:415-420 | src/Akavache.Sqlite3/SqliteBlobCache.cs:460-465 | src/Akavache.Sqlite3/SqliteBlobCache.cs:633-638 | src/Akavache.Sqlite3/SqliteBlobCache.cs:651-656 | src/Akavache.Sqlite3/SqliteBlobCache.cs:688-693 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 2) src/Akavache.Sqlite3/SqliteBlobCache.cs:658— src/Akavache.Sqlite3/SqliteBlobCache.cs:658-667 | src/Akavache.Sqlite3/SqliteBlobCache.cs:696-705 — 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/Akavache.Sqlite3/SqliteBlobCache.cs:658` 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.
Duplicated block (7 lines × 2) src/Akavache.Core/InMemoryBlobCacheBase.cs:587— src/Akavache.Core/InMemoryBlobCacheBase.cs:587-593 | src/Akavache.Core/InMemoryBlobCacheBase.cs:643-649 — 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/Akavache.Core/InMemoryBlobCacheBase.cs:587` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Akavache.Core/InMemoryBlobCacheBase.cs:650` calls `foreach` and `src/Akavache.Core/InMemoryBlobCacheBase.cs:594` 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· Edited copy of a member (63 corresponding lines) · ×1
Edited copy of a member (63 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:95— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:95-158 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:90-152 — These two members are one piece of code written twice and then edited apart: 63 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:283— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:283-328 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:251-290 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) src/samples/AkavacheTodoMaui/Services/NotificationService.cs:66— src/samples/AkavacheTodoMaui/Services/NotificationService.cs:66-95 | src/samples/AkavacheTodoWpf/Services/NotificationService.cs:123-159 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:276— src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:276-306 | src/samples/AkavacheTodoWpf/ViewModels/TodoItemViewModel.cs:277-307 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:177— src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:177-203 | src/samples/AkavacheTodoWpf/ViewModels/TodoItemViewModel.cs:195-215 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:462— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:462-481 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:400-419 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:641— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:641-662 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:512-533 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) src/samples/AkavacheTodoMaui/Services/NotificationService.cs:47— src/samples/AkavacheTodoMaui/Services/NotificationService.cs:47-60 | src/samples/AkavacheTodoWpf/Services/NotificationService.cs:249-262 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) src/samples/AkavacheTodoMaui/Services/TodoCacheService.cs:165— src/samples/AkavacheTodoMaui/Services/TodoCacheService.cs:165-188 | src/samples/AkavacheTodoWpf/Services/TodoCacheService.cs:150-178 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) src/samples/AkavacheTodoWpf/Services/NotificationService.cs:283— src/samples/AkavacheTodoWpf/Services/NotificationService.cs:283-302 | src/samples/AkavacheTodoMaui/Services/NotificationService.cs:194-208 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:742— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:742-749 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:591-598 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) src/samples/AkavacheTodoMaui/Services/NotificationService.cs:177— src/samples/AkavacheTodoMaui/Services/NotificationService.cs:177-188 | src/samples/AkavacheTodoWpf/Services/NotificationService.cs:266-277 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) src/samples/AkavacheTodoMaui/Services/TodoCacheService.cs:32— src/samples/AkavacheTodoMaui/Services/TodoCacheService.cs:32-35 | src/samples/AkavacheTodoWpf/Services/TodoCacheService.cs:31-33 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:209— src/samples/AkavacheTodoMaui/ViewModels/TodoItemViewModel.cs:209-217 | src/samples/AkavacheTodoWpf/ViewModels/TodoItemViewModel.cs:221-229 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:488— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:488-495 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:424-430 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:502— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:502-505 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:435-438 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (56 lines × 2) src/samples/AkavacheTodoMaui/Services/TodoCacheService.cs:84— src/samples/AkavacheTodoMaui/Services/TodoCacheService.cs:84-139 | src/samples/AkavacheTodoWpf/Services/TodoCacheService.cs:71-126 — before extracting anything, compare `src/samples/AkavacheTodoMaui/Services/TodoCacheService.cs` and `src/samples/AkavacheTodoWpf/Services/TodoCacheService.cs` as WHOLE FILES: 83% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (38 lines × 2) src/samples/AkavacheTodoMaui/Models/AppSettings.cs:10— src/samples/AkavacheTodoMaui/Models/AppSettings.cs:10-47 | src/samples/AkavacheTodoWpf/Models/AppSettings.cs:10-47 — before extracting anything, compare `src/samples/AkavacheTodoMaui/Models/AppSettings.cs` and `src/samples/AkavacheTodoWpf/Models/AppSettings.cs` as WHOLE FILES: 97% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/samples/AkavacheTodoMaui/Models/AppSettings.cs:10` 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.
Duplicated block (28 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:170— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:170-197 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:164-191 — before extracting anything, compare `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs` and `src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:133— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:133-158 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:127-152 — before extracting anything, compare `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs` and `src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:133` it begins part-way through the construct above it, 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 (21 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:47— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:47-67 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:48-68 — before extracting anything, compare `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs` and `src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:412— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:412-431 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:354-373 — before extracting anything, compare `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs` and `src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:412` 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.
Duplicated block (34–35 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:96— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:96-130 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:91-124 — before extracting anything, compare `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs` and `src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:96` 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.
Duplicated block (14 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:291— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:291-304 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:258-271 — before extracting anything, compare `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs` and `src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:291` 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.
Duplicated block (15 lines × 2) src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:462— src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:462-476 | src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:400-414 — before extracting anything, compare `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs` and `src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:462` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:460` calls `RequiresUnreferencedCode`, `RequiresDynamicCode` and `src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:399` 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.
Low cohesion: AkavacheBuilder (LCOM4 4) src/Akavache.Core/Core/AkavacheBuilder.cs:15— AkavacheBuilder's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
P8 · Schema migrations· Schema created by a CREATE TABLE statement (no migration path) · ×1
Schema created by a CREATE TABLE statement (no migration path) src/Akavache.Sqlite3/SqlitePclRawConnection.cs:43— a CREATE TABLE statement here creates the schema at runtime, and this repository keeps no migration history — there's no upgrade path for an existing production database. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` or a migrations bundle) so schema changes are versioned and applied safely.
Duplicated predicate src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs:614— `!string.IsNullOrWhiteSpace(NewTodoTime) && TimeOnly.TryParse(NewTodoTime, out var time)` appears character-identically in 2 files — src/samples/AkavacheTodoMaui/ViewModels/MainViewModel.cs, src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.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/samples/AkavacheTodoMaui/Services/NotificationService.cs:69— `!todo.DueDate.HasValue || !_currentSettings.NotificationsEnabled` appears character-identically in 2 files — src/samples/AkavacheTodoMaui/Services/NotificationService.cs, src/samples/AkavacheTodoWpf/Services/NotificationService.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/samples/AkavacheTodoMaui/Services/NotificationService.cs:215— `!todo.DueDate.HasValue || todo.IsCompleted` appears character-identically in 2 files — src/samples/AkavacheTodoMaui/Services/NotificationService.cs, src/samples/AkavacheTodoWpf/Services/NotificationService.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/samples/AkavacheTodoMaui/Models/TodoItem.cs:87— `DueDate < TimeProvider.System.GetLocalNow() && !IsCompleted` appears character-identically in 2 files — src/samples/AkavacheTodoMaui/Models/TodoItem.cs, src/samples/AkavacheTodoWpf/Models/TodoItem.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/samples/AkavacheTodoMaui/Models/TodoItem.cs:91— `DueDate > TimeProvider.System.GetLocalNow() && DueDate.Value <= TimeProvider.System.GetLocalNow().AddHours(DueSoonWindowHours) && !IsComplet…` appears character-identically in 2 files — src/samples/AkavacheTodoMaui/Models/TodoItem.cs, src/samples/AkavacheTodoWpf/Models/TodoItem.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/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs:101— `bsonResult is not null || typeof(T).IsValueType` appears character-identically in 2 files — src/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs, src/Akavache.SystemTextJson.Bson/SystemJsonBsonSerializer.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/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs:59— `data is null || data.Length <= BsonLengthPrefixSize` appears character-identically in 2 files — src/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs, src/Akavache.SystemTextJson.Bson/SystemJsonBsonSerializer.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/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs:68— `documentLength <= BsonLengthPrefixSize || documentLength > data.Length + BsonLengthTolerance` appears character-identically in 2 files — src/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs, src/Akavache.SystemTextJson.Bson/SystemJsonBsonSerializer.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/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs:75— `firstChar is not ((byte)'{' or (byte)'[' or (byte)'"') && !BinaryHelpers.StartsWithJsonOpener(data)` appears character-identically in 2 files — src/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs, src/Akavache.SystemTextJson.Bson/SystemJsonBsonSerializer.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/Akavache.Core/Helpers/DateTimeHelpers.cs:82— `forcedDateTimeKind.HasValue && dateTime.Kind != forcedDateTimeKind.Value` appears character-identically in 2 files — src/Akavache.Core/Helpers/DateTimeHelpers.cs, src/Akavache.Core/UniversalSerializer.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/samples/AkavacheTodoMaui/Services/NotificationService.cs:223— `now >= notificationTime && now <= todo.DueDate.Value` appears character-identically in 2 files — src/samples/AkavacheTodoMaui/Services/NotificationService.cs, src/samples/AkavacheTodoWpf/Services/NotificationService.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/samples/AkavacheTodoMaui/Services/NotificationService.cs:199— `todo is { IsCompleted: false, DueDate: not null } && _currentSettings.NotificationsEnabled && ShouldNotify(todo)` appears character-identically in 2 files — src/samples/AkavacheTodoMaui/Services/NotificationService.cs, src/samples/AkavacheTodoWpf/Services/NotificationService.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/Akavache.Core/Helpers/DateTimeTypeExtensions.cs:20— `type == typeof(DateTime) || type == typeof(DateTime?)` appears character-identically in 2 files — src/Akavache.Core/Helpers/DateTimeTypeExtensions.cs, src/Akavache.NewtonsoftJson/NewtonsoftDateTimeContractResolver.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.
redundant comment src/Akavache.Core/UniversalSerializer.cs:703— "Try registered BSON-capable serializers" repeats the code it sits on: 4 of its 5 words (try, registered, bson, serializers) are already in `foreach (var factory in Volatile.Read(ref _registeredSerializerFactories))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs:352— "Set our contract resolver, preserving any existing one" repeats the code it sits on: 4 of its 5 words (set, contract, resolver, existing) are already in `_contractResolver.ExistingContractResolver = settings.ContractResolver;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Core.Tests.Parallel/SecurityUtilitiesTests.cs:272— "Test SafePathCombine" repeats the code it sits on: 4 of its 4 words (test, safe, path, combine) are already in `_ = Assert.Throws<ArgumentException>(static () => SecurityUtilities.SafePathCombine(null!, "test"));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Core.Tests/CoreUtilityTests.cs:238— "Test KeyNotFoundException helper" repeats the code it sits on: 6 of its 6 words (test, key, not, found, exception, helper) are already in `var keyNotFoundObs = IBlobCache.ExceptionHelpers.ObservableThrowKeyNotFoundException<string>("test_key");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Core.Tests/CoreUtilityTests.cs:248— "Test ObjectDisposedException helper" repeats the code it sits on: 5 of its 5 words (test, object, disposed, exception, helper) are already in `var objectDisposedObs = IBlobCache.ExceptionHelpers.ObservableThrowObjectDisposedException<string>("test_cache");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Core.Tests/IBlobCacheInterfaceTests.cs:52— 6 comments in this file only repeat the code they sit on (lines 52, 437, 441, 454, 458, 472), for example "Test KeyNotFoundException helper". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Integration.Tests.Parallel/SerializerExtensionsTests.cs:505— "Insert existing user" repeats the code it sits on: 3 of its 3 words (insert, existing, user) are already in `cache.InsertObject("existing_user", existingUser).WaitForCompletion();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Integration.Tests/BitmapImageExtensionsTests.cs:460— "Insert valid image data" repeats the code it sits on: 4 of its 4 words (insert, valid, image, data) are already in `cache.Insert(key, validImageData)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Integration.Tests/ImageCacheExtensionsTests.cs:475— "Insert valid image data" repeats the code it sits on: 4 of its 4 words (insert, valid, image, data) are already in `cache.Insert(key, validImageData)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Integration.Tests/ImageExtensionsTests.cs:305— "Insert image data" repeats the code it sits on: 3 of its 3 words (insert, image, data) are already in `cache.Insert(key, imageData).WaitForCompletion();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Integration.Tests/UniversalSerializerKeyLookupTests.cs:43— "Act - Try to find with alternative keys" repeats the code it sits on: 4 of its 5 words (try, find, alternative, keys) are already in `var result = await UniversalSerializer.TryFindDataWithAlternativeKeysAsync<UserObject>(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/tests/Akavache.Sqlite3.Tests.Parallel/SqliteBlobCacheDirectTests.cs:702— "Typed inserts with expiration" repeats the code it sits on: 3 of its 3 words (typed, inserts, expiration) are already in `cache.Insert(ExpiredTypedKey, ThirdEntryPayload, typeof(string), pastExpiration).WaitForCompletion();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
P10 · Library API & versioning· Public type used only inside its own library · ×8
Public type used only inside its own library src/Akavache.Core/InMemoryBlobCache.cs:23— `Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net10.0-android)`, `Akavache.EncryptedSqlite3.Reactive(net10.0-android)`, `Akavache.HttpDownloader.Reactive(net10.0-android)`, `Akavache.NewtonsoftJson.Reactive(net10.0-android)`, `Akavache.Sqlite3.Reactive(net10.0-android)`, `Akavache.SystemTextJson.Reactive(net10.0-android)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/Akavache.Core/InMemoryBlobCache.cs:23— `Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net47)`, `Akavache.EncryptedSqlite3.Reactive(net47)`, `Akavache.HttpDownloader.Reactive(net47)`, `Akavache.NewtonsoftJson.Reactive(net47)`, `Akavache.Sqlite3.Reactive(net47)`, `Akavache.SystemTextJson.Reactive(net47)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/Akavache.Core/InMemoryBlobCache.cs:23— `Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net471)`, `Akavache.EncryptedSqlite3.Reactive(net471)`, `Akavache.HttpDownloader.Reactive(net471)`, `Akavache.NewtonsoftJson.Reactive(net471)`, `Akavache.Sqlite3.Reactive(net471)`, `Akavache.SystemTextJson.Reactive(net471)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/Akavache.Core/InMemoryBlobCache.cs:23— `Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net472)`, `Akavache.EncryptedSqlite3.Reactive(net472)`, `Akavache.HttpDownloader.Reactive(net472)`, `Akavache.NewtonsoftJson.Reactive(net472)`, `Akavache.Sqlite3.Reactive(net472)`, `Akavache.SystemTextJson.Reactive(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/Akavache.Core/InMemoryBlobCache.cs:23— `Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net48)`, `Akavache.EncryptedSqlite3.Reactive(net48)`, `Akavache.HttpDownloader.Reactive(net48)`, `Akavache.NewtonsoftJson.Reactive(net48)`, `Akavache.Sqlite3.Reactive(net48)`, `Akavache.SystemTextJson.Reactive(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/Akavache.Core/InMemoryBlobCache.cs:23— `Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net481)`, `Akavache.EncryptedSqlite3.Reactive(net481)`, `Akavache.HttpDownloader.Reactive(net481)`, `Akavache.NewtonsoftJson.Reactive(net481)`, `Akavache.Sqlite3.Reactive(net481)`, `Akavache.SystemTextJson.Reactive(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/Akavache.Core/InMemoryBlobCache.cs:23— `Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.EncryptedSqlite3.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.HttpDownloader.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.NewtonsoftJson.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.Sqlite3.Reactive(net10.0-windows10.0.19041.0)`, `Akavache.SystemTextJson.Reactive(net10.0-windows10.0.19041.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/Akavache.Core/InMemoryBlobCache.cs:23— `Akavache.Reactive.InMemoryBlobCache` (src/Akavache.Core/InMemoryBlobCache.cs:23) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Akavache.Drawing.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.EncryptedSqlite3.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.HttpDownloader.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.NewtonsoftJson.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.Sqlite3.Reactive(net11.0-windows10.0.19041.0)`, `Akavache.SystemTextJson.Reactive(net11.0-windows10.0.19041.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
README/code drift docs/BENCHMARK_REPORT.md:21— docs/BENCHMARK_REPORT.md names .NET 9, but the projects target .NET 10, 11. 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/installation.md:45— docs/installation.md names .NET 8, but the projects target .NET 10, 11. 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/performance.md:78— docs/performance.md names .NET 9, but the projects target .NET 10, 11. 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/platform-notes.md:7— docs/platform-notes.md names .NET 9, but the projects target .NET 10, 11. 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.
Silent fallback default in catch src/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs:232— `DeserializeBsonFormat` swallows every exception into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Akavache.NewtonsoftJson/NewtonsoftSerializer.cs:284— `TryDeserializeFromOtherFormats` swallows every exception into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Akavache.SystemTextJson.Bson/SystemJsonBsonSerializer.cs:128— `Deserialize` swallows every exception into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Fat interface: IBlobCache (35 members) src/Akavache.Core/IBlobCache.cs:15— `IBlobCache` declares 35 members under just 13 distinct name(s): `Serializer`, `Scheduler`, `ForcedDateTimeKind`, `Insert`, `Insert`, `Insert`, `Insert`, `Insert`, `Insert`, `Insert`, `Insert`, `Get`, `Get`, `Get`, `Get`, `GetAll`, `GetAllKeys`, `GetAllKeys`, `GetCreatedAt`, `GetCreatedAt`, `GetCreatedAt`, `GetCreatedAt`, `Flush`, `Flush`, `Invalidate`, `Invalidate`, `Invalidate`, `Invalidate`, `InvalidateAll`, `InvalidateAll`, `Vacuum`, `UpdateExpiration`, `UpdateExpiration`, `UpdateExpiration`, `UpdateExpiration`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 35 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 35 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: IHttpService (24 members) src/Akavache.HttpDownloader/IHttpService.cs:16— `IHttpService` declares 24 members under just 1 distinct name(s): `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`, `DownloadUrl`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 24 separate responsibilities: a caller binds to 1 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 24 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Hand-rolled JSON/XML parsing via regex src/Akavache.SystemTextJson.Bson/SystemJsonBsonSerializer.Regex.cs:31— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via regex src/Akavache.SystemTextJson.Bson/SystemJsonBsonSerializer.Regex.cs:40— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Silent fallback default on parse failure src/samples/AkavacheTodoMaui/ViewModels/EditTodoViewModel.cs:127— `ExecuteSave` falls back to `TimeOnly.MinValue` when `!string.IsNullOrWhiteSpace(DueTime) && TimeOnly.TryParse(DueTime, out var time)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/samples/AkavacheTodoWpf/ViewModels/MainViewModel.cs:463— `ExecuteAddTodo` falls back to `TimeOnly.MinValue` when `!string.IsNullOrWhiteSpace(NewTodoTime) && TimeOnly.TryParse(NewTodoTime, out va…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
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.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 10 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 0/16 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.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.9 `!` suppressions per 1k syntax nodes — 65 suppression(s) across the 70132 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
doc comments repeat the names src/Akavache.Core/AkavacheBuilderExtensions.cs:110— 40 of 524 documented parameters and 36 of 422 summaries in `Akavache(net10.0)` only repeat the member or parameter name (e.g. "The builder." for `builder`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/benchmarks/Akavache.Benchmarks/PerfHelper.cs:77— 0 of 8 documented parameters and 3 of 114 summaries in `Akavache.Benchmarks(net10.0)` only repeat the member or parameter name (e.g. "Generate the contents of the database." for `GenerateRandomDatabaseContents`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/tests/Akavache.Core.Tests.Parallel/AkavacheSqliteExceptionTests.cs:56— 4 of 56 documented parameters and 25 of 475 summaries in `Akavache.Core.Tests.Parallel.Reactive(net10.0)` only repeat the member or parameter name (e.g. "The result-code-and-message constructor stores both the result code and message." for `Ctor_WithResultCodeAndMessage_StoresBoth`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/Akavache.EncryptedSqlite3/AkavacheBuilderExtensions.cs:50— 10 of 174 documented parameters and 0 of 218 summaries in `Akavache.EncryptedSqlite3.Reactive(net10.0)` only repeat the member or parameter name (e.g. "The password." for `password`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/tests/Akavache.EncryptedSqlite3.Tests.Parallel/EncryptedSqliteBlobCacheDirectTests.cs:560— 22 of 93 documented parameters and 9 of 336 summaries in `Akavache.EncryptedSqlite3.Tests.Parallel.Reactive(net10.0)` only repeat the member or parameter name (e.g. "InvalidateAll with a null type throws ArgumentNullException." for `InvalidateAllWithNullTypeShouldThrowArgumentNullException`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/Akavache.HttpDownloader/HttpExtensions.cs:207— 12 of 307 documented parameters and 4 of 125 summaries in `Akavache.HttpDownloader.Reactive(net10.0)` only repeat the member or parameter name (e.g. "The method." for `method`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/tests/shared/TestBases/BlobCacheDownloadTestsBase.cs:34— 4 of 48 documented parameters and 1 of 232 summaries in `Akavache.HttpDownloader.Tests.Reactive(net10.0)` only repeat the member or parameter name (e.g. "Type of the serializer." for `serializerType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/tests/Akavache.Integration.Tests.Parallel/NewtonsoftDateConvertersTests.cs:579— 0 of 21 documented parameters and 7 of 457 summaries in `Akavache.Integration.Tests.Parallel.Reactive(net10.0)` only repeat the member or parameter name (e.g. "ConvertDateTimeKind with Utc returns a UTC DateTime." for `ConvertDateTimeKind_Utc_ReturnsUtc`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/tests/Akavache.Integration.Tests/AkavacheBuilderExtensionsTests.cs:16— 0 of 36 documented parameters and 2 of 673 summaries in `Akavache.Integration.Tests.Reactive(net10.0)` only repeat the member or parameter name (e.g. "Tests for AkavacheBuilderExtensions." for `AkavacheBuilderExtensionsTests`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/Akavache.NewtonsoftJson/NewtonsoftDateTimeTickConverter.cs:70— 1 of 20 documented parameters and 1 of 41 summaries in `Akavache.NewtonsoftJson.Reactive(net10.0)` only repeat the member or parameter name (e.g. "Converts a to the specified ." for `ConvertDateTimeKind`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/tests/Akavache.Settings.Tests.Parallel/SettingsBaseHelperTests.cs:23— 1 of 64 documented parameters and 7 of 281 summaries in `Akavache.Settings.Tests.Parallel.Reactive(net10.0)` only repeat the member or parameter name (e.g. "The value is seeded with." for `SeededTestValue`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/tests/Akavache.Settings.Tests/SettingsBaseFallbackTests.cs:22— 0 of 9 documented parameters and 1 of 83 summaries in `Akavache.Settings.Tests.Reactive(net10.0)` only repeat the member or parameter name (e.g. "The value is seeded with." for `SeededTestValue`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/tests/Akavache.Sqlite3.Tests.Parallel/InternalHelperTests.cs:89— 6 of 56 documented parameters and 18 of 491 summaries in `Akavache.Sqlite3.Tests.Parallel.Reactive(net10.0)` only repeat the member or parameter name (e.g. "SQLITE_OK does not throw." for `CheckRc_SqliteOk_DoesNotThrow`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/Akavache.SystemTextJson.Bson/SystemJsonBsonSerializer.cs:80— 1 of 23 documented parameters and 0 of 29 summaries in `Akavache.SystemTextJson.Bson.Reactive(net10.0)` only repeat the member or parameter name (e.g. "The bytes." for `bytes`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names src/Akavache.SystemTextJson/SystemJsonSerializer.cs:40— 1 of 7 documented parameters and 0 of 11 summaries in `Akavache.SystemTextJson.Reactive(net10.0)` only repeat the member or parameter name (e.g. "The bytes." for `bytes`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
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.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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. semgrep could not parse 105 file(s) — `src/Akavache.Core/AkavacheBuilderExtensions.cs`, `src/Akavache.Core/AkavacheSqliteException.cs`, `src/Akavache.Core/CacheDatabase.cs`, `src/Akavache.Core/CacheEntry.cs`, `src/Akavache.Core/CheckpointMode.cs`, … (+100 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
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.
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.
Run 01a1e66e-72b7-7e5e-8d0c-8e19bb4b9c5e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 30 · Warnings: 202 · Recommendations: 53 · Info: 15 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 22:16 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.