Public report of fsprojects/pulsar-client-dotnet, published 13 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 report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). 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, 13 November 2026, 09:54 UTC · Survey ID cd_8a27442672f34ba9acbf966d0e9e4c40

fsprojects/pulsar-client-dotnet

Measured 13 November 2026, 09:54 UTC, at code version 477793f

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

CAI score 56out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 2 since the last survey

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

A small codebase: 15,849 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 43

Findings by how serious they are

6 critical 78 serious 44 minor

11 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 09:54 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 ▸

41of 41 dimensions measured by tools.
96of 128 findings point to an exact file and line, so you can open each one in the code. The other 32 concern the repository as a whole, such as missing documentation.
41dimensions across 6 lenses, read from 15,849 lines of product code in 4 projects.
Chapters

Executive summary

fsprojects/pulsar-client-dotnet falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 56 out of 100 and is rated Adequate, and five of its six critical findings are security problems in the build pipeline and in the packages it uses.

Production Readiness, at 43, is the weakest lens and counts most in the score. The best first step is updating the outdated dependencies, worth about 6 points. Protecting the data stores from deletion would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 66.

Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One known security hole in a package the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks. The warning switched off for a whole file needs narrowing to the lines that need it.

The product code is 15,849 lines, about €30,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 for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 43 · counts for 46%Code Health 61 · counts for 25%Maturity 62 · counts for 14%Security and Compliance 78 · counts for 8%Performance 85 · counts for 4%Architecture 96 · counts for 2%

If Production Readiness rose from 43 to 70, the lowest score rated Strong, the score would rise from 56 to about 66.

