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.
If Production Readiness rose from 43 to 70, the lowest score rated Strong, the score would rise from 56 to about 66.
New since the last survey: 16 findings
- 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
Fixed since the last survey: 22 findings
- 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 problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.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. |
| Size | Small: 15,849 lines of product code |
| Comment lines | The estimate prices 15,823 lines. Comment lines count towards the size of 15,849 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 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.Schema | 11 Pulsar.Client.Internal | 12 Pulsar.Client.Transaction | 13 Pulsar.Client.Common | 14 Pulsar.Client.Common.ConsumerBase | 15 Pulsar.Client.Common.ServiceUriModule | 16 Pulsar.Client.Internal.BatchHelpers | 17 Pulsar.Client.Internal.CompressionCodec | 18 Pulsar.Client.Api | 19 Pulsar.Client.Api.AutoClusterFailoverLogic | 20 Pulsar.Client.Api.SchemaUtils | 21 Pulsar.Client.Auth | 22 Pulsar.Client.Auth.OAuth2 | 23 Pulsar.Client.Common.Commands | 24 Pulsar.Client.Crypto | 25 Pulsar.Client.Otel.OTelProducerInterceptor | 26 Pulsar.Client.Otel.OtelConsumerInterceptor | 27 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.Schema | 37 | 29 | |||||||||||||||||||||||||
| 11 Pulsar.Client.Internal | 2 | 5 | 61 | 32 | |||||||||||||||||||||||
| 12 Pulsar.Client.Transaction | 2 | 1 | 2 | ||||||||||||||||||||||||
| 13 Pulsar.Client.Common | 1 | 1 | |||||||||||||||||||||||||
| 14 Pulsar.Client.Common.ConsumerBase | 5 | 1 | |||||||||||||||||||||||||
| 15 Pulsar.Client.Common.ServiceUriModule | 1 | ||||||||||||||||||||||||||
| 16 Pulsar.Client.Internal.BatchHelpers | 1 | ||||||||||||||||||||||||||
| 17 Pulsar.Client.Internal.CompressionCodec | 5 | 1 | |||||||||||||||||||||||||
| 18 Pulsar.Client.Api | 6 | 21 | 8 | 89 | 4 | ||||||||||||||||||||||
| 19 Pulsar.Client.Api.AutoClusterFailoverLogic | 2 | ||||||||||||||||||||||||||
| 20 Pulsar.Client.Api.SchemaUtils | 3 | 1 | |||||||||||||||||||||||||
| 21 Pulsar.Client.Auth | 6 | ||||||||||||||||||||||||||
| 22 Pulsar.Client.Auth.OAuth2 | 2 | ||||||||||||||||||||||||||
| 23 Pulsar.Client.Common.Commands | 1 | 9 | 1 | ||||||||||||||||||||||||
| 24 Pulsar.Client.Crypto | 2 | 2 | |||||||||||||||||||||||||
| 25 Pulsar.Client.Otel.OTelProducerInterceptor | 2 | 2 | |||||||||||||||||||||||||
| 26 Pulsar.Client.Otel.OtelConsumerInterceptor | 3 | 2 | |||||||||||||||||||||||||
| 27 Pulsar.Client.Auth.DefaultImplementation | 2 | 1 |
10→13 Pulsar.Client.Schema uses Pulsar.Client.Common part of a loop✕
- Connections
- 37 pairs of types, where a type in Pulsar.Client.Schema uses a type in Pulsar.Client.Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Pulsar.Client.Schema.AutoConsumeSchemaStub→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.AutoProduceBytesSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.AutoProduceBytesSchemaStub→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.AvroSchema`1→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.AvroSchema`1→Pulsar.Client.Common.SchemaVersionPulsar.Client.Schema.BooleanSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.ByteSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.BytesSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.DateSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.DoubleSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.FloatSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.GenericAvroSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.GenericAvroSchema→Pulsar.Client.Common.SchemaVersionPulsar.Client.Schema.GenericAvroSchema→Pulsar.Client.Common.TopicSchemaPulsar.Client.Schema.GenericJsonSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.GenericJsonSchema→Pulsar.Client.Common.SchemaVersionPulsar.Client.Schema.GenericJsonSchema→Pulsar.Client.Common.TopicSchemaPulsar.Client.Schema.GenericProtobufNativeSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.GenericProtobufNativeSchema→Pulsar.Client.Common.SchemaVersionPulsar.Client.Schema.GenericProtobufNativeSchema→Pulsar.Client.Common.TopicSchemaPulsar.Client.Schema.IKeyValueProcessor→Pulsar.Client.Common.KeyValueEncodingTypePulsar.Client.Schema.IntSchema→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.JsonSchema`1→Pulsar.Client.Common.SchemaInfoPulsar.Client.Schema.KeyValueProcessor`2→Pulsar.Client.Common.KeyValueEncodingTypePulsar.Client.Schema.KeyValueSchema→Pulsar.Client.Common.KeyValueEncodingType
- Direction
- Pulsar.Client.Schema uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Schema, while a change to Pulsar.Client.Schema can't break Pulsar.Client.Common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→18 Pulsar.Client.Schema uses Pulsar.Client.Api part of a loop✕
- Connections
- 29 pairs of types, where a type in Pulsar.Client.Schema uses a type in Pulsar.Client.Api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Pulsar.Client.Schema.AutoConsumeSchemaStub→Pulsar.Client.Api.GenericRecordPulsar.Client.Schema.AutoConsumeSchemaStub→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.AutoProduceBytesSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.AutoProduceBytesSchemaStub→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.AvroSchema`1→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.BooleanSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.ByteSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.BytesSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.DateSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.DoubleSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.FloatSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.GenericAvroSchema→Pulsar.Client.Api.GenericRecordPulsar.Client.Schema.GenericAvroSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.GenericJsonSchema→Pulsar.Client.Api.GenericRecordPulsar.Client.Schema.GenericJsonSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.GenericProtobufNativeSchema→Pulsar.Client.Api.GenericRecordPulsar.Client.Schema.GenericProtobufNativeSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.IntSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.JsonSchema`1→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.KeyValueProcessor→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.KeyValueSchema`2→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.LongSchema→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.MultiVersionSchemaInfoProvider→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.ProtoBufNativeSchema`1→Pulsar.Client.Api.ISchema`1Pulsar.Client.Schema.ProtobufSchema`1→Pulsar.Client.Api.ISchema`1
- Direction
- Pulsar.Client.Schema uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Schema, while a change to Pulsar.Client.Schema can't break Pulsar.Client.Api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→10 Pulsar.Client.Internal uses Pulsar.Client.Schema✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Internal uses a type in Pulsar.Client.Schema.
- The types involved
Pulsar.Client.Internal.MultiTopicsReaderImpl`1→Pulsar.Client.Schema.MultiVersionSchemaInfoProviderPulsar.Client.Internal.ReaderImpl`1→Pulsar.Client.Schema.MultiVersionSchemaInfoProvider
- Direction
- Pulsar.Client.Internal uses Pulsar.Client.Schema, so a change to Pulsar.Client.Schema can break Pulsar.Client.Internal, while a change to Pulsar.Client.Internal can't break Pulsar.Client.Schema.
- Position
- Below the diagonal: Pulsar.Client.Internal uses a module listed above it, which is the healthy direction.
11→12 Pulsar.Client.Internal uses Pulsar.Client.Transaction part of a loop✕
- Connections
- 5 pairs of types, where a type in Pulsar.Client.Internal uses a type in Pulsar.Client.Transaction.
- The types involved
Pulsar.Client.Internal.MessageContainer`1→Pulsar.Client.Transaction.TxnIdPulsar.Client.Internal.OpSendMsgWrapper`1→Pulsar.Client.Transaction.TxnIdPulsar.Client.Internal.TransactionMetaStoreHandler→Pulsar.Client.Transaction.TxnIdPulsar.Client.Internal.TransactionMetaStoreMessage→Pulsar.Client.Transaction.TxnIdPulsar.Client.Internal.TxnRequest→Pulsar.Client.Transaction.TxnId
- Direction
- Pulsar.Client.Internal uses Pulsar.Client.Transaction, so a change to Pulsar.Client.Transaction can break Pulsar.Client.Internal, while a change to Pulsar.Client.Internal can't break Pulsar.Client.Transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→13 Pulsar.Client.Internal uses Pulsar.Client.Common part of a loop✕
- Connections
- 61 pairs of types, where a type in Pulsar.Client.Internal uses a type in Pulsar.Client.Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Pulsar.Client.Internal.AcknowledgmentsGroupingTracker→Pulsar.Client.Common.AckTypePulsar.Client.Internal.AcknowledgmentsGroupingTracker→Pulsar.Client.Common.MessageIdPulsar.Client.Internal.BinaryLookupService→Pulsar.Client.Common.BrokerPulsar.Client.Internal.BinaryLookupService→Pulsar.Client.Common.NamespaceNamePulsar.Client.Internal.BinaryLookupService→Pulsar.Client.Common.PartitionedTopicMetadataPulsar.Client.Internal.BinaryLookupService→Pulsar.Client.Common.SchemaVersionPulsar.Client.Internal.BinaryLookupService→Pulsar.Client.Common.TopicNamePulsar.Client.Internal.BinaryLookupService→Pulsar.Client.Common.TopicSchemaPulsar.Client.Internal.ChunkedMessageCtx→Pulsar.Client.Common.CompressionTypePulsar.Client.Internal.ChunkedMessageCtx→Pulsar.Client.Common.MessageIdPulsar.Client.Internal.ChunkedMessageCtx→Pulsar.Client.Common.RawMessagePulsar.Client.Internal.ChunkedMessageTracker→Pulsar.Client.Common.MessageIdPulsar.Client.Internal.ChunkedMessageTracker→Pulsar.Client.Common.MetadataPulsar.Client.Internal.ChunkedMessageTracker→Pulsar.Client.Common.RawMessagePulsar.Client.Internal.ClientCnx→Pulsar.Client.Common.BrokerPulsar.Client.Internal.ClientCnx→Pulsar.Client.Common.ConnectionPulsar.Client.Internal.ClientCnx→Pulsar.Client.Common.PulsarResponseTypePulsar.Client.Internal.ConnectionPool→Pulsar.Client.Common.BrokerPulsar.Client.Internal.ConsumerInterceptors`1→Pulsar.Client.Common.MessageIdPulsar.Client.Internal.ConsumerInterceptors`1→Pulsar.Client.Common.Message`1Pulsar.Client.Internal.ConsumerStatsImpl→Pulsar.Client.Common.ConsumerStatsPulsar.Client.Internal.DeadLetterProcessor`1→Pulsar.Client.Common.MessageIdPulsar.Client.Internal.DeadLetterProcessor`1→Pulsar.Client.Common.Message`1Pulsar.Client.Internal.DefaultBatchMessageContainer`1→Pulsar.Client.Common.BatchItem`1Pulsar.Client.Internal.HttpLookupService→Pulsar.Client.Common.Broker
- Direction
- Pulsar.Client.Internal uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Internal, while a change to Pulsar.Client.Internal can't break Pulsar.Client.Common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→18 Pulsar.Client.Internal uses Pulsar.Client.Api part of a loop✕
- Connections
- 32 pairs of types, where a type in Pulsar.Client.Internal uses a type in Pulsar.Client.Api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Pulsar.Client.Internal.BinaryLookupService→Pulsar.Client.Api.PulsarClientConfigurationPulsar.Client.Internal.BinaryLookupService→Pulsar.Client.Api.ServiceInfoPulsar.Client.Internal.ClientCnx→Pulsar.Client.Api.PulsarClientConfigurationPulsar.Client.Internal.ConnectionPool→Pulsar.Client.Api.PulsarClientConfigurationPulsar.Client.Internal.ConsumerInterceptors`1→Pulsar.Client.Api.IConsumerInterceptor`1Pulsar.Client.Internal.ConsumerInterceptors`1→Pulsar.Client.Api.IConsumer`1Pulsar.Client.Internal.DeadLetterProcessor`1→Pulsar.Client.Api.DeadLetterPolicyPulsar.Client.Internal.DeadLetterProcessor`1→Pulsar.Client.Api.IDeadLetterProcessor`1Pulsar.Client.Internal.DefaultBatchMessageContainer`1→Pulsar.Client.Api.ProducerConfigurationPulsar.Client.Internal.HttpLookupService→Pulsar.Client.Api.PulsarClientConfigurationPulsar.Client.Internal.HttpLookupService→Pulsar.Client.Api.ServiceInfoPulsar.Client.Internal.ILookupService→Pulsar.Client.Api.ServiceInfoPulsar.Client.Internal.KeyBasedBatchMessageContainer`1→Pulsar.Client.Api.ProducerConfigurationPulsar.Client.Internal.MessageContainer`1→Pulsar.Client.Api.ProducerConfigurationPulsar.Client.Internal.MultiTopicsReaderImpl`1→Pulsar.Client.Api.ConsumerInitInfo`1Pulsar.Client.Internal.MultiTopicsReaderImpl`1→Pulsar.Client.Api.IReader`1Pulsar.Client.Internal.MultiTopicsReaderImpl`1→Pulsar.Client.Api.ISchema`1Pulsar.Client.Internal.MultiTopicsReaderImpl`1→Pulsar.Client.Api.PulsarClientConfigurationPulsar.Client.Internal.MultiTopicsReaderImpl`1→Pulsar.Client.Api.ReaderConfigurationPulsar.Client.Internal.ProducerInterceptors`1→Pulsar.Client.Api.IProducerInterceptor`1Pulsar.Client.Internal.ProducerInterceptors`1→Pulsar.Client.Api.IProducer`1Pulsar.Client.Internal.PulsarHttpClient→Pulsar.Client.Api.AuthenticationPulsar.Client.Internal.ReaderImpl`1→Pulsar.Client.Api.BatchReceivePolicyPulsar.Client.Internal.ReaderImpl`1→Pulsar.Client.Api.IReader`1Pulsar.Client.Internal.ReaderImpl`1→Pulsar.Client.Api.ISchema`1
- Direction
- Pulsar.Client.Internal uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Internal, while a change to Pulsar.Client.Internal can't break Pulsar.Client.Api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→11 Pulsar.Client.Transaction uses Pulsar.Client.Internal✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Transaction uses a type in Pulsar.Client.Internal.
- The types involved
Pulsar.Client.Transaction.TransactionCoordinatorClient→Pulsar.Client.Internal.ConnectionPoolPulsar.Client.Transaction.TransactionCoordinatorClient→Pulsar.Client.Internal.ILookupService
- Direction
- Pulsar.Client.Transaction uses Pulsar.Client.Internal, so a change to Pulsar.Client.Internal can break Pulsar.Client.Transaction, while a change to Pulsar.Client.Transaction can't break Pulsar.Client.Internal.
- Position
- Below the diagonal: Pulsar.Client.Transaction uses a module listed above it, which is the healthy direction.
12→13 Pulsar.Client.Transaction uses Pulsar.Client.Common part of a loop✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Transaction uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Transaction.Transaction→Pulsar.Client.Common.MessageId
- Direction
- Pulsar.Client.Transaction uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Transaction, while a change to Pulsar.Client.Transaction can't break Pulsar.Client.Common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→18 Pulsar.Client.Transaction uses Pulsar.Client.Api part of a loop✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Transaction uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Transaction.TransactionBuilder→Pulsar.Client.Api.TransactionConfigurationPulsar.Client.Transaction.TransactionCoordinatorClient→Pulsar.Client.Api.PulsarClientConfiguration
- Direction
- Pulsar.Client.Transaction uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Transaction, while a change to Pulsar.Client.Transaction can't break Pulsar.Client.Api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→12 Pulsar.Client.Common uses Pulsar.Client.Transaction✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Common uses a type in Pulsar.Client.Transaction.
- The types involved
Pulsar.Client.Common.MessageBuilder`1→Pulsar.Client.Transaction.Transaction
- Direction
- Pulsar.Client.Common uses Pulsar.Client.Transaction, so a change to Pulsar.Client.Transaction can break Pulsar.Client.Common, while a change to Pulsar.Client.Common can't break Pulsar.Client.Transaction.
- Position
- Below the diagonal: Pulsar.Client.Common uses a module listed above it, which is the healthy direction.
13→18 Pulsar.Client.Common uses Pulsar.Client.Api part of a loop✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Common uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Common.Message`1→Pulsar.Client.Api.ISchema`1
- Direction
- Pulsar.Client.Common uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Common, while a change to Pulsar.Client.Common can't break Pulsar.Client.Api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→13 Pulsar.Client.Common.ConsumerBase uses Pulsar.Client.Common✕
- Connections
- 5 pairs of types, where a type in Pulsar.Client.Common.ConsumerBase uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Common.ConsumerBase.ConsumerBase→Pulsar.Client.Common.Message`1Pulsar.Client.Common.ConsumerBase.ConsumerBase→Pulsar.Client.Common.Messages`1Pulsar.Client.Common.ConsumerBase.ConsumerBase→Pulsar.Client.Common.SubscriptionTypePulsar.Client.Common.ConsumerBase.ReceiveCallback`1→Pulsar.Client.Common.Message`1Pulsar.Client.Common.ConsumerBase.ReceiveCallbacks`1→Pulsar.Client.Common.Messages`1
- Direction
- Pulsar.Client.Common.ConsumerBase uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Common.ConsumerBase, while a change to Pulsar.Client.Common.ConsumerBase can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Common.ConsumerBase uses a module listed above it, which is the healthy direction.
14→18 Pulsar.Client.Common.ConsumerBase uses Pulsar.Client.Api part of a loop✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Common.ConsumerBase uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Common.ConsumerBase.ConsumerBase→Pulsar.Client.Api.BatchReceivePolicy
- Direction
- Pulsar.Client.Common.ConsumerBase uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Common.ConsumerBase, while a change to Pulsar.Client.Common.ConsumerBase can't break Pulsar.Client.Api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→13 Pulsar.Client.Common.ServiceUriModule uses Pulsar.Client.Common✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Common.ServiceUriModule uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Common.ServiceUriModule.ServiceUriModule→Pulsar.Client.Common.ServiceUri
- Direction
- Pulsar.Client.Common.ServiceUriModule uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Common.ServiceUriModule, while a change to Pulsar.Client.Common.ServiceUriModule can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Common.ServiceUriModule uses a module listed above it, which is the healthy direction.
16→13 Pulsar.Client.Internal.BatchHelpers uses Pulsar.Client.Common✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Internal.BatchHelpers uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Internal.BatchHelpers.BatchHelpers→Pulsar.Client.Common.BatchItem`1
- Direction
- Pulsar.Client.Internal.BatchHelpers uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Internal.BatchHelpers, while a change to Pulsar.Client.Internal.BatchHelpers can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Internal.BatchHelpers uses a module listed above it, which is the healthy direction.
17→11 Pulsar.Client.Internal.CompressionCodec uses Pulsar.Client.Internal✕
- Connections
- 5 pairs of types, where a type in Pulsar.Client.Internal.CompressionCodec uses a type in Pulsar.Client.Internal.
- The types involved
Pulsar.Client.Internal.CompressionCodec.CompressionCodec→Pulsar.Client.Internal.ICompressionCodecPulsar.Client.Internal.CompressionCodec.LZ4Compression→Pulsar.Client.Internal.ICompressionCodecPulsar.Client.Internal.CompressionCodec.SnappyCompression→Pulsar.Client.Internal.ICompressionCodecPulsar.Client.Internal.CompressionCodec.ZLibCompression→Pulsar.Client.Internal.ICompressionCodecPulsar.Client.Internal.CompressionCodec.ZstdCompression→Pulsar.Client.Internal.ICompressionCodec
- Direction
- Pulsar.Client.Internal.CompressionCodec uses Pulsar.Client.Internal, so a change to Pulsar.Client.Internal can break Pulsar.Client.Internal.CompressionCodec, while a change to Pulsar.Client.Internal.CompressionCodec can't break Pulsar.Client.Internal.
- Position
- Below the diagonal: Pulsar.Client.Internal.CompressionCodec uses a module listed above it, which is the healthy direction.
17→13 Pulsar.Client.Internal.CompressionCodec uses Pulsar.Client.Common✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Internal.CompressionCodec uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Internal.CompressionCodec.CompressionCodec→Pulsar.Client.Common.CompressionType
- Direction
- Pulsar.Client.Internal.CompressionCodec uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Internal.CompressionCodec, while a change to Pulsar.Client.Internal.CompressionCodec can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Internal.CompressionCodec uses a module listed above it, which is the healthy direction.
18→10 Pulsar.Client.Api uses Pulsar.Client.Schema✕
- Connections
- 6 pairs of types, where a type in Pulsar.Client.Api uses a type in Pulsar.Client.Schema.
- The types involved
Pulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Schema.MultiVersionSchemaInfoProviderPulsar.Client.Api.ConsumerInitInfo`1→Pulsar.Client.Schema.MultiVersionSchemaInfoProviderPulsar.Client.Api.ProducerImpl`1→Pulsar.Client.Schema.IKeyValueProcessorPulsar.Client.Api.PulsarClient→Pulsar.Client.Schema.MultiVersionSchemaInfoProviderPulsar.Client.Api.PulsarClientMessage→Pulsar.Client.Schema.MultiVersionSchemaInfoProviderPulsar.Client.Api.ZeroQueueConsumerImpl`1→Pulsar.Client.Schema.MultiVersionSchemaInfoProvider
- Direction
- Pulsar.Client.Api uses Pulsar.Client.Schema, so a change to Pulsar.Client.Schema can break Pulsar.Client.Api, while a change to Pulsar.Client.Api can't break Pulsar.Client.Schema.
- Position
- Below the diagonal: Pulsar.Client.Api uses a module listed above it, which is the healthy direction.
18→11 Pulsar.Client.Api uses Pulsar.Client.Internal✕
- Connections
- 21 pairs of types, where a type in Pulsar.Client.Api uses a type in Pulsar.Client.Internal.
- The types involved
Pulsar.Client.Api.AutoServiceInfo→Pulsar.Client.Internal.EndPointResolverPulsar.Client.Api.ConsumerBuilder`1→Pulsar.Client.Internal.ConsumerInterceptors`1Pulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Internal.ConnectionPoolPulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Internal.ConsumerInterceptors`1Pulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Internal.ILookupServicePulsar.Client.Api.ConsumerMessage`1→Pulsar.Client.Internal.ClientCnxPulsar.Client.Api.MultiTopicsConsumerImpl`1→Pulsar.Client.Internal.ConnectionPoolPulsar.Client.Api.MultiTopicsConsumerImpl`1→Pulsar.Client.Internal.ConsumerInterceptors`1Pulsar.Client.Api.MultiTopicsConsumerImpl`1→Pulsar.Client.Internal.ILookupServicePulsar.Client.Api.PartitionedProducerImpl`1→Pulsar.Client.Internal.ConnectionPoolPulsar.Client.Api.PartitionedProducerImpl`1→Pulsar.Client.Internal.ILookupServicePulsar.Client.Api.PartitionedProducerImpl`1→Pulsar.Client.Internal.ProducerInterceptors`1Pulsar.Client.Api.ProducerBuilder`1→Pulsar.Client.Internal.ProducerInterceptors`1Pulsar.Client.Api.ProducerImpl`1→Pulsar.Client.Internal.ConnectionPoolPulsar.Client.Api.ProducerImpl`1→Pulsar.Client.Internal.ILookupServicePulsar.Client.Api.ProducerImpl`1→Pulsar.Client.Internal.ProducerInterceptors`1Pulsar.Client.Api.ProducerMessage`1→Pulsar.Client.Internal.ClientCnxPulsar.Client.Api.PulsarClient→Pulsar.Client.Internal.ConsumerInterceptors`1Pulsar.Client.Api.PulsarClient→Pulsar.Client.Internal.ProducerInterceptors`1Pulsar.Client.Api.ZeroQueueConsumerImpl`1→Pulsar.Client.Internal.ConsumerInterceptors`1Pulsar.Client.Api.ZeroQueueConsumerImpl`1→Pulsar.Client.Internal.ILookupService
- Direction
- Pulsar.Client.Api uses Pulsar.Client.Internal, so a change to Pulsar.Client.Internal can break Pulsar.Client.Api, while a change to Pulsar.Client.Api can't break Pulsar.Client.Internal.
- Position
- Below the diagonal: Pulsar.Client.Api uses a module listed above it, which is the healthy direction.
18→12 Pulsar.Client.Api uses Pulsar.Client.Transaction✕
- Connections
- 8 pairs of types, where a type in Pulsar.Client.Api uses a type in Pulsar.Client.Transaction.
- The types involved
Pulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Transaction.TransactionPulsar.Client.Api.IConsumer`1→Pulsar.Client.Transaction.TransactionPulsar.Client.Api.IProducer`1→Pulsar.Client.Transaction.TransactionPulsar.Client.Api.MultiTopicConsumerMessage`1→Pulsar.Client.Transaction.TransactionPulsar.Client.Api.MultiTopicsConsumerImpl`1→Pulsar.Client.Transaction.TransactionPulsar.Client.Api.PartitionedProducerImpl`1→Pulsar.Client.Transaction.TransactionPulsar.Client.Api.ProducerImpl`1→Pulsar.Client.Transaction.TransactionPulsar.Client.Api.PulsarClient→Pulsar.Client.Transaction.TransactionBuilder
- Direction
- Pulsar.Client.Api uses Pulsar.Client.Transaction, so a change to Pulsar.Client.Transaction can break Pulsar.Client.Api, while a change to Pulsar.Client.Api can't break Pulsar.Client.Transaction.
- Position
- Below the diagonal: Pulsar.Client.Api uses a module listed above it, which is the healthy direction.
18→13 Pulsar.Client.Api uses Pulsar.Client.Common✕
- Connections
- 89 pairs of types, where a type in Pulsar.Client.Api uses a type in Pulsar.Client.Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Pulsar.Client.Api.AuthenticationDataProvider→Pulsar.Client.Common.AuthDataPulsar.Client.Api.BatchAddResponse`1→Pulsar.Client.Common.Messages`1Pulsar.Client.Api.ChildConsumerInfo`1→Pulsar.Client.Common.TopicNamePulsar.Client.Api.ConsumerBuilder`1→Pulsar.Client.Common.ConsumerCryptoFailureActionPulsar.Client.Api.ConsumerBuilder`1→Pulsar.Client.Common.SubscriptionInitialPositionPulsar.Client.Api.ConsumerBuilder`1→Pulsar.Client.Common.SubscriptionModePulsar.Client.Api.ConsumerBuilder`1→Pulsar.Client.Common.SubscriptionTypePulsar.Client.Api.ConsumerConfiguration`1→Pulsar.Client.Common.ConsumerCryptoFailureActionPulsar.Client.Api.ConsumerConfiguration`1→Pulsar.Client.Common.SubscriptionInitialPositionPulsar.Client.Api.ConsumerConfiguration`1→Pulsar.Client.Common.SubscriptionModePulsar.Client.Api.ConsumerConfiguration`1→Pulsar.Client.Common.SubscriptionTypePulsar.Client.Api.ConsumerConfiguration`1→Pulsar.Client.Common.TopicNamePulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Common.ConsumerStatsPulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Common.MessageIdPulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Common.Message`1Pulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Common.Messages`1Pulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Common.RawMessagePulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Common.SeekTypePulsar.Client.Api.ConsumerImpl`1→Pulsar.Client.Common.TopicNamePulsar.Client.Api.ConsumerInitInfo`1→Pulsar.Client.Common.PartitionedTopicMetadataPulsar.Client.Api.ConsumerInitInfo`1→Pulsar.Client.Common.TopicNamePulsar.Client.Api.ConsumerMessage`1→Pulsar.Client.Common.AckTypePulsar.Client.Api.ConsumerMessage`1→Pulsar.Client.Common.ConsumerStatsPulsar.Client.Api.ConsumerMessage`1→Pulsar.Client.Common.MessageIdPulsar.Client.Api.ConsumerMessage`1→Pulsar.Client.Common.Message`1
- Direction
- Pulsar.Client.Api uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Api, while a change to Pulsar.Client.Api can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Api uses a module listed above it, which is the healthy direction.
18→14 Pulsar.Client.Api uses Pulsar.Client.Common.ConsumerBase✕
- Connections
- 4 pairs of types, where a type in Pulsar.Client.Api uses a type in Pulsar.Client.Common.ConsumerBase.
- The types involved
Pulsar.Client.Api.ConsumerMessage`1→Pulsar.Client.Common.ConsumerBase.ReceiveCallback`1Pulsar.Client.Api.ConsumerMessage`1→Pulsar.Client.Common.ConsumerBase.ReceiveCallbacks`1Pulsar.Client.Api.MultiTopicConsumerMessage`1→Pulsar.Client.Common.ConsumerBase.ReceiveCallback`1Pulsar.Client.Api.MultiTopicConsumerMessage`1→Pulsar.Client.Common.ConsumerBase.ReceiveCallbacks`1
- Direction
- Pulsar.Client.Api uses Pulsar.Client.Common.ConsumerBase, so a change to Pulsar.Client.Common.ConsumerBase can break Pulsar.Client.Api, while a change to Pulsar.Client.Api can't break Pulsar.Client.Common.ConsumerBase.
- Position
- Below the diagonal: Pulsar.Client.Api uses a module listed above it, which is the healthy direction.
19→18 Pulsar.Client.Api.AutoClusterFailoverLogic uses Pulsar.Client.Api✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Api.AutoClusterFailoverLogic uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Api.AutoClusterFailoverLogic.AutoClusterFailoverLogic→Pulsar.Client.Api.AutoClusterConfigPulsar.Client.Api.AutoClusterFailoverLogic.AutoClusterFailoverLogic→Pulsar.Client.Api.AutoClusterState
- Direction
- Pulsar.Client.Api.AutoClusterFailoverLogic uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Api.AutoClusterFailoverLogic, while a change to Pulsar.Client.Api.AutoClusterFailoverLogic can't break Pulsar.Client.Api.
- Position
- Below the diagonal: Pulsar.Client.Api.AutoClusterFailoverLogic uses a module listed above it, which is the healthy direction.
20→13 Pulsar.Client.Api.SchemaUtils uses Pulsar.Client.Common✕
- Connections
- 3 pairs of types, where a type in Pulsar.Client.Api.SchemaUtils uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Api.SchemaUtils.SchemaUtils→Pulsar.Client.Common.RawMessagePulsar.Client.Api.SchemaUtils.SchemaUtils→Pulsar.Client.Common.SchemaInfoPulsar.Client.Api.SchemaUtils.SchemaUtils→Pulsar.Client.Common.SchemaType
- Direction
- Pulsar.Client.Api.SchemaUtils uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Api.SchemaUtils, while a change to Pulsar.Client.Api.SchemaUtils can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Api.SchemaUtils uses a module listed above it, which is the healthy direction.
20→18 Pulsar.Client.Api.SchemaUtils uses Pulsar.Client.Api✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Api.SchemaUtils uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Api.SchemaUtils.SchemaUtils→Pulsar.Client.Api.Field
- Direction
- Pulsar.Client.Api.SchemaUtils uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Api.SchemaUtils, while a change to Pulsar.Client.Api.SchemaUtils can't break Pulsar.Client.Api.
- Position
- Below the diagonal: Pulsar.Client.Api.SchemaUtils uses a module listed above it, which is the healthy direction.
21→18 Pulsar.Client.Auth uses Pulsar.Client.Api✕
- Connections
- 6 pairs of types, where a type in Pulsar.Client.Auth uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Auth.AuthenticationDataTls→Pulsar.Client.Api.AuthenticationDataProviderPulsar.Client.Auth.AuthenticationDataToken→Pulsar.Client.Api.AuthenticationDataProviderPulsar.Client.Auth.AuthenticationTls→Pulsar.Client.Api.AuthenticationPulsar.Client.Auth.AuthenticationTls→Pulsar.Client.Api.AuthenticationDataProviderPulsar.Client.Auth.AuthenticationToken→Pulsar.Client.Api.AuthenticationPulsar.Client.Auth.AuthenticationToken→Pulsar.Client.Api.AuthenticationDataProvider
- Direction
- Pulsar.Client.Auth uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Auth, while a change to Pulsar.Client.Auth can't break Pulsar.Client.Api.
- Position
- Below the diagonal: Pulsar.Client.Auth uses a module listed above it, which is the healthy direction.
22→18 Pulsar.Client.Auth.OAuth2 uses Pulsar.Client.Api✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Auth.OAuth2 uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Auth.OAuth2.AuthenticationOauth2→Pulsar.Client.Api.AuthenticationPulsar.Client.Auth.OAuth2.AuthenticationOauth2→Pulsar.Client.Api.AuthenticationDataProvider
- Direction
- Pulsar.Client.Auth.OAuth2 uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Auth.OAuth2, while a change to Pulsar.Client.Auth.OAuth2 can't break Pulsar.Client.Api.
- Position
- Below the diagonal: Pulsar.Client.Auth.OAuth2 uses a module listed above it, which is the healthy direction.
23→12 Pulsar.Client.Common.Commands uses Pulsar.Client.Transaction✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Common.Commands uses a type in Pulsar.Client.Transaction.
- The types involved
Pulsar.Client.Common.Commands.Commands→Pulsar.Client.Transaction.TxnId
- Direction
- Pulsar.Client.Common.Commands uses Pulsar.Client.Transaction, so a change to Pulsar.Client.Transaction can break Pulsar.Client.Common.Commands, while a change to Pulsar.Client.Common.Commands can't break Pulsar.Client.Transaction.
- Position
- Below the diagonal: Pulsar.Client.Common.Commands uses a module listed above it, which is the healthy direction.
23→13 Pulsar.Client.Common.Commands uses Pulsar.Client.Common✕
- Connections
- 9 pairs of types, where a type in Pulsar.Client.Common.Commands uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.AckTypePulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.AuthDataPulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.MessageIdPulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.MetadataPulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.NamespaceNamePulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.SchemaInfoPulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.SchemaVersionPulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.SubscriptionInitialPositionPulsar.Client.Common.Commands.Commands→Pulsar.Client.Common.SubscriptionType
- Direction
- Pulsar.Client.Common.Commands uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Common.Commands, while a change to Pulsar.Client.Common.Commands can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Common.Commands uses a module listed above it, which is the healthy direction.
23→18 Pulsar.Client.Common.Commands uses Pulsar.Client.Api✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Common.Commands uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Common.Commands.Commands→Pulsar.Client.Api.KeySharedPolicy
- Direction
- Pulsar.Client.Common.Commands uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Common.Commands, while a change to Pulsar.Client.Common.Commands can't break Pulsar.Client.Api.
- Position
- Below the diagonal: Pulsar.Client.Common.Commands uses a module listed above it, which is the healthy direction.
24→13 Pulsar.Client.Crypto uses Pulsar.Client.Common✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Crypto uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Crypto.MessageDecryptor→Pulsar.Client.Common.EncryptedMessagePulsar.Client.Crypto.MessageEncryptor→Pulsar.Client.Common.EncryptedMessage
- Direction
- Pulsar.Client.Crypto uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Crypto, while a change to Pulsar.Client.Crypto can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Crypto uses a module listed above it, which is the healthy direction.
24→18 Pulsar.Client.Crypto uses Pulsar.Client.Api✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Crypto uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Crypto.MessageDecryptor→Pulsar.Client.Api.IMessageDecryptorPulsar.Client.Crypto.MessageEncryptor→Pulsar.Client.Api.IMessageEncryptor
- Direction
- Pulsar.Client.Crypto uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Crypto, while a change to Pulsar.Client.Crypto can't break Pulsar.Client.Api.
- Position
- Below the diagonal: Pulsar.Client.Crypto uses a module listed above it, which is the healthy direction.
25→13 Pulsar.Client.Otel.OTelProducerInterceptor uses Pulsar.Client.Common✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Otel.OTelProducerInterceptor uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Otel.OTelProducerInterceptor.OTelProducerInterceptor`1→Pulsar.Client.Common.MessageBuilder`1Pulsar.Client.Otel.OTelProducerInterceptor.OTelProducerInterceptor`1→Pulsar.Client.Common.MessageId
- Direction
- Pulsar.Client.Otel.OTelProducerInterceptor uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Otel.OTelProducerInterceptor, while a change to Pulsar.Client.Otel.OTelProducerInterceptor can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Otel.OTelProducerInterceptor uses a module listed above it, which is the healthy direction.
25→18 Pulsar.Client.Otel.OTelProducerInterceptor uses Pulsar.Client.Api✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Otel.OTelProducerInterceptor uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Otel.OTelProducerInterceptor.OTelProducerInterceptor`1→Pulsar.Client.Api.IProducerInterceptor`1Pulsar.Client.Otel.OTelProducerInterceptor.OTelProducerInterceptor`1→Pulsar.Client.Api.IProducer`1
- Direction
- Pulsar.Client.Otel.OTelProducerInterceptor uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Otel.OTelProducerInterceptor, while a change to Pulsar.Client.Otel.OTelProducerInterceptor can't break Pulsar.Client.Api.
- Position
- Below the diagonal: Pulsar.Client.Otel.OTelProducerInterceptor uses a module listed above it, which is the healthy direction.
26→13 Pulsar.Client.Otel.OtelConsumerInterceptor uses Pulsar.Client.Common✕
- Connections
- 3 pairs of types, where a type in Pulsar.Client.Otel.OtelConsumerInterceptor uses a type in Pulsar.Client.Common.
- The types involved
Pulsar.Client.Otel.OtelConsumerInterceptor.InterceptorCommand→Pulsar.Client.Common.MessageIdPulsar.Client.Otel.OtelConsumerInterceptor.OTelConsumerInterceptor`1→Pulsar.Client.Common.MessageIdPulsar.Client.Otel.OtelConsumerInterceptor.OTelConsumerInterceptor`1→Pulsar.Client.Common.Message`1
- Direction
- Pulsar.Client.Otel.OtelConsumerInterceptor uses Pulsar.Client.Common, so a change to Pulsar.Client.Common can break Pulsar.Client.Otel.OtelConsumerInterceptor, while a change to Pulsar.Client.Otel.OtelConsumerInterceptor can't break Pulsar.Client.Common.
- Position
- Below the diagonal: Pulsar.Client.Otel.OtelConsumerInterceptor uses a module listed above it, which is the healthy direction.
26→18 Pulsar.Client.Otel.OtelConsumerInterceptor uses Pulsar.Client.Api✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Otel.OtelConsumerInterceptor uses a type in Pulsar.Client.Api.
- The types involved
Pulsar.Client.Otel.OtelConsumerInterceptor.OTelConsumerInterceptor`1→Pulsar.Client.Api.IConsumerInterceptor`1Pulsar.Client.Otel.OtelConsumerInterceptor.OTelConsumerInterceptor`1→Pulsar.Client.Api.IConsumer`1
- Direction
- Pulsar.Client.Otel.OtelConsumerInterceptor uses Pulsar.Client.Api, so a change to Pulsar.Client.Api can break Pulsar.Client.Otel.OtelConsumerInterceptor, while a change to Pulsar.Client.Otel.OtelConsumerInterceptor can't break Pulsar.Client.Api.
- Position
- Below the diagonal: Pulsar.Client.Otel.OtelConsumerInterceptor uses a module listed above it, which is the healthy direction.
27→21 Pulsar.Client.Auth.DefaultImplementation uses Pulsar.Client.Auth✕
- Connections
- 2 pairs of types, where a type in Pulsar.Client.Auth.DefaultImplementation uses a type in Pulsar.Client.Auth.
- The types involved
Pulsar.Client.Auth.DefaultImplementation.DefaultImplementation→Pulsar.Client.Auth.AuthenticationTlsPulsar.Client.Auth.DefaultImplementation.DefaultImplementation→Pulsar.Client.Auth.AuthenticationToken
- Direction
- Pulsar.Client.Auth.DefaultImplementation uses Pulsar.Client.Auth, so a change to Pulsar.Client.Auth can break Pulsar.Client.Auth.DefaultImplementation, while a change to Pulsar.Client.Auth.DefaultImplementation can't break Pulsar.Client.Auth.
- Position
- Below the diagonal: Pulsar.Client.Auth.DefaultImplementation uses a module listed above it, which is the healthy direction.
27→22 Pulsar.Client.Auth.DefaultImplementation uses Pulsar.Client.Auth.OAuth2✕
- Connections
- 1 pair of types, where a type in Pulsar.Client.Auth.DefaultImplementation uses a type in Pulsar.Client.Auth.OAuth2.
- The types involved
Pulsar.Client.Auth.DefaultImplementation.DefaultImplementation→Pulsar.Client.Auth.OAuth2.AuthenticationOauth2
- Direction
- Pulsar.Client.Auth.DefaultImplementation uses Pulsar.Client.Auth.OAuth2, so a change to Pulsar.Client.Auth.OAuth2 can break Pulsar.Client.Auth.DefaultImplementation, while a change to Pulsar.Client.Auth.DefaultImplementation can't break Pulsar.Client.Auth.OAuth2.
- Position
- Below the diagonal: Pulsar.Client.Auth.DefaultImplementation uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A05:2025 — Injection | 6 | High / 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 `!`.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with Pulsar.Client.fsproj (5), REDACTED. | +5.8 pts | Low | Dependency Hygiene |
| Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with RealWorld.cs. | +2.7 pts | Low | Explicit 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 pts | Medium | DR & Backup |
| Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`. | +3.3 pts | Medium | Nullable 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 pts | Medium | Architecture 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 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.5 pts | Medium | Release Hygiene |
| Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. | +1.0 pts | Low | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Pulsar.Client/Internal/ConsumerImpl.fs | 4.8 | Mixed | Cognitive Complexity: ConsumerImpl`1.ReceiveIndividualMessagesFromBatch (cognitive 23) |
| src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs | 5.1 | Mixed | God Classes: FileTooLong: Internal/MultiTopicsConsumerImpl.fs |
| src/Pulsar.Client/Internal/ProducerImpl.fs | 6.3 | Mixed | God Classes: FileTooLong: Internal/ProducerImpl.fs |
| REDACTED | 6.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Pulsar.Client/Internal/ClientCnx.fs | 7.0 | Mixed | God Classes: FileTooLong: Internal/ClientCnx.fs |
| src/Pulsar.Client/Api/ConsumerBuilder.fs | 7.0 | Mixed | God Classes: TooManyMethods: ConsumerBuilder`1 |
| src/Pulsar.Client/Internal/BinaryLookupService.fs | 7.2 | Mixed | Code Duplication: Duplicated block (18 lines × 2) |
| src/Pulsar.Client.Proto/DynamicJsonConverter.cs | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/Pulsar.Client/Internal/ConsumerStatsImpl.fs | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs | 7.4 | Mixed | Code Duplication: Edited copy of a member (97 corresponding lines) |
| src/Pulsar.Client/Internal/PartitionedProducerImpl.fs | 7.4 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| examples/CsharpExamples/RealWorld.cs | 7.6 | Mixed | Explicit Debt: FileScopedPragmaDisable |
| src/Pulsar.Client/Common/MessageId.fs | 7.8 | Mixed | Cyclomatic Complexity: MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cyclomatic 16) |
| src/Pulsar.Client.Proto/MurmurHash3.cs | 7.8 | Mixed | Code Duplication: Edited copy of a member (71 corresponding lines) |
| src/Pulsar.Client/Api/PulsarClient.fs | 7.8 | Mixed | Code Duplication: Duplicated block (11–12 lines × 2) |
| src/Pulsar.Client/Common/Commands.fs | 7.8 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs | 7.8 | Mixed | Code Duplication: Duplicated block (10 lines × 3) |
| src/Pulsar.Client/Internal/Compression.fs | 7.8 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 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.
What we checked — 41 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 96 of 128 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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 Complexity
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.
What to do
- 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.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo at 33.
What to do
- 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.
D3 · God Classes
8 god class(es) detected.
What to do
- 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).
- 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).
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with Tools.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
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.
What to do
- 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).
- 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).
- 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).
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 58 classes have LCOM4 above 3.
What to do
- 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).
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).
D12 · Dependency Hygiene
25 outdated, 0 vulnerable, 0 deprecated, 1 prerelease packages.
What to do
- 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).
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
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.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
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).
What to do
- Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with RealWorld.cs. — One of this dimension's main actionable groups (1 issue-level).
- 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).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 2 unit(s).
D26 · Project Cohesion
1 of 4 projects flagged as possibly oversized/incoherent.
What to do
- 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).
D27 · Navigability
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.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
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.
What to do
- 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).
- 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).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
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.
D35 · Change Coupling
Strongest change-coupling: ConsumerBuilder.fs↔ConsumerImpl.fs 76%; IProducer.fs↔ConsumerImpl.fs 70%; ProducerImpl.fs↔TransactionMetaStoreHandler.fs 69%
What to do
- 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).
- 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).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- 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)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED: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 & Rollback
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 & Backup
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 Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `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 types
- 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
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 43% | Weak — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 78% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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)
Critical — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileScopedPragmaDisable examples/CsharpExamples/RealWorld.cs:8
- REDACTED
Serious — 78 finding(s)
- FileTooLong: Internal/ConsumerImpl.fs src/Pulsar.Client/Internal/ConsumerImpl.fs
- FileTooLong: Internal/MultiTopicsConsumerImpl.fs src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs
- FileTooLong: Internal/ProducerImpl.fs src/Pulsar.Client/Internal/ProducerImpl.fs
- FileTooLong: Internal/ClientCnx.fs src/Pulsar.Client/Internal/ClientCnx.fs
- Change coupling: ConsumerBuilder.fs ↔ ConsumerImpl.fs src/Pulsar.Client/Api/ConsumerBuilder.fs:1
- Change coupling: ConsumerImpl.fs ↔ PartitionedProducerImpl.fs src/Pulsar.Client/Internal/ConsumerImpl.fs:1
- Change coupling: MultiTopicsConsumerImpl.fs ↔ ReaderImpl.fs src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:1
- Change coupling: MultiTopicsConsumerImpl.fs ↔ PartitionedProducerImpl.fs src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:1
- Unfinished stub — raises a "not implemented" error src/Pulsar.Client/Schema/AutoConsumeSchema.fs:9
- Unfinished stub — raises a "not implemented" error src/Pulsar.Client/Schema/AutoConsumeSchema.fs:10
- Unfinished stub — raises a "not implemented" error src/Pulsar.Client/Schema/AutoProduceBytesSchema.fs:9
- Unfinished stub — raises a "not implemented" error src/Pulsar.Client/Schema/AutoProduceBytesSchema.fs:10
- TooManyMethods: ConsumerImpl`1 src/Pulsar.Client/Internal/ConsumerImpl.fs:68
- TooManyMethods: MultiTopicsConsumerImpl`1 src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:90
- TooManyMethods: ConsumerBuilder`1 src/Pulsar.Client/Api/ConsumerBuilder.fs:10
- Change-coupling hub: IProducer.fs → IConsumer.fs, ConsumerImpl.fs, MultiTopicsConsumerImpl.fs src/Pulsar.Client/Api/IProducer.fs
- Change-coupling hub: ProducerImpl.fs → ProducerBuilder.fs, ReaderImpl.fs, TransactionMetaStoreHandler.fs src/Pulsar.Client/Internal/ProducerImpl.fs
- Change-coupling hub: ClientCnx.fs → ConnectionHandler.fs, ConsumerImpl.fs, ProducerImpl.fs, TransactionMetaStoreHandler.fs src/Pulsar.Client/Internal/ClientCnx.fs
- Duplicated block (10 lines × 2) src/Pulsar.Client/Common/Commands.fs:42
- Duplicated block (10 lines × 2) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:39
- Duplicated block (10 lines × 2) src/Pulsar.Client/Common/Commands.fs:27
- Duplicated block (8 lines × 2) src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:227
- Duplicated block (8 lines × 2) src/Pulsar.Client/Internal/Compression.fs:67
- Duplicated block (8 lines × 2) src/Pulsar.Client/Internal/Compression.fs:58
- Duplicated block (7 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:121
- Duplicated block (7 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:1578
- Duplicated block (7 lines × 2) src/Pulsar.Client/Internal/ProducerImpl.fs:1208
- Duplicated block (6 lines × 2) src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:40
- Duplicated block (6 lines × 2) src/Pulsar.Client/Internal/NegativeAcksTracker.fs:78
- Duplicated block (6 lines × 2) src/Pulsar.Client/Api/PulsarClient.fs:337
- TodoComment src/Pulsar.Client.Proto/DynamicJsonConverter.cs:47
- TodoComment src/Pulsar.Client.Proto/DynamicJsonConverter.cs:51
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:89
- Duplicated block (14 lines × 2) examples/FsharpExamples/RealWorld.fs:50
- Duplicated block (11 lines × 2) src/Pulsar.Client/Internal/BinaryLookupService.fs:65
- Duplicated block (11 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:255
- Duplicated block (9 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:1319
- Duplicated block (9 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:1625
- Duplicated block (10 lines × 3) src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:321
- Duplicated block (10 lines × 3) examples/CsharpExamples/Oauth2.cs:51
- MessageId.System.IComparable<Pulsar.Client.Common.MessageId>.CompareTo (cyclomatic 16) src/Pulsar.Client/Common/MessageId.fs:140
- Prerelease dependency: Expecto.FsCheck
- CommentedOutCode examples/CsharpExamples/Program.cs:21
- 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
- TooManyFunctions: Tools src/Pulsar.Client/Common/Tools.fs:2
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:1
- Edited copy of a member (97 corresponding lines) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:1
- Edited copy of a member (71 corresponding lines) src/Pulsar.Client.Proto/MurmurHash3.cs:42
- Edited copies of one member (7 members, 15+ corresponding lines) src/Pulsar.Client/Schema/BooleanSchema.fs:1
- Edited copies of one member (3 members, 17+ corresponding lines) src/Pulsar.Client/Schema/DateSchema.fs:1
- Edited copy of a member (10 corresponding lines) src/Pulsar.Client/Schema/AutoConsumeSchema.fs:1
- Duplicated block (70 lines × 2) src/Pulsar.Client/Internal/ConsumerImpl.fs:853
- Duplicated block (46–47 lines × 2) src/Pulsar.Client.Proto/MurmurHash3.cs:53
- Duplicated block (41 lines × 2) src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs:57
- Duplicated block (18 lines × 2) src/Pulsar.Client/Internal/BinaryLookupService.fs:31
- Duplicated block (9–14 lines × 2) src/Pulsar.Client/Internal/BinaryLookupService.fs:156
- Duplicated block (11–12 lines × 2) src/Pulsar.Client/Api/PulsarClient.fs:347
- Duplicated block (12 lines × 2) src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs:768
- Duplicated block (20 lines × 2) src/Pulsar.Client/Internal/PartitionedProducerImpl.fs:461
- Duplicated block (6–7 lines × 2) src/Pulsar.Client/Internal/BinaryLookupService.fs:182
- Duplicated block (6 lines × 3) src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:38
- Duplicated block (4–6 lines × 3) src/Pulsar.Client/Internal/HttpLookupService.fs:103
- Duplicated block (9 lines × 3) src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs:334
- Edited copy of a member (42 corresponding lines) examples/FsharpExamples/Simple.fs:1
- Edited copy of a member (30 corresponding lines) examples/CsharpExamples/Oauth2.cs:29
- Duplicated block (17–18 lines × 2) examples/FsharpExamples/Oauth2.fs:42
- Duplicated block (15 lines × 2) examples/CsharpExamples/CustomProps.cs:14
- Duplicated block (16 lines × 2) examples/CsharpExamples/Simple.cs:18
- Duplicated block (13 lines × 3) examples/FsharpExamples/Oauth2.fs:38
- Low cohesion: ZeroQueueConsumerImpl`1 (LCOM4 5) src/Pulsar.Client/Internal/ConsumerImpl.fs:2101
- Sync-over-async blocking src/Pulsar.Client/Internal/TableViewImpl.fs:45
- NuGet dependencies are not locked
Minor — 25 finding(s)
- Outdated: Microsoft.Extensions.Caching.Memory src/Pulsar.Client/Pulsar.Client.fsproj:58
- Outdated: Microsoft.Extensions.Logging src/Pulsar.Client/Pulsar.Client.fsproj:59
- Outdated: Microsoft.Extensions.Logging.Abstractions src/Pulsar.Client/Pulsar.Client.fsproj:60
- Outdated: NSec.Cryptography src/Pulsar.Client/Pulsar.Client.fsproj:54
- Outdated: System.IO.Pipelines src/Pulsar.Client/Pulsar.Client.fsproj:61
- Outdated: System.Threading.Channels REDACTED:38
- Orphaned file src/Pulsar.Client/Internal/ConsumerStatsImpl.fs:1
- Orphaned file src/Pulsar.Client/Internal/ProducerStatsImpl.fs:1
- Orphaned file src/Pulsar.Client.Otel/OtelConsumerInterceptor.fs:1
- Orphaned file src/Pulsar.Client/Common/ServiceUri.fs:1
- Duplicated predicate src/Pulsar.Client/Internal/ConsumerImpl.fs:807
- Duplicated predicate src/Pulsar.Client/Internal/ConsumerImpl.fs:531
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion src/Pulsar.Client.Proto/Pulsar.Client.Proto.csproj:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:3
- No dependency-update automation examples/CsharpExamples/CsharpExamples.csproj:9
- No changelog
- Nullable reference types not enabled everywhere
Minor — 19 finding(s)
- Outdated: Microsoft.Extensions.Logging.Console
- Outdated: OpenTelemetry
- Outdated: OpenTelemetry.Exporter.Console
- Outdated: Pulsar.Client
- Outdated: FSharp.Core
- Outdated: Expecto.FsCheck
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: Serilog
- Outdated: Microsoft.Extensions.DependencyInjection
- Outdated: Apache.Avro
- Outdated: AvroSchemaGenerator
- Outdated: K4os.Compression.LZ4
- Outdated: Microsoft.IO.RecyclableMemoryStream
- Outdated: Pipelines.Sockets.Unofficial
- Outdated: protobuf-net
- Outdated: protobuf-net.Reflection
- Outdated: zlib.net-mutliplatform
- Outdated: ZstdNet
- Outdated: OpenTelemetry.Api
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4ed4ecdcbb142acbc5e7fcd5e591dee/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4ed4ecdcbb142acbc5e7fcd5e591dee/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Pulsar.Client.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-1fcc842443c14ec9b113e09e39696b9d | 0 | artifacts/raw/osv-scanner.json |