Code composition: what the lines of code are
Business logic 1%Supporting code 3%Tests 95%
New since the last survey: 16 findings

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

  • God Classes · TooManyFunctions: Tools src/Pulsar.Client/Common/Tools.fs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/Pulsar.Client/Internal/ConsumerStatsImpl.fs
  • Code Duplication · Edited copy of a member (97 corresponding lines) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs
  • Code Duplication · Edited copy of a member (71 corresponding lines) src/Pulsar.Client.Proto/MurmurHash3.cs
  • Code Duplication · Edited copies of one member (7 members, 15+ corresponding lines) src/Pulsar.Client/Schema/BooleanSchema.fs
  • Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) src/Pulsar.Client/Schema/DateSchema.fs
  • Code Duplication · Edited copy of a member (10 corresponding lines) src/Pulsar.Client/Schema/AutoConsumeSchema.fs
  • Code Duplication · Duplicated block (12 lines × 2) src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs
  • Code Duplication · Duplicated block (7 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs
  • Code Duplication · Duplicated block (6 lines × 2) src/Pulsar.Client/Internal/NegativeAcksTracker.fs
  • Code Duplication · Duplicated block (10 lines × 3) src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs
  • Code Duplication · Duplicated block (9 lines × 3) src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs
  • Code Duplication · Edited copy of a member (42 corresponding lines) examples/FsharpExamples/Simple.fs
  • Code Duplication · Edited copy of a member (30 corresponding lines) examples/CsharpExamples/Oauth2.cs
  • Change Coupling · Change-coupling hub: ProducerImpl.fs → ProducerBuilder.fs, ReaderImpl.fs, TransactionMetaStoreHandler.fs src/Pulsar.Client/Internal/ProducerImpl.fs
  • Change Coupling · Change coupling: MultiTopicsConsumerImpl.fs ↔ ReaderImpl.fs src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs

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

Fixed since the last survey: 22 findings

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

  • Code Duplication · Near-duplicate member pair (59 shared lines) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/Pulsar.Client/Internal/ConsumerStatsImpl.fs
  • Code Duplication · Duplicated block (19 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs
  • Code Duplication · Duplicated block (17 lines × 2) src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs
  • Code Duplication · Duplicated block (9–10 lines × 2) src/Pulsar.Client/Internal/AcknowledgmentsGroupingTracker.fs
  • Code Duplication · Duplicated block (9–10 lines × 2) src/Pulsar.Client/Internal/NegativeAcksTracker.fs
  • Code Duplication · Duplicated block (9 lines × 2) src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs
  • Code Duplication · Duplicated block (9 lines × 2) src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs
  • Code Duplication · Duplicated block (8 lines × 2) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs
  • Code Duplication · Duplicated block (7 lines × 2) src/Pulsar.Client/Internal/ProducerImpl.fs
  • Code Duplication · Duplicated block (6 lines × 2) src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs
  • Code Duplication · Duplicated block (10 lines × 3) src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs
  • Code Duplication · Duplicated block (10 lines × 3) src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs
  • Code Duplication · Duplicated block (6 lines × 3) src/Pulsar.Client/Internal/ConsumerImpl.fs
  • Code Coverage · Coverage not measured — no coverage collector is wired up
  • Test Reliability · Flaky test: UnitTests::Stats.Stats.Consumer stats
  • Secret Scanning · Leaked secret: high-entropy-secret examples/Oauth2Files/credentials_file.json
  • Secret Scanning · Leaked secret: signing-key examples/Oauth2Files/credentials_file.json
  • Churn × Complexity Hotspots · Repeated repair: src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs
  • Secrets (history) · Secret: generic-api-key examples/Oauth2Files/credentials_file.json
  • Change Coupling · Change coupling: ProducerImpl.fs ↔ TransactionMetaStoreHandler.fs src/Pulsar.Client/Internal/ProducerImpl.fs
  • Change Coupling · Change coupling: ProducerBuilder.fs ↔ ProducerImpl.fs src/Pulsar.Client/Api/ProducerBuilder.fs
Rebuild cost: about €30,000 · Estimate
Cost to rebuild€9,900 to €50,000, for 164 to 522 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemLow, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeSmall: 15,849 lines of product code
Comment linesThe estimate prices 15,823 lines. Comment lines count towards the size of 15,849 lines but aren't priced as work.
What it is notNot 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
Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with Pulsar.Client.fsproj (5), REDACTED.
Raises the score by about 6 points · Low effort · Dependency Hygiene
2
Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with RealWorld.cs.
Raises the score by about 3 points · Low effort · Explicit Debt
3
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Raises the score by about 4 points · Medium effort · DR & Backup

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 €30,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 43 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 6 Outdated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 6 Dependency Hygiene findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch CsharpExamples CsharpExamples FsharpExamples FsharpExamples Pulsar.Client Client Pulsar.Client.Proto Proto Pulsar.Client->Pulsar.Client.Proto Pulsar.Client.Otel Otel

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 38 dependencies between them. One loop runs through 6 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 AssemblyInfo2 Pulsar.Client.Api.ProducerStreamOwnership3 Pulsar.Client.Api.PulsarClientException4 Pulsar.Client.Common.RetryMessageUtil5 Pulsar.Client.Common.Tools6 Pulsar.Client.Common.TopicNameHelpers7 Pulsar.Client.Common.UMX8 Pulsar.Client.Internal.Generators9 Pulsar.Client.Internal.SocketFactory10 Pulsar.Client.Schema11 Pulsar.Client.Internal12 Pulsar.Client.Transaction13 Pulsar.Client.Common14 Pulsar.Client.Common.ConsumerBase15 Pulsar.Client.Common.ServiceUriModule16 Pulsar.Client.Internal.BatchHelpers17 Pulsar.Client.Internal.CompressionCodec18 Pulsar.Client.Api19 Pulsar.Client.Api.AutoClusterFailoverLogic20 Pulsar.Client.Api.SchemaUtils21 Pulsar.Client.Auth22 Pulsar.Client.Auth.OAuth223 Pulsar.Client.Common.Commands24 Pulsar.Client.Crypto25 Pulsar.Client.Otel.OTelProducerInterceptor26 Pulsar.Client.Otel.OtelConsumerInterceptor27 Pulsar.Client.Auth.DefaultImplementation
1 AssemblyInfo
2 Pulsar.Client.Api.ProducerStreamOwnership
3 Pulsar.Client.Api.PulsarClientException
4 Pulsar.Client.Common.RetryMessageUtil
5 Pulsar.Client.Common.Tools
6 Pulsar.Client.Common.TopicNameHelpers
7 Pulsar.Client.Common.UMX
8 Pulsar.Client.Internal.Generators
9 Pulsar.Client.Internal.SocketFactory
10 Pulsar.Client.Schema3729
11 Pulsar.Client.Internal256132
12 Pulsar.Client.Transaction212
13 Pulsar.Client.Common11
14 Pulsar.Client.Common.ConsumerBase51
15 Pulsar.Client.Common.ServiceUriModule1
16 Pulsar.Client.Internal.BatchHelpers1
17 Pulsar.Client.Internal.CompressionCodec51
18 Pulsar.Client.Api6218894
19 Pulsar.Client.Api.AutoClusterFailoverLogic2
20 Pulsar.Client.Api.SchemaUtils31
21 Pulsar.Client.Auth6
22 Pulsar.Client.Auth.OAuth22
23 Pulsar.Client.Common.Commands191
24 Pulsar.Client.Crypto22
25 Pulsar.Client.Otel.OTelProducerInterceptor22
26 Pulsar.Client.Otel.OtelConsumerInterceptor32
27 Pulsar.Client.Auth.DefaultImplementation21
Uses a module listed above itPart of a loopThe module itself
1 AssemblyInfo2 Pulsar.Client.Api.ProducerStreamOwnership3 Pulsar.Client.Api.PulsarClientException4 Pulsar.Client.Common.RetryMessageUtil5 Pulsar.Client.Common.Tools6 Pulsar.Client.Common.TopicNameHelpers7 Pulsar.Client.Common.UMX8 Pulsar.Client.Internal.Generators9 Pulsar.Client.Internal.SocketFactory10 Pulsar.Client.Schema11 Pulsar.Client.Internal12 Pulsar.Client.Transaction13 Pulsar.Client.Common14 Pulsar.Client.Common.ConsumerBase15 Pulsar.Client.Common.ServiceUriModule16 Pulsar.Client.Internal.BatchHelpers17 Pulsar.Client.Internal.CompressionCodec18 Pulsar.Client.Api19 Pulsar.Client.Api.AutoClusterFailoverLogic20 Pulsar.Client.Api.SchemaUtils21 Pulsar.Client.Auth22 Pulsar.Client.Auth.OAuth223 Pulsar.Client.Common.Commands24 Pulsar.Client.Crypto25 Pulsar.Client.Otel.OTelProducerInterceptor26 Pulsar.Client.Otel.OtelConsumerInterceptor27 Pulsar.Client.Auth.DefaultImplementationAssemblyInfo1Pulsar.Client.Api.ProducerStreamOwnership2Pulsar.Client.Api.PulsarClientException3Pulsar.Client.Common.RetryMessageUtil4Pulsar.Client.Common.Tools5Pulsar.Client.Common.TopicNameHelpers6Pulsar.Client.Common.UMX7Pulsar.Client.Internal.Generators8Pulsar.Client.Internal.SocketFactory9Pulsar.Client.Schema10Pulsar.Client.Internal11Pulsar.Client.Transaction12Pulsar.Client.Common13Pulsar.Client.Common.ConsumerBase14Pulsar.Client.Common.ServiceUriModule15Pulsar.Client.Internal.BatchHelpers16Pulsar.Client.Internal.CompressionCodec17Pulsar.Client.Api18Pulsar.Client.Api.AutoClusterFailoverLogic19Pulsar.Client.Api.SchemaUtils20Pulsar.Client.Auth21Pulsar.Client.Auth.OAuth222Pulsar.Client.Common.Commands23Pulsar.Client.Crypto24Pulsar.Client.Otel.OTelProducerInterceptor25Pulsar.Client.Otel.OtelConsumerInterceptor26Pulsar.Client.Auth.DefaultImplementation2737292561322121151115162188942316219122223221

At a glance — Code Health · 61% · Adequate · gated by X5 ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 62% · Adequate · gated by M2 ·

At a glance — Readiness · 43% · Weak · gated by P3, P5 ·

At a glance — Security · 78% · Adequate · gated by D36 ·

At a glance — Performance · 85% · Strong ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures8High / Critical
A05:2025 — Injection6High / Critical

Roadmap

Top priorities: Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with Pulsar.Client.fsproj (5), REDACTED; Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete; Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

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

Do thisHelpsEffortDimension
Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with Pulsar.Client.fsproj (5), REDACTED.+5.8 ptsLowDependency Hygiene
Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with RealWorld.cs.+2.7 ptsLowExplicit Debt
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.+4.4 ptsMediumDR & Backup
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.+3.3 ptsMediumNullable reference types
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.+2.9 ptsMediumArchitecture documentation
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.+2.5 ptsMediumDeployment & Rollback
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+2.5 ptsMediumRelease Hygiene
Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene.+1.0 ptsLowDependency Hygiene

File quality

Per-file score 0–10 — a quality signature. Of 36 files carrying findings, judged against the Production bar: 6% slop · 55% mixed · 39% near-clean.

FileScoreBandWorst signal
REDACTED2.1SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
src/Pulsar.Client/Internal/ConsumerImpl.fs4.8MixedCognitive Complexity: ConsumerImpl`1.ReceiveIndividualMessagesFromBatch (cognitive 23)
src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs5.1MixedGod Classes: FileTooLong: Internal/MultiTopicsConsumerImpl.fs
src/Pulsar.Client/Internal/ProducerImpl.fs6.3MixedGod Classes: FileTooLong: Internal/ProducerImpl.fs
REDACTED6.7MixedDependency Vulnerabilities: High CVE: REDACTED
src/Pulsar.Client/Internal/ClientCnx.fs7.0MixedGod Classes: FileTooLong: Internal/ClientCnx.fs
src/Pulsar.Client/Api/ConsumerBuilder.fs7.0MixedGod Classes: TooManyMethods: ConsumerBuilder`1
src/Pulsar.Client/Internal/BinaryLookupService.fs7.2MixedCode Duplication: Duplicated block (18 lines × 2)
src/Pulsar.Client.Proto/DynamicJsonConverter.cs7.3MixedExplicit Debt: TodoComment
src/Pulsar.Client/Internal/ConsumerStatsImpl.fs7.4MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs7.4MixedCode Duplication: Edited copy of a member (97 corresponding lines)
src/Pulsar.Client/Internal/PartitionedProducerImpl.fs7.4MixedCode Duplication: Duplicated block (14 lines × 2)
examples/CsharpExamples/RealWorld.cs7.6MixedExplicit Debt: FileScopedPragmaDisable
src/Pulsar.Client/Common/MessageId.fs7.8MixedCyclomatic Complexity: MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cyclomatic 16)
src/Pulsar.Client.Proto/MurmurHash3.cs7.8MixedCode Duplication: Edited copy of a member (71 corresponding lines)
src/Pulsar.Client/Api/PulsarClient.fs7.8MixedCode Duplication: Duplicated block (11–12 lines × 2)
src/Pulsar.Client/Common/Commands.fs7.8MixedCode Duplication: Duplicated block (10 lines × 2)
src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs7.8MixedCode Duplication: Duplicated block (10 lines × 3)
src/Pulsar.Client/Internal/Compression.fs7.8MixedCode Duplication: Duplicated block (8 lines × 2)

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 — 6

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 — 78

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 — 44

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

Could not be resolved — 11

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 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, 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 — 41 dimensions across the health lenses
D1D2D3D4D5D6D11D12D13D14D15D16D17D19D26D27D28D29D30D31D34D35D36D43D44AX10AX3AX4AX5AX8GD1M1M2M3P1P3P4P5P6PF3X5

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

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 96 of 128 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1d454-9958-7ca3-ac6e-5c1041e32532.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'examples/FsharpExamples/FsharpExamples.fsproj' because the file extension '.fsproj' is not associated with a language.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 4 deducted marker(s) and the 0.2/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (15,072 lines, 95% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.

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.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • 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.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo at 16. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Schema.GetValidateFunction at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Pulsar.Client/Api/Schema.fs (Schema.GetValidateFunction at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cyclomatic 16)src/Pulsar.Client/Common/MessageId.fs:140

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.

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

D2 · Cognitive Complexity9.0 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

2 method(s) exceeded the cognitive complexity threshold of 15; the worst was MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo at 33.

MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cognitive 33)src/Pulsar.Client/Common/MessageId.fs:140
ConsumerImpl`1.ReceiveIndividualMessagesFromBatch (cognitive 23)src/Pulsar.Client/Internal/ConsumerImpl.fs:1726

What to do

  1. Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cognitive 33), ConsumerImpl`1.ReceiveIndividualMessagesFromBatch (cognitive 23). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes8.3 / 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.

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

8 god class(es) detected.

FileTooLong: Internal/ConsumerImpl.fs · ×4src/Pulsar.Client/Internal/ConsumerImpl.fs
TooManyMethods: ConsumerImpl`1 · ×3src/Pulsar.Client/Internal/ConsumerImpl.fs:68
TooManyFunctions: Toolssrc/Pulsar.Client/Common/Tools.fs:2

What to do

  1. Resolve the 4 FileTooLong finding(s) in God Classes — start with ConsumerImpl.fs, MultiTopicsConsumerImpl.fs, ProducerImpl.fs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 TooManyMethods finding(s) in God Classes — start with ConsumerImpl.fs, MultiTopicsConsumerImpl.fs, ConsumerBuilder.fs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 TooManyFunctions finding(s) in God Classes — start with Tools.fs. — 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.

D4 · Code Duplication9.0 / 10Strong✓ Tool-verified

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

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

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

36 duplicated block group(s) detected. A further 8 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 8 of the 44 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.

Duplicated block (10 lines × 2) · ×3src/Pulsar.Client/Common/Commands.fs:42
Duplicated block (8 lines × 2) · ×3src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:227
Duplicated block (7 lines × 2) · ×3src/Pulsar.Client/Internal/ConsumerImpl.fs:121
Duplicated block (6 lines × 2) · ×3src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:40
Duplicated block (14 lines × 2) · ×2src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:89

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

What to do

  1. Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with Commands.fs (2), MultiTopicsReaderImpl.fs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Compression.fs (2), PartitionedProducerImpl.fs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ConsumerImpl.fs (2), ProducerImpl.fs. — One of this dimension's main actionable groups (3 warning-level).

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

1 of 58 classes have LCOM4 above 3.

Low cohesion: ZeroQueueConsumerImpl`1 (LCOM4 5)src/Pulsar.Client/Internal/ConsumerImpl.fs:2101

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ConsumerImpl.fs. — 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.

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

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

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

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

0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene8.6 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

25 outdated, 0 vulnerable, 0 deprecated, 1 prerelease packages.

Prerelease dependency: Expecto.FsCheck
Outdated: Microsoft.Extensions.Caching.Memory · ×6src/Pulsar.Client/Pulsar.Client.fsproj:58
Outdated: Microsoft.Extensions.Logging.Console · ×19

What to do

  1. Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with Pulsar.Client.fsproj (5), REDACTED. — One of this dimension's main actionable groups (6 recommendation-level).
  2. Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 174 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 33 direct `PackageReference`(s), and 123 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor8.7 / 10Strong✓ Tool-verified

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

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

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

7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Pulsar.Client/Api/PulsarClient.fs. Counted over 52 of the 110 production source files in this repository: 55 are under the ~2,400-byte size floor this dimension measures over, and the remaining 3 have no attributable history left to measure.

Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt9.6 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

4 deducted debt markers + unmeasured dead symbols across 3866 LoC in the .NET projects (0.2/KLoC) → score 9.6. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (95% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

FileScopedPragmaDisableexamples/CsharpExamples/RealWorld.cs:8
TodoComment · ×2src/Pulsar.Client.Proto/DynamicJsonConverter.cs:47
CommentedOutCodeexamples/CsharpExamples/Program.cs:21

What to do

  1. Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with RealWorld.cs. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 2 TodoComment finding(s) in Explicit Debt — start with DynamicJsonConverter.cs (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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.

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

1 of 1 documentation facets pass in full. 3 document(s) read across 2 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D26 · Project Cohesion5.0 / 10Adequate✓ Tool-verified

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

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

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

1 of 4 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionsrc/Pulsar.Client.Proto/Pulsar.Client.Proto.csproj:1

What to do

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

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

D27 · Navigability9.8 / 10Exemplary✓ Tool-verified

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

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

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

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

92 % of calls cross a namespace and 4 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)9.0 / 10Adequategated by 4 critical findings✓ Tool-verified

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

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

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

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

6 finding(s): 0 critical, 4 high, 2 medium, 0 low. 4 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.

REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
  2. No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

D34 · Knowledge Freshness9.2 / 10Exemplary✓ Tool-verified

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

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

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

4 of 55 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Pulsar.Client/Internal/ConsumerStatsImpl.fs. Counted over 55 of the 110 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×4src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling8.7 / 10Strong✓ Tool-verified

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

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

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

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

Strongest change-coupling: ConsumerBuilder.fs↔ConsumerImpl.fs 76%; IProducer.fs↔ConsumerImpl.fs 70%; ProducerImpl.fs↔TransactionMetaStoreHandler.fs 69%

Change coupling: ConsumerBuilder.fs ↔ ConsumerImpl.fs · ×4src/Pulsar.Client/Api/ConsumerBuilder.fs:1
Change-coupling hub: IProducer.fs → IConsumer.fs, ConsumerImpl.fs, MultiTopicsConsumerImpl.fs · ×3src/Pulsar.Client/Api/IProducer.fs

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with MultiTopicsConsumerImpl.fs (2), ConsumerBuilder.fs, ConsumerImpl.fs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with IProducer.fs, ProducerImpl.fs, ClientCnx.fs. — One of this dimension's main actionable groups (3 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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.

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

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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

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

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

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

GD1 · Unfinished & placeholder code9.9 / 10Exemplary✓ Tool-verified

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

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

  • A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×4) — src/Pulsar.Client/Schema/AutoConsumeSchema.fs:9, src/Pulsar.Client/Schema/AutoConsumeSchema.fs:10, src/Pulsar.Client/Schema/AutoProduceBytesSchema.fs:9, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

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.

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
  • `examples/CsharpExamples/CsharpExamples.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — examples/CsharpExamples/CsharpExamples.csproj:9

What to do

  • Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • 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.
PF3 · Async & latency hygiene8.5 / 10Strong✓ Tool-verified

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

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from 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.

  • `Init` is async and calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. — src/Pulsar.Client/Internal/TableViewImpl.fs:45

What to do

  • F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

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

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

  • 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

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

LensScoreRatingImpact
Code Health61%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96%ExemplaryStrongest area.
Maturity62%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness43%Weak — gated by P3, P5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security78%Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance85%StrongSolid.
Unscored — 2 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.

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 73 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.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX6 Interface segregation — no public interfaces
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D10 Test Quality — ~15540 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • 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 — Naming consistency is measured on C# and TypeScript only; F# not measured.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (15,849 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — no coverage collector is wired up
  • DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 55 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • IC1 Incompleteness & stubs — IC1 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks. 11 claim(s) of kinds M4 does not check were not checked (command argument 8, cd 3); M4 checks only links and versions and artefact counts.
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X1 Async correctness — X1 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — X16 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — X18 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — X2 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — X23 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — X3 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — X4 reached only 5% of this repository's production lines — fsharp (15,072 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 6 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · FileScopedPragmaDisable · ×1
  • FileScopedPragmaDisable examples/CsharpExamples/RealWorld.cs:8 — #pragma warning disable 4014 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
Serious — 78 finding(s)
D3 · God Classes · FileTooLong · ×4
  • FileTooLong: Internal/ConsumerImpl.fs src/Pulsar.Client/Internal/ConsumerImpl.fs — FileTooLong — 1802 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1302 over it, 3.60× 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.
  • FileTooLong: Internal/MultiTopicsConsumerImpl.fs src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs — FileTooLong — 1152 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 652 over it, 2.30× 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.
  • FileTooLong: Internal/ProducerImpl.fs src/Pulsar.Client/Internal/ProducerImpl.fs — FileTooLong — 1132 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 632 over it, 2.26× 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.
  • FileTooLong: Internal/ClientCnx.fs src/Pulsar.Client/Internal/ClientCnx.fs — FileTooLong — 923 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 423 over it, 1.85× 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.
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: ConsumerBuilder.fs ↔ ConsumerImpl.fs src/Pulsar.Client/Api/ConsumerBuilder.fs:1 — `src/Pulsar.Client/Api/ConsumerBuilder.fs` and `src/Pulsar.Client/Internal/ConsumerImpl.fs` change together 76% of the time (28 of the 37 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 28 shared commits counted here, the most recent 3 are `e0282f86` Add support for setting `replicateSubscriptionState` for the subscrip…; `a3d343b4` Enabled batching for deadletter producer; `e05ae811` Continue with transactions — run `git show` on any of them.
  • Change coupling: ConsumerImpl.fs ↔ PartitionedProducerImpl.fs src/Pulsar.Client/Internal/ConsumerImpl.fs:1 — `src/Pulsar.Client/Internal/ConsumerImpl.fs` and `src/Pulsar.Client/Internal/PartitionedProducerImpl.fs` change together 63% of the time (22 of the 35 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 22 shared commits counted here, the most recent 3 are `4b029676` Handle stopped children and deleted topics as the Java client does (#…; `ab742a33` Start the stopped-mailbox drain only after failure cleanup; `20519ac2` Align tracking the current message and failing its reply on fault acr… — run `git show` on any of them.
  • Change coupling: MultiTopicsConsumerImpl.fs ↔ ReaderImpl.fs src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:1 — `src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs` and `src/Pulsar.Client/Internal/ReaderImpl.fs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `438f0bbf` Changed several API properties to async methods to avoid deadlocks #247; `5b224213` Merge for IsConnected from v2 (#241); `d617c550` Feautre/175 support seek by function (#180) — run `git show` on any of them.
  • Change coupling: MultiTopicsConsumerImpl.fs ↔ PartitionedProducerImpl.fs src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:1 — `src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs` and `src/Pulsar.Client/Internal/PartitionedProducerImpl.fs` change together 54% of the time (19 of the 35 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `4b029676` Handle stopped children and deleted topics as the Java client does (#…; `ab742a33` Start the stopped-mailbox drain only after failure cleanup; `20519ac2` Align tracking the current message and failing its reply on fault acr… — run `git show` on any of them.
GD1 · Unfinished & placeholder code · Unfinished stub · ×4
  • Unfinished stub — raises a "not implemented" error src/Pulsar.Client/Schema/AutoConsumeSchema.fs:9 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error src/Pulsar.Client/Schema/AutoConsumeSchema.fs:10 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error src/Pulsar.Client/Schema/AutoProduceBytesSchema.fs:9 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — raises a "not implemented" error src/Pulsar.Client/Schema/AutoProduceBytesSchema.fs:10 — A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: ConsumerImpl`1 src/Pulsar.Client/Internal/ConsumerImpl.fs:68 — TooManyMethods — 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: MultiTopicsConsumerImpl`1 src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:90 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: ConsumerBuilder`1 src/Pulsar.Client/Api/ConsumerBuilder.fs:10 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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.
D35 · Change Coupling · Change-coupling hub · ×3
  • Change-coupling hub: IProducer.fs → IConsumer.fs, ConsumerImpl.fs, MultiTopicsConsumerImpl.fs src/Pulsar.Client/Api/IProducer.fs — `src/Pulsar.Client/Api/IProducer.fs` changes together with 3 other files — `src/Pulsar.Client/Api/IConsumer.fs`, `src/Pulsar.Client/Internal/ConsumerImpl.fs`, `src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
  • Change-coupling hub: ProducerImpl.fs → ProducerBuilder.fs, ReaderImpl.fs, TransactionMetaStoreHandler.fs src/Pulsar.Client/Internal/ProducerImpl.fs — `src/Pulsar.Client/Internal/ProducerImpl.fs` changes together with 3 other files — `src/Pulsar.Client/Api/ProducerBuilder.fs`, `src/Pulsar.Client/Internal/ReaderImpl.fs`, `src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
  • Change-coupling hub: ClientCnx.fs → ConnectionHandler.fs, ConsumerImpl.fs, ProducerImpl.fs, TransactionMetaStoreHandler.fs src/Pulsar.Client/Internal/ClientCnx.fs — `src/Pulsar.Client/Internal/ClientCnx.fs` changes together with 4 other files — `src/Pulsar.Client/Internal/ConnectionHandler.fs`, `src/Pulsar.Client/Internal/ConsumerImpl.fs`, `src/Pulsar.Client/Internal/ProducerImpl.fs`, `src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) src/Pulsar.Client/Common/Commands.fs:42 — src/Pulsar.Client/Common/Commands.fs:42-51 | src/Pulsar.Client/Common/Commands.fs:100-110 — 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/Pulsar.Client/Common/Commands.fs:42` 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 (10 lines × 2) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:39 — src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:39-48 | src/Pulsar.Client/Internal/ReaderImpl.fs:42-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:39` 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 (10 lines × 2) src/Pulsar.Client/Common/Commands.fs:27 — src/Pulsar.Client/Common/Commands.fs:27-36 | src/Pulsar.Client/Common/Commands.fs:56-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:227 — src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:227-240 | src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:327-334 — 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/Pulsar.Client/Internal/PartitionedProducerImpl.fs:227` 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. 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 (8 lines × 2) src/Pulsar.Client/Internal/Compression.fs:67 — src/Pulsar.Client/Internal/Compression.fs:67-74 | src/Pulsar.Client/Internal/Compression.fs:97-104 — 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 (8 lines × 2) src/Pulsar.Client/Internal/Compression.fs:58 — src/Pulsar.Client/Internal/Compression.fs:58-65 | src/Pulsar.Client/Internal/Compression.fs:88-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:121 — src/Pulsar.Client/Internal/ConsumerImpl.fs:121-127 | src/Pulsar.Client/Internal/ProducerImpl.fs:164-170 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:1578 — src/Pulsar.Client/Internal/ConsumerImpl.fs:1578-1584 | src/Pulsar.Client/Internal/ProducerImpl.fs:863-869 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) src/Pulsar.Client/Internal/ProducerImpl.fs:1208 — src/Pulsar.Client/Internal/ProducerImpl.fs:1208-1214 | src/Pulsar.Client/Internal/ProducerImpl.fs:1225-1231 — 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/Pulsar.Client/Internal/ProducerImpl.fs:1208` 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:40 — src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:40-46 | src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:160-165 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) src/Pulsar.Client/Internal/NegativeAcksTracker.fs:78 — src/Pulsar.Client/Internal/NegativeAcksTracker.fs:78-83 | src/Pulsar.Client/Internal/UnAckedMessageTracker.fs:122-128 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Pulsar.Client/Internal/NegativeAcksTracker.fs:78` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Pulsar.Client/Internal/UnAckedMessageTracker.fs:132` calls `fillTimePartions` and `src/Pulsar.Client/Internal/NegativeAcksTracker.fs:87` 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 (6 lines × 2) src/Pulsar.Client/Api/PulsarClient.fs:337 — src/Pulsar.Client/Api/PulsarClient.fs:337-342 | src/Pulsar.Client/Api/PulsarClient.fs:362-367 — 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/Pulsar.Client/Api/PulsarClient.fs:337` 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.
D17 · Explicit Debt · TodoComment · ×2
  • TodoComment src/Pulsar.Client.Proto/DynamicJsonConverter.cs:47 — //TODO: Missing Datetime&Bytes Convert — 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/Pulsar.Client.Proto/DynamicJsonConverter.cs:51 — //TODO: more num type — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:89 — src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:89-102 | src/Pulsar.Client/Internal/ProducerStatsImpl.fs:29-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (14 lines × 2) examples/FsharpExamples/RealWorld.fs:50 — examples/FsharpExamples/RealWorld.fs:50-63 | examples/FsharpExamples/Simple.fs:12-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/FsharpExamples/RealWorld.fs:50` 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, `examples/FsharpExamples/RealWorld.fs:64` calls `EnableBatching` and `examples/FsharpExamples/Simple.fs:26` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) src/Pulsar.Client/Internal/BinaryLookupService.fs:65 — src/Pulsar.Client/Internal/BinaryLookupService.fs:65-75 | src/Pulsar.Client/Internal/HttpLookupService.fs:128-138 — before extracting anything, compare `src/Pulsar.Client/Internal/BinaryLookupService.fs` and `src/Pulsar.Client/Internal/HttpLookupService.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Pulsar.Client/Internal/BinaryLookupService.fs:65` 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.
  • Duplicated block (11 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:255 — src/Pulsar.Client/Internal/ConsumerImpl.fs:255-265 | src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:135-145 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Pulsar.Client/Internal/ConsumerImpl.fs:254` calls `OnNegativeAcksSend` and `src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:134` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:1319 — src/Pulsar.Client/Internal/ConsumerImpl.fs:1319-1327 | src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:992-1000 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:1625 — src/Pulsar.Client/Internal/ConsumerImpl.fs:1625-1633 | src/Pulsar.Client/Internal/ConsumerImpl.fs:1655-1663 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:321 — src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:321-330 | src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:361-370 | src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:400-409 — 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 (10 lines × 3) examples/CsharpExamples/Oauth2.cs:51 — examples/CsharpExamples/Oauth2.cs:51-60 | examples/CsharpExamples/Simple.cs:27-36 | examples/CsharpExamples/TlsAuthentication.cs:32-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/CsharpExamples/Oauth2.cs:51` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/CsharpExamples/Oauth2.cs:50` calls `SubscriptionType` and `examples/CsharpExamples/Simple.cs:26` does not — after which the two agree again for 4 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.
D1 · Cyclomatic Complexity · MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cyclomatic 16) · ×1
  • MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cyclomatic 16) src/Pulsar.Client/Common/MessageId.fs:140 — MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D12 · Dependency Hygiene · Prerelease dependency · ×1
  • Prerelease dependency: Expecto.FsCheck — Expecto.FsCheck resolves to 11.1.1-fscheck2, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
D17 · Explicit Debt · CommentedOutCode · ×1
  • CommentedOutCode examples/CsharpExamples/Program.cs:21 — 8 consecutive commented-code lines
D2 · Cognitive Complexity · MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cognitive 33) · ×1
  • MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cognitive 33) src/Pulsar.Client/Common/MessageId.fs:140 — MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (23 pts), match/switch 3 (10 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConsumerImpl`1.ReceiveIndividualMessagesFromBatch (cognitive 23) · ×1
  • ConsumerImpl`1.ReceiveIndividualMessagesFromBatch (cognitive 23) src/Pulsar.Client/Internal/ConsumerImpl.fs:1726 — ConsumerImpl`1.ReceiveIndividualMessagesFromBatch has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 3, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · TooManyFunctions · ×1
  • TooManyFunctions: Tools src/Pulsar.Client/Common/Tools.fs:2 — TooManyFunctions — 31 functions. The bar is 30 functions; this is 1 over it, 1.03× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:1 — src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:1-157 | src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:1-1400 | src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:1-516 | src/Pulsar.Client/Internal/ProducerStatsImpl.fs:1-149 — These 4 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 4 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 4 times.
D4 · Code Duplication · Edited copy of a member (97 corresponding lines) · ×1
  • Edited copy of a member (97 corresponding lines) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:1 — src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:1-97 | src/Pulsar.Client/Internal/ReaderImpl.fs:1-102 — These two members are one piece of code written twice and then edited apart: 97 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 (71 corresponding lines) · ×1
  • Edited copy of a member (71 corresponding lines) src/Pulsar.Client.Proto/MurmurHash3.cs:42 — src/Pulsar.Client.Proto/MurmurHash3.cs:42-112 | src/Pulsar.Client.Proto/MurmurHash3.cs:115-188 — These two members are one piece of code written twice and then edited apart: 71 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 copies of one member (7 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 15+ corresponding lines) src/Pulsar.Client/Schema/BooleanSchema.fs:1 — src/Pulsar.Client/Schema/BooleanSchema.fs:1-15 | src/Pulsar.Client/Schema/ByteSchema.fs:1-16 | src/Pulsar.Client/Schema/DoubleSchema.fs:1-19 | src/Pulsar.Client/Schema/FloatSchema.fs:1-19 | src/Pulsar.Client/Schema/IntSchema.fs:1-20 | src/Pulsar.Client/Schema/LongSchema.fs:1-20 | src/Pulsar.Client/Schema/ShortSchema.fs:1-20 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 15 lines, 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 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) src/Pulsar.Client/Schema/DateSchema.fs:1 — src/Pulsar.Client/Schema/DateSchema.fs:1-18 | src/Pulsar.Client/Schema/TimeSchema.fs:1-19 | src/Pulsar.Client/Schema/TimestampSchema.fs:1-17 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) src/Pulsar.Client/Schema/AutoConsumeSchema.fs:1 — src/Pulsar.Client/Schema/AutoConsumeSchema.fs:1-11 | src/Pulsar.Client/Schema/BytesSchema.fs:1-10 — 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.
D4 · Code Duplication · Duplicated block (70 lines × 2) · ×1
  • Duplicated block (70 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:853 — src/Pulsar.Client/Internal/ConsumerImpl.fs:853-922 | src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:625-694 — 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.
D4 · Code Duplication · Duplicated block (46–47 lines × 2) · ×1
  • Duplicated block (46–47 lines × 2) src/Pulsar.Client.Proto/MurmurHash3.cs:53 — src/Pulsar.Client.Proto/MurmurHash3.cs:53-99 | src/Pulsar.Client.Proto/MurmurHash3.cs:128-173 — 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/Pulsar.Client.Proto/MurmurHash3.cs:53` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Pulsar.Client.Proto/MurmurHash3.cs:176` calls `ReadBytes` and `src/Pulsar.Client.Proto/MurmurHash3.cs:102` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×1
  • Duplicated block (41 lines × 2) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:57 — src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:57-97 | src/Pulsar.Client/Internal/ReaderImpl.fs:62-102 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Pulsar.Client/Internal/ReaderImpl.fs:60` calls `BatchReceivePolicy` and `src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:55` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/Pulsar.Client/Internal/BinaryLookupService.fs:31 — src/Pulsar.Client/Internal/BinaryLookupService.fs:31-48 | src/Pulsar.Client/Internal/HttpLookupService.fs:74-91 — before extracting anything, compare `src/Pulsar.Client/Internal/BinaryLookupService.fs` and `src/Pulsar.Client/Internal/HttpLookupService.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Pulsar.Client/Internal/BinaryLookupService.fs:31` 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.
D4 · Code Duplication · Duplicated block (9–14 lines × 2) · ×1
  • Duplicated block (9–14 lines × 2) src/Pulsar.Client/Internal/BinaryLookupService.fs:156 — src/Pulsar.Client/Internal/BinaryLookupService.fs:156-164 | src/Pulsar.Client/Internal/HttpLookupService.fs:193-206 — before extracting anything, compare `src/Pulsar.Client/Internal/BinaryLookupService.fs` and `src/Pulsar.Client/Internal/HttpLookupService.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Pulsar.Client/Internal/BinaryLookupService.fs:156` 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. 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) src/Pulsar.Client/Api/PulsarClient.fs:347 — src/Pulsar.Client/Api/PulsarClient.fs:347-358 | src/Pulsar.Client/Api/PulsarClient.fs:379-389 — 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/Pulsar.Client/Api/PulsarClient.fs:379` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:768 — src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:768-779 | src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:202-213 — 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.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:461 — src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:461-480 | src/Pulsar.Client/Internal/ProducerImpl.fs:1272-1291 — 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) src/Pulsar.Client/Internal/BinaryLookupService.fs:182 — src/Pulsar.Client/Internal/BinaryLookupService.fs:182-188 | src/Pulsar.Client/Internal/HttpLookupService.fs:259-264 — before extracting anything, compare `src/Pulsar.Client/Internal/BinaryLookupService.fs` and `src/Pulsar.Client/Internal/HttpLookupService.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Pulsar.Client/Internal/BinaryLookupService.fs:182` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:38 — src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:38-44 | src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:88-93 | src/Pulsar.Client/Internal/ProducerStatsImpl.fs:28-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (4–6 lines × 3) · ×1
  • Duplicated block (4–6 lines × 3) src/Pulsar.Client/Internal/HttpLookupService.fs:103 — src/Pulsar.Client/Internal/HttpLookupService.fs:103-106 | src/Pulsar.Client/Internal/HttpLookupService.fs:155-160 | src/Pulsar.Client/Internal/HttpLookupService.fs:208-213 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Pulsar.Client/Internal/HttpLookupService.fs:155` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:334 — src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:334-342 | src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:374-382 | src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:413-421 — 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.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) examples/FsharpExamples/Simple.fs:1 — examples/FsharpExamples/Simple.fs:1-42 | examples/FsharpExamples/TlsAuthentication.fs:1-47 — These two members are one piece of code written twice and then edited apart: 42 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) examples/CsharpExamples/Oauth2.cs:29 — examples/CsharpExamples/Oauth2.cs:29-60 | examples/CsharpExamples/TlsAuthentication.cs:12-41 — 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 · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) examples/FsharpExamples/Oauth2.fs:42 — examples/FsharpExamples/Oauth2.fs:42-59 | examples/FsharpExamples/Simple.fs:25-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/FsharpExamples/Oauth2.fs:42` 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. 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) examples/CsharpExamples/CustomProps.cs:14 — examples/CsharpExamples/CustomProps.cs:14-28 | examples/CsharpExamples/Simple.cs:13-27 — 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) examples/CsharpExamples/Simple.cs:18 — examples/CsharpExamples/Simple.cs:18-33 | examples/CsharpExamples/TlsAuthentication.cs:23-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/CsharpExamples/Simple.cs:18` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/CsharpExamples/TlsAuthentication.cs:21` calls `TlsTrustCertificate`, `Authentication` and `examples/CsharpExamples/Simple.cs:17` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) examples/FsharpExamples/Oauth2.fs:38 — examples/FsharpExamples/Oauth2.fs:38-50 | examples/FsharpExamples/Simple.fs:21-33 | examples/FsharpExamples/TlsAuthentication.fs:26-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/FsharpExamples/Oauth2.fs:38` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/FsharpExamples/Oauth2.fs:37` calls `Authentication`, `ClientCredentials` and `examples/FsharpExamples/Simple.fs:20` does not — after which the two agree again for 4 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: ZeroQueueConsumerImpl`1 (LCOM4 5) src/Pulsar.Client/Internal/ConsumerImpl.fs:2101 — ZeroQueueConsumerImpl`1's methods fall into 5 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 5 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×1
  • Sync-over-async blocking src/Pulsar.Client/Internal/TableViewImpl.fs:45 — `Init` is async and calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 25 finding(s)
D12 · Dependency Hygiene · Outdated · ×6
  • Outdated: Microsoft.Extensions.Caching.Memory src/Pulsar.Client/Pulsar.Client.fsproj:58 — Microsoft.Extensions.Caching.Memory 8.0.1 → 11.0.0 available (referenced by Pulsar.Client).
  • Outdated: Microsoft.Extensions.Logging src/Pulsar.Client/Pulsar.Client.fsproj:59 — Microsoft.Extensions.Logging 8.0.0 → 11.0.0 available (referenced by Pulsar.Client).
  • Outdated: Microsoft.Extensions.Logging.Abstractions src/Pulsar.Client/Pulsar.Client.fsproj:60 — Microsoft.Extensions.Logging.Abstractions 8.0.2 → 11.0.0 available (referenced by Pulsar.Client).
  • Outdated: NSec.Cryptography src/Pulsar.Client/Pulsar.Client.fsproj:54 — NSec.Cryptography 22.4.0 → 26.4.0 available (referenced by Pulsar.Client).
  • Outdated: System.IO.Pipelines src/Pulsar.Client/Pulsar.Client.fsproj:61 — System.IO.Pipelines 8.0.0 → 11.0.0 available (referenced by Pulsar.Client).
  • Outdated: System.Threading.Channels REDACTED:38 — System.Threading.Channels 8.0.0 → 11.0.0 available (referenced by Pulsar.Client.Otel).
D34 · Knowledge Freshness · Orphaned file · ×4
  • Orphaned file src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Pulsar.Client/Internal/ProducerStatsImpl.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Pulsar.Client.Otel/OtelConsumerInterceptor.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Pulsar.Client/Common/ServiceUri.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate src/Pulsar.Client/Internal/ConsumerImpl.fs:807 — `hasWaitingBatchChannel && hasEnoughMessagesForBatchReceive()` appears character-identically in 2 files — src/Pulsar.Client/Internal/ConsumerImpl.fs, src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs. 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/Pulsar.Client/Internal/ConsumerImpl.fs:531 — `shouldContinue && incomingMessages.Count > 0` appears character-identically in 2 files — src/Pulsar.Client/Internal/ConsumerImpl.fs, src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs. 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.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: src/Pulsar.Client/Api/PulsarClient.fs, src/Pulsar.Client/Internal/NegativeAcksTracker.fs, src/Pulsar.Client/Api/PulsarClientException.fs, src/Pulsar.Client/Internal/ReaderImpl.fs, src/Pulsar.Client/Internal/ConsumerInterceptors.fs. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (7 single-owned of 52 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 52 of the 110 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/Pulsar.Client/Transaction/Transaction.fs, src/Pulsar.Client/Auth/Oauth2/TokenClient.fs.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion src/Pulsar.Client.Proto/Pulsar.Client.Proto.csproj:1 — `Pulsar.Client.Proto` overshoots its size bounds (3397 LoC, 260 public types across 91 namespaces). 1 of 4 project(s) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 4 of 55 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 55 of the 110 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/Pulsar.Client/Internal/ConsumerStatsImpl.fs, src/Pulsar.Client/Internal/ProducerStatsImpl.fs, src/Pulsar.Client.Otel/OtelConsumerInterceptor.fs, src/Pulsar.Client/Common/ServiceUri.fs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:3 — No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation examples/CsharpExamples/CsharpExamples.csproj:9 — `examples/CsharpExamples/CsharpExamples.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P6 · Release Hygiene · No changelog · ×1
  • 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.)
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Minor — 19 finding(s)
D12 · Dependency Hygiene · Outdated · ×19
  • Outdated: Microsoft.Extensions.Logging.Console — Microsoft.Extensions.Logging.Console 10.0.1 → 11.0.0 available (referenced by CsharpExamples).
  • Outdated: OpenTelemetry — OpenTelemetry 1.15.3 → 1.21.0 available (referenced by CsharpExamples).
  • Outdated: OpenTelemetry.Exporter.Console — OpenTelemetry.Exporter.Console 1.15.3 → 1.21.0 available (referenced by CsharpExamples).
  • Outdated: Pulsar.Client — Pulsar.Client 3.16.0 → 3.21.0 available (referenced by CsharpExamples).
  • Outdated: FSharp.Core — FSharp.Core 10.1.400 → 11.0.101 available (referenced by FsharpExamples).
  • Outdated: Expecto.FsCheck — Expecto.FsCheck 11.1.1-fscheck2 → 11.1.1 available (referenced by UnitTests).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 18.0.1 → 18.12.0 available (referenced by UnitTests).
  • Outdated: Serilog — Serilog 4.3.0 → 4.4.0 available (referenced by UnitTests).
  • Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 10.0.1 → 11.0.0 available (referenced by IntegrationTests).
  • Outdated: Apache.Avro — Apache.Avro 1.12.1 → 1.12.2 available (referenced by Pulsar.Client).
  • Outdated: AvroSchemaGenerator — AvroSchemaGenerator 2.9.2 → 2.10.0 available (referenced by Pulsar.Client).
  • Outdated: K4os.Compression.LZ4 — K4os.Compression.LZ4 1.3.6 → 1.3.8 available (referenced by Pulsar.Client).
  • Outdated: Microsoft.IO.RecyclableMemoryStream — Microsoft.IO.RecyclableMemoryStream 3.0.0 → 4.0.1 available (referenced by Pulsar.Client).
  • Outdated: Pipelines.Sockets.Unofficial — Pipelines.Sockets.Unofficial 2.2.8 → 2.2.16 available (referenced by Pulsar.Client).
  • Outdated: protobuf-net — protobuf-net 3.2.30 → 3.4.40 available (referenced by Pulsar.Client).
  • Outdated: protobuf-net.Reflection — protobuf-net.Reflection 3.2.12 → 3.4.40 available (referenced by Pulsar.Client).
  • Outdated: zlib.net-mutliplatform — zlib.net-mutliplatform 1.0.6 → 1.1.0 available (referenced by Pulsar.Client).
  • Outdated: ZstdNet — ZstdNet 1.4.5 → 1.5.7 available (referenced by Pulsar.Client).
  • Outdated: OpenTelemetry.Api — OpenTelemetry.Api 1.15.3 → 1.21.0 available (referenced by Pulsar.Client.Otel).

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4ed4ecdcbb142acbc5e7fcd5e591dee/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4ed4ecdcbb142acbc5e7fcd5e591dee/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .6artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list Pulsar.Client.sln package --vulnerable --include-transitive --format json1artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-1fcc842443c14ec9b113e09e39696b9d0artifacts/raw/osv-scanner.json

Run 01a1d454-9958-7ca3-ac6e-5c1041e32532 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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