Executive summary
grpc/grpc-rust falls short of our standard for a preview release because its Security dimensions are rated Critical, and eight passwords or keys sit in the current code. It scores 66 out of 100, which alone would earn Strong, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 53, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 10 points. Recording design decisions comes next, worth about 3 points. Raising Production Readiness to 62 would lift the score to about 69.
Seventy-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen passwords or keys in the code's history and eight in the code are open to anyone who can read the repository, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 98,374 lines, about €140,000 to rebuild.
If Production Readiness rose from 53 to 62, the lowest score rated Strong, the score would rise from 66 to about 69.
New since the last survey: 19 findings
- Cognitive Complexity · TransportContext::run (cognitive 19) xds-client/src/client/worker.rs
- Code Duplication · Duplicated block (9 lines × 2) grpc-rustls/src/server/mod.rs
- Code Duplication · Duplicated block (12 lines × 2) grpc-rustls/src/client/mod.rs
- Code Duplication · Duplicated block (6 lines × 2) grpc-xds/src/resource/string_matcher.rs
- Cohesion (LCOM4) · Low cohesion: TlsStream (LCOM4 7) grpc-rustls/src/tls_stream.rs
- Churn × Complexity Hotspots · Repeated repair: tonic-xds/src/xds/resource/route_config.rs tonic-xds/src/xds/resource/route_config.rs
- Explicit Debt · TodoComment tonic-xds/src/client/loadbalance/cluster_factory.rs
- Explicit Debt · TodoComment grpc-xds/src/routing/mod.rs
- Explicit Debt · TodoComment grpc-xds/src/routing/virtual_host.rs
- Explicit Debt · TodoComment grpc-xds/src/routing/route.rs
- Explicit Debt · TodoComment grpc-xds/src/resource/route.rs
- Explicit Debt · TodoComment grpc-xds/src/load_balancing/cluster_manager.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 23 findings
- Cyclomatic Complexity · AdsWorker::add_watcher (cyclomatic 16) xds-client/src/client/worker.rs
- Cognitive Complexity · AdsWorker::add_watcher (cognitive 40) xds-client/src/client/worker.rs
- Cognitive Complexity · AdsWorker::run (cognitive 25) xds-client/src/client/worker.rs
- Cognitive Complexity · AdsWorker::run_connected (cognitive 22) xds-client/src/client/worker.rs
- Code Duplication · Duplicated block (10 lines × 2) xds-client/src/client/worker.rs
- Code Duplication · Duplicated block (10 lines × 2) xds-client/src/client/worker.rs
- Code Duplication · Duplicated block (9 lines × 2) grpc/src/credentials/rustls/server/mod.rs
- Code Duplication · Duplicated block (7 lines × 2) grpc/src/client/load_balancing/mod.rs
- Code Duplication · Duplicated block (12 lines × 2) grpc/src/credentials/rustls/client/mod.rs
- Cohesion (LCOM4) · Low cohesion: TlsStream (LCOM4 7) grpc/src/credentials/rustls/tls_stream.rs
- Churn × Complexity Hotspots · Hotspot: xds-client/src/client/worker.rs xds-client/src/client/worker.rs
- Churn × Complexity Hotspots · Hotspot: interop/src/bin/client.rs interop/src/bin/client.rs
- Explicit Debt · TodoComment grpc-xds/src/resource/route.rs
- Explicit Debt · TodoComment grpc-xds/src/resource/route.rs
- Explicit Debt · TodoComment grpc/src/client/channel.rs
- Static Analysis (SAST) · High: REDACTED .github/workflows/release-protoc-gen-rust-grpc.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/release-protoc-gen-rust-grpc.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/release-protoc-gen-rust-grpc.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/release-protoc-gen-rust-grpc.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/release-protoc-gen-rust-grpc.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/release-protoc-gen-rust-grpc.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/release-protoc-gen-rust-grpc.yml
- Documentation (README) · README may be stale
Rebuild cost: about €140,000 · Estimate
| Cost to rebuild | €45,000 to €230,000, for 750 to 2,381 hours of work, about 0.9 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 98,374 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 grpc.attributes | 2 grpc.client.call_options | 3 grpc.client.load_balancing.subchannel.private | 4 grpc.credentials.common | 5 grpc.private | 6 grpc.server.service | 7 grpc_xds.resource.endpoint | 8 tonic.codec.compression | 9 tonic.server | 10 grpc.client.name_resolution | 11 grpc.metadata.value | 12 tonic_xds.xds.cache | 13 grpc.metadata.map | 14 grpc.rt | 15 grpc.credentials.client | 16 tonic.request | 17 tonic.status | 18 grpc.credentials | 19 tonic.client.grpc | 20 tonic.transport.error | 21 tonic_types.richer_error | 22 tonic_xds.client.retry | 23 grpc.core | 24 tonic_types.generated.google_rpc | 25 xds_client.client.config | 26 grpc.client | 27 grpc.client.transport | 28 grpc.client.load_balancing | 29 grpc.client.subchannel | 30 grpc.client.transport.tonic | 31 grpc.server | 32 grpc.client.channel | 33 grpc.client.load_balancing.child_manager | 34 grpc.client.load_balancing.pick_first | 35 grpc.inmemory | 36 grpc.server.interceptor | 37 tonic.transport.server | 38 grpc.client.load_balancing.priority | 39 xds_client.transport.tonic | 40 grpc_protobuf.client |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 grpc.attributes | ||||||||||||||||||||||||||||||||||||||||
| 2 grpc.client.call_options | ||||||||||||||||||||||||||||||||||||||||
| 3 grpc.client.load_balancing.subchannel.private | ||||||||||||||||||||||||||||||||||||||||
| 4 grpc.credentials.common | ||||||||||||||||||||||||||||||||||||||||
| 5 grpc.private | ||||||||||||||||||||||||||||||||||||||||
| 6 grpc.server.service | ||||||||||||||||||||||||||||||||||||||||
| 7 grpc_xds.resource.endpoint | ||||||||||||||||||||||||||||||||||||||||
| 8 tonic.codec.compression | ||||||||||||||||||||||||||||||||||||||||
| 9 tonic.server | ||||||||||||||||||||||||||||||||||||||||
| 10 grpc.client.name_resolution | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 11 grpc.metadata.value | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 tonic_xds.xds.cache | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 grpc.metadata.map | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 14 grpc.rt | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 15 grpc.credentials.client | 1 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 16 tonic.request | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 tonic.status | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 18 grpc.credentials | 1 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 19 tonic.client.grpc | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 tonic.transport.error | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 tonic_types.richer_error | 2 | 1 | 3 | 20 | ||||||||||||||||||||||||||||||||||||
| 22 tonic_xds.client.retry | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 grpc.core | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 tonic_types.generated.google_rpc | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 xds_client.client.config | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 grpc.client | 3 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 grpc.client.transport | 1 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 28 grpc.client.load_balancing | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 29 grpc.client.subchannel | 1 | 1 | 2 | 3 | 3 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 30 grpc.client.transport.tonic | 1 | 2 | 3 | 1 | 3 | 6 | 3 | |||||||||||||||||||||||||||||||||
| 31 grpc.server | 3 | 1 | 3 | 3 | 2 | 1 | 10 | 1 | ||||||||||||||||||||||||||||||||
| 32 grpc.client.channel | 1 | 1 | 2 | 4 | 1 | 5 | 3 | 5 | ||||||||||||||||||||||||||||||||
| 33 grpc.client.load_balancing.child_manager | 2 | 1 | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||
| 34 grpc.client.load_balancing.pick_first | 2 | 2 | 1 | 1 | 11 | |||||||||||||||||||||||||||||||||||
| 35 grpc.inmemory | 1 | 1 | 3 | 4 | 2 | 3 | 2 | 4 | 2 | |||||||||||||||||||||||||||||||
| 36 grpc.server.interceptor | 5 | 7 | 3 | |||||||||||||||||||||||||||||||||||||
| 37 tonic.transport.server | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 grpc.client.load_balancing.priority | 3 | 4 | 1 | 7 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 39 xds_client.transport.tonic | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 grpc_protobuf.client | 1 | 1 | 1 | 1 | 1 |
10→1 grpc.client.name_resolution uses grpc.attributes✕
- Connections
- 2 pairs of types, where a type in grpc.client.name_resolution uses a type in grpc.attributes.
- The types involved
grpc.client.name_resolution.Endpoint→grpc.attributes.Attributesgrpc.client.name_resolution.ResolverUpdate→grpc.attributes.Attributes
- Direction
- grpc.client.name_resolution uses grpc.attributes, so a change to grpc.attributes can break grpc.client.name_resolution, while a change to grpc.client.name_resolution can't break grpc.attributes.
- Position
- Below the diagonal: grpc.client.name_resolution uses a module listed above it, which is the healthy direction.
10→14 grpc.client.name_resolution uses grpc.rt part of a loop✕
- Connections
- 1 pair of types, where a type in grpc.client.name_resolution uses a type in grpc.rt.
- The types involved
grpc.client.name_resolution.ResolverOptions→grpc.rt.GrpcRuntime
- Direction
- grpc.client.name_resolution uses grpc.rt, so a change to grpc.rt can break grpc.client.name_resolution, while a change to grpc.client.name_resolution can't break grpc.rt.
- 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→23 grpc.client.name_resolution uses grpc.core part of a loop✕
- Connections
- 2 pairs of types, where a type in grpc.client.name_resolution uses a type in grpc.core.
- The types involved
grpc.client.name_resolution.Endpoint→grpc.core.Addressgrpc.client.name_resolution.NopResolver→grpc.core.Address
- Direction
- grpc.client.name_resolution uses grpc.core, so a change to grpc.core can break grpc.client.name_resolution, while a change to grpc.client.name_resolution can't break grpc.core.
- 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→20 grpc.metadata.value uses tonic.transport.error part of a loop✕
- Connections
- 1 pair of types, where a type in grpc.metadata.value uses a type in tonic.transport.error.
- The types involved
grpc.metadata.value.ToStrError→tonic.transport.error.Error
- Direction
- grpc.metadata.value uses tonic.transport.error, so a change to tonic.transport.error can break grpc.metadata.value, while a change to grpc.metadata.value can't break tonic.transport.error.
- 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→7 tonic_xds.xds.cache uses grpc_xds.resource.endpoint✕
- Connections
- 1 pair of types, where a type in tonic_xds.xds.cache uses a type in grpc_xds.resource.endpoint.
- The types involved
tonic_xds.xds.cache.XdsCache→grpc_xds.resource.endpoint.EndpointsResource
- Direction
- tonic_xds.xds.cache uses grpc_xds.resource.endpoint, so a change to grpc_xds.resource.endpoint can break tonic_xds.xds.cache, while a change to tonic_xds.xds.cache can't break grpc_xds.resource.endpoint.
- Position
- Below the diagonal: tonic_xds.xds.cache uses a module listed above it, which is the healthy direction.
13→5 grpc.metadata.map uses grpc.private✕
- Connections
- 3 pairs of types, where a type in grpc.metadata.map uses a type in grpc.private.
- The types involved
grpc.metadata.map.AsEncodingAgnosticMetadataKey→grpc.private.Internalgrpc.metadata.map.AsMetadataKey→grpc.private.Internalgrpc.metadata.map.IntoMetadataKey→grpc.private.Internal
- Direction
- grpc.metadata.map uses grpc.private, so a change to grpc.private can break grpc.metadata.map, while a change to grpc.metadata.map can't break grpc.private.
- Position
- Below the diagonal: grpc.metadata.map uses a module listed above it, which is the healthy direction.
13→11 grpc.metadata.map uses grpc.metadata.value✕
- Connections
- 3 pairs of types, where a type in grpc.metadata.map uses a type in grpc.metadata.value.
- The types involved
grpc.metadata.map.AsMetadataKey→grpc.metadata.value.MetadataValuegrpc.metadata.map.IntoMetadataKey→grpc.metadata.value.MetadataValuegrpc.metadata.map.MetadataMap→grpc.metadata.value.MetadataValue
- Direction
- grpc.metadata.map uses grpc.metadata.value, so a change to grpc.metadata.value can break grpc.metadata.map, while a change to grpc.metadata.map can't break grpc.metadata.value.
- Position
- Below the diagonal: grpc.metadata.map uses a module listed above it, which is the healthy direction.
14→5 grpc.rt uses grpc.private✕
- Connections
- 2 pairs of types, where a type in grpc.rt uses a type in grpc.private.
- The types involved
grpc.rt.GrpcEndpoint→grpc.private.Internalgrpc.rt.StreamEndpoint→grpc.private.Internal
- Direction
- grpc.rt uses grpc.private, so a change to grpc.private can break grpc.rt, while a change to grpc.rt can't break grpc.private.
- Position
- Below the diagonal: grpc.rt uses a module listed above it, which is the healthy direction.
14→10 grpc.rt uses grpc.client.name_resolution✕
- Connections
- 3 pairs of types, where a type in grpc.rt uses a type in grpc.client.name_resolution.
- The types involved
grpc.rt.GrpcRuntime→grpc.client.name_resolution.ResolverOptionsgrpc.rt.NoOpRuntime→grpc.client.name_resolution.ResolverOptionsgrpc.rt.Runtime→grpc.client.name_resolution.ResolverOptions
- Direction
- grpc.rt uses grpc.client.name_resolution, so a change to grpc.client.name_resolution can break grpc.rt, while a change to grpc.rt can't break grpc.client.name_resolution.
- Position
- Below the diagonal: grpc.rt uses a module listed above it, which is the healthy direction.
15→1 grpc.credentials.client uses grpc.attributes✕
- Connections
- 1 pair of types, where a type in grpc.credentials.client uses a type in grpc.attributes.
- The types involved
grpc.credentials.client.ClientHandshakeInfo→grpc.attributes.Attributes
- Direction
- grpc.credentials.client uses grpc.attributes, so a change to grpc.attributes can break grpc.credentials.client, while a change to grpc.credentials.client can't break grpc.attributes.
- Position
- Below the diagonal: grpc.credentials.client uses a module listed above it, which is the healthy direction.
15→4 grpc.credentials.client uses grpc.credentials.common✕
- Connections
- 2 pairs of types, where a type in grpc.credentials.client uses a type in grpc.credentials.common.
- The types involved
grpc.credentials.client.CompositeChannelCredentials→grpc.credentials.common.Authoritygrpc.credentials.client.ValidateAuthority→grpc.credentials.common.Authority
- Direction
- grpc.credentials.client uses grpc.credentials.common, so a change to grpc.credentials.common can break grpc.credentials.client, while a change to grpc.credentials.client can't break grpc.credentials.common.
- Position
- Below the diagonal: grpc.credentials.client uses a module listed above it, which is the healthy direction.
15→5 grpc.credentials.client uses grpc.private✕
- Connections
- 1 pair of types, where a type in grpc.credentials.client uses a type in grpc.private.
- The types involved
grpc.credentials.client.CompositeChannelCredentials→grpc.private.Internal
- Direction
- grpc.credentials.client uses grpc.private, so a change to grpc.private can break grpc.credentials.client, while a change to grpc.credentials.client can't break grpc.private.
- Position
- Below the diagonal: grpc.credentials.client uses a module listed above it, which is the healthy direction.
15→14 grpc.credentials.client uses grpc.rt✕
- Connections
- 1 pair of types, where a type in grpc.credentials.client uses a type in grpc.rt.
- The types involved
grpc.credentials.client.CompositeChannelCredentials→grpc.rt.GrpcRuntime
- Direction
- grpc.credentials.client uses grpc.rt, so a change to grpc.rt can break grpc.credentials.client, while a change to grpc.credentials.client can't break grpc.rt.
- Position
- Below the diagonal: grpc.credentials.client uses a module listed above it, which is the healthy direction.
15→18 grpc.credentials.client uses grpc.credentials part of a loop✕
- Connections
- 3 pairs of types, where a type in grpc.credentials.client uses a type in grpc.credentials.
- The types involved
grpc.credentials.client.CompositeChannelCredentials→grpc.credentials.ChannelCredentialsgrpc.credentials.client.CompositeChannelCredentials→grpc.credentials.ProtocolInfogrpc.credentials.client.HandshakeOutput→grpc.credentials.SecurityInfo
- Direction
- grpc.credentials.client uses grpc.credentials, so a change to grpc.credentials can break grpc.credentials.client, while a change to grpc.credentials.client can't break grpc.credentials.
- 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.
16→3 tonic.request uses grpc.client.load_balancing.subchannel.private✕
- Connections
- 2 pairs of types, where a type in tonic.request uses a type in grpc.client.load_balancing.subchannel.private.
- The types involved
tonic.request.IntoRequest→grpc.client.load_balancing.subchannel.private.Sealedtonic.request.IntoStreamingRequest→grpc.client.load_balancing.subchannel.private.Sealed
- Direction
- tonic.request uses grpc.client.load_balancing.subchannel.private, so a change to grpc.client.load_balancing.subchannel.private can break tonic.request, while a change to tonic.request can't break grpc.client.load_balancing.subchannel.private.
- Position
- Below the diagonal: tonic.request uses a module listed above it, which is the healthy direction.
16→13 tonic.request uses grpc.metadata.map✕
- Connections
- 1 pair of types, where a type in tonic.request uses a type in grpc.metadata.map.
- The types involved
tonic.request.Request→grpc.metadata.map.MetadataMap
- Direction
- tonic.request uses grpc.metadata.map, so a change to grpc.metadata.map can break tonic.request, while a change to tonic.request can't break grpc.metadata.map.
- Position
- Below the diagonal: tonic.request uses a module listed above it, which is the healthy direction.
17→13 tonic.status uses grpc.metadata.map✕
- Connections
- 2 pairs of types, where a type in tonic.status uses a type in grpc.metadata.map.
- The types involved
tonic.status.Status→grpc.metadata.map.MetadataMaptonic.status.StatusInner→grpc.metadata.map.MetadataMap
- Direction
- tonic.status uses grpc.metadata.map, so a change to grpc.metadata.map can break tonic.status, while a change to tonic.status can't break grpc.metadata.map.
- Position
- Below the diagonal: tonic.status uses a module listed above it, which is the healthy direction.
17→20 tonic.status uses tonic.transport.error part of a loop✕
- Connections
- 4 pairs of types, where a type in tonic.status uses a type in tonic.transport.error.
- The types involved
tonic.status.ConnectError→tonic.transport.error.Errortonic.status.Status→tonic.transport.error.Errortonic.status.TimeoutExpired→tonic.transport.error.Errortonic.status.status$module→tonic.transport.error.Error
- Direction
- tonic.status uses tonic.transport.error, so a change to tonic.transport.error can break tonic.status, while a change to tonic.status can't break tonic.transport.error.
- 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.
18→1 grpc.credentials uses grpc.attributes✕
- Connections
- 1 pair of types, where a type in grpc.credentials uses a type in grpc.attributes.
- The types involved
grpc.credentials.SecurityInfo→grpc.attributes.Attributes
- Direction
- grpc.credentials uses grpc.attributes, so a change to grpc.attributes can break grpc.credentials, while a change to grpc.credentials can't break grpc.attributes.
- Position
- Below the diagonal: grpc.credentials uses a module listed above it, which is the healthy direction.
18→4 grpc.credentials uses grpc.credentials.common✕
- Connections
- 1 pair of types, where a type in grpc.credentials uses a type in grpc.credentials.common.
- The types involved
grpc.credentials.ChannelCredentials→grpc.credentials.common.Authority
- Direction
- grpc.credentials uses grpc.credentials.common, so a change to grpc.credentials.common can break grpc.credentials, while a change to grpc.credentials can't break grpc.credentials.common.
- Position
- Below the diagonal: grpc.credentials uses a module listed above it, which is the healthy direction.
18→5 grpc.credentials uses grpc.private✕
- Connections
- 2 pairs of types, where a type in grpc.credentials uses a type in grpc.private.
- The types involved
grpc.credentials.ChannelCredentials→grpc.private.Internalgrpc.credentials.ServerCredentials→grpc.private.Internal
- Direction
- grpc.credentials uses grpc.private, so a change to grpc.private can break grpc.credentials, while a change to grpc.credentials can't break grpc.private.
- Position
- Below the diagonal: grpc.credentials uses a module listed above it, which is the healthy direction.
18→14 grpc.credentials uses grpc.rt✕
- Connections
- 2 pairs of types, where a type in grpc.credentials uses a type in grpc.rt.
- The types involved
grpc.credentials.ChannelCredentials→grpc.rt.GrpcRuntimegrpc.credentials.ServerCredentials→grpc.rt.GrpcRuntime
- Direction
- grpc.credentials uses grpc.rt, so a change to grpc.rt can break grpc.credentials, while a change to grpc.credentials can't break grpc.rt.
- Position
- Below the diagonal: grpc.credentials uses a module listed above it, which is the healthy direction.
18→15 grpc.credentials uses grpc.credentials.client✕
- Connections
- 1 pair of types, where a type in grpc.credentials uses a type in grpc.credentials.client.
- The types involved
grpc.credentials.ChannelCredentials→grpc.credentials.client.ClientHandshakeInfo
- Direction
- grpc.credentials uses grpc.credentials.client, so a change to grpc.credentials.client can break grpc.credentials, while a change to grpc.credentials can't break grpc.credentials.client.
- Position
- Below the diagonal: grpc.credentials uses a module listed above it, which is the healthy direction.
19→8 tonic.client.grpc uses tonic.codec.compression✕
- Connections
- 3 pairs of types, where a type in tonic.client.grpc uses a type in tonic.codec.compression.
- The types involved
tonic.client.grpc.Grpc→tonic.codec.compression.CompressionEncodingtonic.client.grpc.GrpcConfig→tonic.codec.compression.CompressionEncodingtonic.client.grpc.GrpcConfig→tonic.codec.compression.EnabledCompressionEncodings
- Direction
- tonic.client.grpc uses tonic.codec.compression, so a change to tonic.codec.compression can break tonic.client.grpc, while a change to tonic.client.grpc can't break tonic.codec.compression.
- Position
- Below the diagonal: tonic.client.grpc uses a module listed above it, which is the healthy direction.
19→16 tonic.client.grpc uses tonic.request✕
- Connections
- 2 pairs of types, where a type in tonic.client.grpc uses a type in tonic.request.
- The types involved
tonic.client.grpc.Grpc→tonic.request.Requesttonic.client.grpc.GrpcConfig→tonic.request.Request
- Direction
- tonic.client.grpc uses tonic.request, so a change to tonic.request can break tonic.client.grpc, while a change to tonic.client.grpc can't break tonic.request.
- Position
- Below the diagonal: tonic.client.grpc uses a module listed above it, which is the healthy direction.
20→17 tonic.transport.error uses tonic.status✕
- Connections
- 1 pair of types, where a type in tonic.transport.error uses a type in tonic.status.
- The types involved
tonic.transport.error.Error→tonic.status.Status
- Direction
- tonic.transport.error uses tonic.status, so a change to tonic.status can break tonic.transport.error, while a change to tonic.transport.error can't break tonic.status.
- Position
- Below the diagonal: tonic.transport.error uses a module listed above it, which is the healthy direction.
21→3 tonic_types.richer_error uses grpc.client.load_balancing.subchannel.private✕
- Connections
- 2 pairs of types, where a type in tonic_types.richer_error uses a type in grpc.client.load_balancing.subchannel.private.
- The types involved
tonic_types.richer_error.RpcStatusExt→grpc.client.load_balancing.subchannel.private.Sealedtonic_types.richer_error.StatusExt→grpc.client.load_balancing.subchannel.private.Sealed
- Direction
- tonic_types.richer_error uses grpc.client.load_balancing.subchannel.private, so a change to grpc.client.load_balancing.subchannel.private can break tonic_types.richer_error, while a change to tonic_types.richer_error can't break grpc.client.load_balancing.subchannel.private.
- Position
- Below the diagonal: tonic_types.richer_error uses a module listed above it, which is the healthy direction.
21→13 tonic_types.richer_error uses grpc.metadata.map✕
- Connections
- 1 pair of types, where a type in tonic_types.richer_error uses a type in grpc.metadata.map.
- The types involved
tonic_types.richer_error.StatusExt→grpc.metadata.map.MetadataMap
- Direction
- tonic_types.richer_error uses grpc.metadata.map, so a change to grpc.metadata.map can break tonic_types.richer_error, while a change to tonic_types.richer_error can't break grpc.metadata.map.
- Position
- Below the diagonal: tonic_types.richer_error uses a module listed above it, which is the healthy direction.
21→17 tonic_types.richer_error uses tonic.status✕
- Connections
- 3 pairs of types, where a type in tonic_types.richer_error uses a type in tonic.status.
- The types involved
tonic_types.richer_error.StatusExt→tonic.status.Codetonic_types.richer_error.StatusExt→tonic.status.Statustonic_types.richer_error.richer_error$module→tonic.status.Code
- Direction
- tonic_types.richer_error uses tonic.status, so a change to tonic.status can break tonic_types.richer_error, while a change to tonic_types.richer_error can't break tonic.status.
- Position
- Below the diagonal: tonic_types.richer_error uses a module listed above it, which is the healthy direction.
21→24 tonic_types.richer_error uses tonic_types.generated.google_rpc part of a loop✕
- Connections
- 20 pairs of types, where a type in tonic_types.richer_error uses a type in tonic_types.generated.google_rpc.
- The types involved
tonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.BadRequesttonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.DebugInfotonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.ErrorInfotonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.Helptonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.LocalizedMessagetonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.PreconditionFailuretonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.QuotaFailuretonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.RequestInfotonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.ResourceInfotonic_types.richer_error.RpcStatusExt→tonic_types.generated.google_rpc.RetryInfotonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.BadRequesttonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.DebugInfotonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.ErrorInfotonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.Helptonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.LocalizedMessagetonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.PreconditionFailuretonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.QuotaFailuretonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.RequestInfotonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.ResourceInfotonic_types.richer_error.StatusExt→tonic_types.generated.google_rpc.RetryInfo
- Direction
- tonic_types.richer_error uses tonic_types.generated.google_rpc, so a change to tonic_types.generated.google_rpc can break tonic_types.richer_error, while a change to tonic_types.richer_error can't break tonic_types.generated.google_rpc.
- 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.
22→6 tonic_xds.client.retry uses grpc.server.service✕
- Connections
- 2 pairs of types, where a type in tonic_xds.client.retry uses a type in grpc.server.service.
- The types involved
tonic_xds.client.retry.RetryLayer→grpc.server.service.Servicetonic_xds.client.retry.RetryService→grpc.server.service.Service
- Direction
- tonic_xds.client.retry uses grpc.server.service, so a change to grpc.server.service can break tonic_xds.client.retry, while a change to tonic_xds.client.retry can't break grpc.server.service.
- Position
- Below the diagonal: tonic_xds.client.retry uses a module listed above it, which is the healthy direction.
22→16 tonic_xds.client.retry uses tonic.request✕
- Connections
- 2 pairs of types, where a type in tonic_xds.client.retry uses a type in tonic.request.
- The types involved
tonic_xds.client.retry.RetryPolicy→tonic.request.Requesttonic_xds.client.retry.RetryService→tonic.request.Request
- Direction
- tonic_xds.client.retry uses tonic.request, so a change to tonic.request can break tonic_xds.client.retry, while a change to tonic_xds.client.retry can't break tonic.request.
- Position
- Below the diagonal: tonic_xds.client.retry uses a module listed above it, which is the healthy direction.
22→17 tonic_xds.client.retry uses tonic.status✕
- Connections
- 2 pairs of types, where a type in tonic_xds.client.retry uses a type in tonic.status.
- The types involved
tonic_xds.client.retry.GrpcRetryClassifier→tonic.status.Codetonic_xds.client.retry.retry$module→tonic.status.Code
- Direction
- tonic_xds.client.retry uses tonic.status, so a change to tonic.status can break tonic_xds.client.retry, while a change to tonic_xds.client.retry can't break tonic.status.
- Position
- Below the diagonal: tonic_xds.client.retry uses a module listed above it, which is the healthy direction.
23→1 grpc.core uses grpc.attributes✕
- Connections
- 1 pair of types, where a type in grpc.core uses a type in grpc.attributes.
- The types involved
grpc.core.Address→grpc.attributes.Attributes
- Direction
- grpc.core uses grpc.attributes, so a change to grpc.attributes can break grpc.core, while a change to grpc.core can't break grpc.attributes.
- Position
- Below the diagonal: grpc.core uses a module listed above it, which is the healthy direction.
23→18 grpc.core uses grpc.credentials✕
- Connections
- 1 pair of types, where a type in grpc.core uses a type in grpc.credentials.
- The types involved
grpc.core.ConnectionInfo→grpc.credentials.SecurityInfo
- Direction
- grpc.core uses grpc.credentials, so a change to grpc.credentials can break grpc.core, while a change to grpc.core can't break grpc.credentials.
- Position
- Below the diagonal: grpc.core uses a module listed above it, which is the healthy direction.
23→20 grpc.core uses tonic.transport.error✕
- Connections
- 2 pairs of types, where a type in grpc.core uses a type in tonic.transport.error.
- The types involved
grpc.core.StreamEnded→tonic.transport.error.Errorgrpc.core.StreamError→tonic.transport.error.Error
- Direction
- grpc.core uses tonic.transport.error, so a change to tonic.transport.error can break grpc.core, while a change to grpc.core can't break tonic.transport.error.
- Position
- Below the diagonal: grpc.core uses a module listed above it, which is the healthy direction.
24→3 tonic_types.generated.google_rpc uses grpc.client.load_balancing.subchannel.private✕
- Connections
- 1 pair of types, where a type in tonic_types.generated.google_rpc uses a type in grpc.client.load_balancing.subchannel.private.
- The types involved
tonic_types.generated.google_rpc.Status→grpc.client.load_balancing.subchannel.private.Sealed
- Direction
- tonic_types.generated.google_rpc uses grpc.client.load_balancing.subchannel.private, so a change to grpc.client.load_balancing.subchannel.private can break tonic_types.generated.google_rpc, while a change to tonic_types.generated.google_rpc can't break grpc.client.load_balancing.subchannel.private.
- Position
- Below the diagonal: tonic_types.generated.google_rpc uses a module listed above it, which is the healthy direction.
24→13 tonic_types.generated.google_rpc uses grpc.metadata.map✕
- Connections
- 1 pair of types, where a type in tonic_types.generated.google_rpc uses a type in grpc.metadata.map.
- The types involved
tonic_types.generated.google_rpc.Status→grpc.metadata.map.MetadataMap
- Direction
- tonic_types.generated.google_rpc uses grpc.metadata.map, so a change to grpc.metadata.map can break tonic_types.generated.google_rpc, while a change to tonic_types.generated.google_rpc can't break grpc.metadata.map.
- Position
- Below the diagonal: tonic_types.generated.google_rpc uses a module listed above it, which is the healthy direction.
24→17 tonic_types.generated.google_rpc uses tonic.status✕
- Connections
- 1 pair of types, where a type in tonic_types.generated.google_rpc uses a type in tonic.status.
- The types involved
tonic_types.generated.google_rpc.Status→tonic.status.Code
- Direction
- tonic_types.generated.google_rpc uses tonic.status, so a change to tonic.status can break tonic_types.generated.google_rpc, while a change to tonic_types.generated.google_rpc can't break tonic.status.
- Position
- Below the diagonal: tonic_types.generated.google_rpc uses a module listed above it, which is the healthy direction.
24→21 tonic_types.generated.google_rpc uses tonic_types.richer_error✕
- Connections
- 2 pairs of types, where a type in tonic_types.generated.google_rpc uses a type in tonic_types.richer_error.
- The types involved
tonic_types.generated.google_rpc.Status→tonic_types.richer_error.RpcStatusExttonic_types.generated.google_rpc.Status→tonic_types.richer_error.StatusExt
- Direction
- tonic_types.generated.google_rpc uses tonic_types.richer_error, so a change to tonic_types.richer_error can break tonic_types.generated.google_rpc, while a change to tonic_types.generated.google_rpc can't break tonic_types.richer_error.
- Position
- Below the diagonal: tonic_types.generated.google_rpc uses a module listed above it, which is the healthy direction.
25→1 xds_client.client.config uses grpc.attributes✕
- Connections
- 1 pair of types, where a type in xds_client.client.config uses a type in grpc.attributes.
- The types involved
xds_client.client.config.ClientConfig→grpc.attributes.Node
- Direction
- xds_client.client.config uses grpc.attributes, so a change to grpc.attributes can break xds_client.client.config, while a change to xds_client.client.config can't break grpc.attributes.
- Position
- Below the diagonal: xds_client.client.config uses a module listed above it, which is the healthy direction.
25→22 xds_client.client.config uses tonic_xds.client.retry✕
- Connections
- 1 pair of types, where a type in xds_client.client.config uses a type in tonic_xds.client.retry.
- The types involved
xds_client.client.config.ClientConfig→tonic_xds.client.retry.RetryPolicy
- Direction
- xds_client.client.config uses tonic_xds.client.retry, so a change to tonic_xds.client.retry can break xds_client.client.config, while a change to xds_client.client.config can't break tonic_xds.client.retry.
- Position
- Below the diagonal: xds_client.client.config uses a module listed above it, which is the healthy direction.
26→2 grpc.client uses grpc.client.call_options✕
- Connections
- 3 pairs of types, where a type in grpc.client uses a type in grpc.client.call_options.
- The types involved
grpc.client.DynInvoke→grpc.client.call_options.CallOptionsgrpc.client.Invoke→grpc.client.call_options.CallOptionsgrpc.client.InvokeOnce→grpc.client.call_options.CallOptions
- Direction
- grpc.client uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc.client, while a change to grpc.client can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc.client uses a module listed above it, which is the healthy direction.
26→13 grpc.client uses grpc.metadata.map✕
- Connections
- 3 pairs of types, where a type in grpc.client uses a type in grpc.metadata.map.
- The types involved
grpc.client.RequestHeaders→grpc.metadata.map.MetadataMapgrpc.client.ResponseHeaders→grpc.metadata.map.MetadataMapgrpc.client.Trailers→grpc.metadata.map.MetadataMap
- Direction
- grpc.client uses grpc.metadata.map, so a change to grpc.metadata.map can break grpc.client, while a change to grpc.client can't break grpc.metadata.map.
- Position
- Below the diagonal: grpc.client uses a module listed above it, which is the healthy direction.
26→23 grpc.client uses grpc.core✕
- Connections
- 2 pairs of types, where a type in grpc.client uses a type in grpc.core.
- The types involved
grpc.client.ResponseHeaders→grpc.core.ConnectionInfogrpc.client.Trailers→grpc.core.ConnectionInfo
- Direction
- grpc.client uses grpc.core, so a change to grpc.core can break grpc.client, while a change to grpc.client can't break grpc.core.
- Position
- Below the diagonal: grpc.client uses a module listed above it, which is the healthy direction.
27→4 grpc.client.transport uses grpc.credentials.common✕
- Connections
- 1 pair of types, where a type in grpc.client.transport uses a type in grpc.credentials.common.
- The types involved
grpc.client.transport.SecurityOpts→grpc.credentials.common.Authority
- Direction
- grpc.client.transport uses grpc.credentials.common, so a change to grpc.credentials.common can break grpc.client.transport, while a change to grpc.client.transport can't break grpc.credentials.common.
- Position
- Below the diagonal: grpc.client.transport uses a module listed above it, which is the healthy direction.
27→14 grpc.client.transport uses grpc.rt✕
- Connections
- 2 pairs of types, where a type in grpc.client.transport uses a type in grpc.rt.
- The types involved
grpc.client.transport.DynTransport→grpc.rt.GrpcRuntimegrpc.client.transport.Transport→grpc.rt.GrpcRuntime
- Direction
- grpc.client.transport uses grpc.rt, so a change to grpc.rt can break grpc.client.transport, while a change to grpc.client.transport can't break grpc.rt.
- Position
- Below the diagonal: grpc.client.transport uses a module listed above it, which is the healthy direction.
27→15 grpc.client.transport uses grpc.credentials.client✕
- Connections
- 1 pair of types, where a type in grpc.client.transport uses a type in grpc.credentials.client.
- The types involved
grpc.client.transport.SecurityOpts→grpc.credentials.client.ClientHandshakeInfo
- Direction
- grpc.client.transport uses grpc.credentials.client, so a change to grpc.credentials.client can break grpc.client.transport, while a change to grpc.client.transport can't break grpc.credentials.client.
- Position
- Below the diagonal: grpc.client.transport uses a module listed above it, which is the healthy direction.
27→23 grpc.client.transport uses grpc.core✕
- Connections
- 3 pairs of types, where a type in grpc.client.transport uses a type in grpc.core.
- The types involved
grpc.client.transport.DynTransport→grpc.core.Addressgrpc.client.transport.ProxyOptions→grpc.core.Addressgrpc.client.transport.Transport→grpc.core.Address
- Direction
- grpc.client.transport uses grpc.core, so a change to grpc.core can break grpc.client.transport, while a change to grpc.client.transport can't break grpc.core.
- Position
- Below the diagonal: grpc.client.transport uses a module listed above it, which is the healthy direction.
28→2 grpc.client.load_balancing uses grpc.client.call_options✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing uses a type in grpc.client.call_options.
- The types involved
grpc.client.load_balancing.PickOptions→grpc.client.call_options.CallOptions
- Direction
- grpc.client.load_balancing uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc.client.load_balancing, while a change to grpc.client.load_balancing can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc.client.load_balancing uses a module listed above it, which is the healthy direction.
28→10 grpc.client.load_balancing uses grpc.client.name_resolution✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing uses a type in grpc.client.name_resolution.
- The types involved
grpc.client.load_balancing.LbPolicy→grpc.client.name_resolution.ResolverUpdate
- Direction
- grpc.client.load_balancing uses grpc.client.name_resolution, so a change to grpc.client.name_resolution can break grpc.client.load_balancing, while a change to grpc.client.load_balancing can't break grpc.client.name_resolution.
- Position
- Below the diagonal: grpc.client.load_balancing uses a module listed above it, which is the healthy direction.
28→13 grpc.client.load_balancing uses grpc.metadata.map✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing uses a type in grpc.metadata.map.
- The types involved
grpc.client.load_balancing.Pick→grpc.metadata.map.MetadataMap
- Direction
- grpc.client.load_balancing uses grpc.metadata.map, so a change to grpc.metadata.map can break grpc.client.load_balancing, while a change to grpc.client.load_balancing can't break grpc.metadata.map.
- Position
- Below the diagonal: grpc.client.load_balancing uses a module listed above it, which is the healthy direction.
28→14 grpc.client.load_balancing uses grpc.rt✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing uses a type in grpc.rt.
- The types involved
grpc.client.load_balancing.LbPolicyOptions→grpc.rt.GrpcRuntime
- Direction
- grpc.client.load_balancing uses grpc.rt, so a change to grpc.rt can break grpc.client.load_balancing, while a change to grpc.client.load_balancing can't break grpc.rt.
- Position
- Below the diagonal: grpc.client.load_balancing uses a module listed above it, which is the healthy direction.
28→23 grpc.client.load_balancing uses grpc.core✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing uses a type in grpc.core.
- The types involved
grpc.client.load_balancing.ChannelController→grpc.core.Address
- Direction
- grpc.client.load_balancing uses grpc.core, so a change to grpc.core can break grpc.client.load_balancing, while a change to grpc.client.load_balancing can't break grpc.core.
- Position
- Below the diagonal: grpc.client.load_balancing uses a module listed above it, which is the healthy direction.
28→26 grpc.client.load_balancing uses grpc.client✕
- Connections
- 2 pairs of types, where a type in grpc.client.load_balancing uses a type in grpc.client.
- The types involved
grpc.client.load_balancing.LbState→grpc.client.ConnectivityStategrpc.client.load_balancing.PickOptions→grpc.client.RequestHeaders
- Direction
- grpc.client.load_balancing uses grpc.client, so a change to grpc.client can break grpc.client.load_balancing, while a change to grpc.client.load_balancing can't break grpc.client.
- Position
- Below the diagonal: grpc.client.load_balancing uses a module listed above it, which is the healthy direction.
29→2 grpc.client.subchannel uses grpc.client.call_options✕
- Connections
- 1 pair of types, where a type in grpc.client.subchannel uses a type in grpc.client.call_options.
- The types involved
grpc.client.subchannel.InternalSubchannel→grpc.client.call_options.CallOptions
- Direction
- grpc.client.subchannel uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc.client.subchannel, while a change to grpc.client.subchannel can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc.client.subchannel uses a module listed above it, which is the healthy direction.
29→3 grpc.client.subchannel uses grpc.client.load_balancing.subchannel.private✕
- Connections
- 1 pair of types, where a type in grpc.client.subchannel uses a type in grpc.client.load_balancing.subchannel.private.
- The types involved
grpc.client.subchannel.InternalSubchannel→grpc.client.load_balancing.subchannel.private.Sealed
- Direction
- grpc.client.subchannel uses grpc.client.load_balancing.subchannel.private, so a change to grpc.client.load_balancing.subchannel.private can break grpc.client.subchannel, while a change to grpc.client.subchannel can't break grpc.client.load_balancing.subchannel.private.
- Position
- Below the diagonal: grpc.client.subchannel uses a module listed above it, which is the healthy direction.
29→4 grpc.client.subchannel uses grpc.credentials.common✕
- Connections
- 2 pairs of types, where a type in grpc.client.subchannel uses a type in grpc.credentials.common.
- The types involved
grpc.client.subchannel.ReadyState→grpc.credentials.common.Authoritygrpc.client.subchannel.subchannel$module→grpc.credentials.common.Authority
- Direction
- grpc.client.subchannel uses grpc.credentials.common, so a change to grpc.credentials.common can break grpc.client.subchannel, while a change to grpc.client.subchannel can't break grpc.credentials.common.
- Position
- Below the diagonal: grpc.client.subchannel uses a module listed above it, which is the healthy direction.
29→14 grpc.client.subchannel uses grpc.rt✕
- Connections
- 3 pairs of types, where a type in grpc.client.subchannel uses a type in grpc.rt.
- The types involved
grpc.client.subchannel.InternalSubchannel→grpc.rt.GrpcRuntimegrpc.client.subchannel.InternalSubchannelData→grpc.rt.GrpcRuntimegrpc.client.subchannel.NopBackoff→grpc.rt.GrpcRuntime
- Direction
- grpc.client.subchannel uses grpc.rt, so a change to grpc.rt can break grpc.client.subchannel, while a change to grpc.client.subchannel can't break grpc.rt.
- Position
- Below the diagonal: grpc.client.subchannel uses a module listed above it, which is the healthy direction.
29→23 grpc.client.subchannel uses grpc.core✕
- Connections
- 3 pairs of types, where a type in grpc.client.subchannel uses a type in grpc.core.
- The types involved
grpc.client.subchannel.InternalSubchannel→grpc.core.Addressgrpc.client.subchannel.InternalSubchannelData→grpc.core.Addressgrpc.client.subchannel.ReadyState→grpc.core.ConnectionInfo
- Direction
- grpc.client.subchannel uses grpc.core, so a change to grpc.core can break grpc.client.subchannel, while a change to grpc.client.subchannel can't break grpc.core.
- Position
- Below the diagonal: grpc.client.subchannel uses a module listed above it, which is the healthy direction.
29→26 grpc.client.subchannel uses grpc.client✕
- Connections
- 2 pairs of types, where a type in grpc.client.subchannel uses a type in grpc.client.
- The types involved
grpc.client.subchannel.InternalSubchannel→grpc.client.DynInvokegrpc.client.subchannel.InternalSubchannel→grpc.client.RequestHeaders
- Direction
- grpc.client.subchannel uses grpc.client, so a change to grpc.client can break grpc.client.subchannel, while a change to grpc.client.subchannel can't break grpc.client.
- Position
- Below the diagonal: grpc.client.subchannel uses a module listed above it, which is the healthy direction.
29→27 grpc.client.subchannel uses grpc.client.transport✕
- Connections
- 3 pairs of types, where a type in grpc.client.subchannel uses a type in grpc.client.transport.
- The types involved
grpc.client.subchannel.InternalSubchannel→grpc.client.transport.SecurityOptsgrpc.client.subchannel.InternalSubchannelData→grpc.client.transport.SecurityOptsgrpc.client.subchannel.InternalSubchannelData→grpc.client.transport.TransportOptions
- Direction
- grpc.client.subchannel uses grpc.client.transport, so a change to grpc.client.transport can break grpc.client.subchannel, while a change to grpc.client.subchannel can't break grpc.client.transport.
- Position
- Below the diagonal: grpc.client.subchannel uses a module listed above it, which is the healthy direction.
30→2 grpc.client.transport.tonic uses grpc.client.call_options✕
- Connections
- 1 pair of types, where a type in grpc.client.transport.tonic uses a type in grpc.client.call_options.
- The types involved
grpc.client.transport.tonic.TonicTransport→grpc.client.call_options.CallOptions
- Direction
- grpc.client.transport.tonic uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc.client.transport.tonic, while a change to grpc.client.transport.tonic can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc.client.transport.tonic uses a module listed above it, which is the healthy direction.
30→14 grpc.client.transport.tonic uses grpc.rt✕
- Connections
- 2 pairs of types, where a type in grpc.client.transport.tonic uses a type in grpc.rt.
- The types involved
grpc.client.transport.tonic.TonicTransport→grpc.rt.GrpcRuntimegrpc.client.transport.tonic.TransportBuilder→grpc.rt.GrpcRuntime
- Direction
- grpc.client.transport.tonic uses grpc.rt, so a change to grpc.rt can break grpc.client.transport.tonic, while a change to grpc.client.transport.tonic can't break grpc.rt.
- Position
- Below the diagonal: grpc.client.transport.tonic uses a module listed above it, which is the healthy direction.
30→16 grpc.client.transport.tonic uses tonic.request✕
- Connections
- 3 pairs of types, where a type in grpc.client.transport.tonic uses a type in tonic.request.
- The types involved
grpc.client.transport.tonic.SendRequestWrapper→tonic.request.Requestgrpc.client.transport.tonic.TonicRecvStream→tonic.request.CancellationHandlegrpc.client.transport.tonic.TonicService→tonic.request.Request
- Direction
- grpc.client.transport.tonic uses tonic.request, so a change to tonic.request can break grpc.client.transport.tonic, while a change to grpc.client.transport.tonic can't break tonic.request.
- Position
- Below the diagonal: grpc.client.transport.tonic uses a module listed above it, which is the healthy direction.
30→19 grpc.client.transport.tonic uses tonic.client.grpc✕
- Connections
- 1 pair of types, where a type in grpc.client.transport.tonic uses a type in tonic.client.grpc.
- The types involved
grpc.client.transport.tonic.TonicTransport→tonic.client.grpc.Grpc
- Direction
- grpc.client.transport.tonic uses tonic.client.grpc, so a change to tonic.client.grpc can break grpc.client.transport.tonic, while a change to grpc.client.transport.tonic can't break tonic.client.grpc.
- Position
- Below the diagonal: grpc.client.transport.tonic uses a module listed above it, which is the healthy direction.
30→23 grpc.client.transport.tonic uses grpc.core✕
- Connections
- 3 pairs of types, where a type in grpc.client.transport.tonic uses a type in grpc.core.
- The types involved
grpc.client.transport.tonic.TonicRecvStream→grpc.core.ConnectionInfogrpc.client.transport.tonic.TonicTransport→grpc.core.ConnectionInfogrpc.client.transport.tonic.TransportBuilder→grpc.core.Address
- Direction
- grpc.client.transport.tonic uses grpc.core, so a change to grpc.core can break grpc.client.transport.tonic, while a change to grpc.client.transport.tonic can't break grpc.core.
- Position
- Below the diagonal: grpc.client.transport.tonic uses a module listed above it, which is the healthy direction.
30→26 grpc.client.transport.tonic uses grpc.client✕
- Connections
- 6 pairs of types, where a type in grpc.client.transport.tonic uses a type in grpc.client.
- The types involved
grpc.client.transport.tonic.TonicRecvStream→grpc.client.RecvStreamgrpc.client.transport.tonic.TonicRecvStream→grpc.client.ResponseStreamItemgrpc.client.transport.tonic.TonicSendStream→grpc.client.SendOptionsgrpc.client.transport.tonic.TonicSendStream→grpc.client.SendStreamgrpc.client.transport.tonic.TonicTransport→grpc.client.Invokegrpc.client.transport.tonic.TonicTransport→grpc.client.RequestHeaders
- Direction
- grpc.client.transport.tonic uses grpc.client, so a change to grpc.client can break grpc.client.transport.tonic, while a change to grpc.client.transport.tonic can't break grpc.client.
- Position
- Below the diagonal: grpc.client.transport.tonic uses a module listed above it, which is the healthy direction.
30→27 grpc.client.transport.tonic uses grpc.client.transport✕
- Connections
- 3 pairs of types, where a type in grpc.client.transport.tonic uses a type in grpc.client.transport.
- The types involved
grpc.client.transport.tonic.TransportBuilder→grpc.client.transport.SecurityOptsgrpc.client.transport.tonic.TransportBuilder→grpc.client.transport.Transportgrpc.client.transport.tonic.TransportBuilder→grpc.client.transport.TransportOptions
- Direction
- grpc.client.transport.tonic uses grpc.client.transport, so a change to grpc.client.transport can break grpc.client.transport.tonic, while a change to grpc.client.transport.tonic can't break grpc.client.transport.
- Position
- Below the diagonal: grpc.client.transport.tonic uses a module listed above it, which is the healthy direction.
31→2 grpc.server uses grpc.client.call_options✕
- Connections
- 3 pairs of types, where a type in grpc.server uses a type in grpc.client.call_options.
- The types involved
grpc.server.DynHandle→grpc.client.call_options.CallOptionsgrpc.server.DynHandleWrapper→grpc.client.call_options.CallOptionsgrpc.server.Handle→grpc.client.call_options.CallOptions
- Direction
- grpc.server uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc.server, while a change to grpc.server can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc.server uses a module listed above it, which is the healthy direction.
31→3 grpc.server uses grpc.client.load_balancing.subchannel.private✕
- Connections
- 1 pair of types, where a type in grpc.server uses a type in grpc.client.load_balancing.subchannel.private.
- The types involved
grpc.server.Listener→grpc.client.load_balancing.subchannel.private.Sealed
- Direction
- grpc.server uses grpc.client.load_balancing.subchannel.private, so a change to grpc.client.load_balancing.subchannel.private can break grpc.server, while a change to grpc.server can't break grpc.client.load_balancing.subchannel.private.
- Position
- Below the diagonal: grpc.server uses a module listed above it, which is the healthy direction.
31→5 grpc.server uses grpc.private✕
- Connections
- 3 pairs of types, where a type in grpc.server uses a type in grpc.private.
- The types involved
grpc.server.GracefulConnection→grpc.private.Internalgrpc.server.Listener→grpc.private.Internalgrpc.server.Transport→grpc.private.Internal
- Direction
- grpc.server uses grpc.private, so a change to grpc.private can break grpc.server, while a change to grpc.server can't break grpc.private.
- Position
- Below the diagonal: grpc.server uses a module listed above it, which is the healthy direction.
31→13 grpc.server uses grpc.metadata.map✕
- Connections
- 3 pairs of types, where a type in grpc.server uses a type in grpc.metadata.map.
- The types involved
grpc.server.RequestHeaders→grpc.metadata.map.MetadataMapgrpc.server.ResponseHeaders→grpc.metadata.map.MetadataMapgrpc.server.Trailers→grpc.metadata.map.MetadataMap
- Direction
- grpc.server uses grpc.metadata.map, so a change to grpc.metadata.map can break grpc.server, while a change to grpc.server can't break grpc.metadata.map.
- Position
- Below the diagonal: grpc.server uses a module listed above it, which is the healthy direction.
31→14 grpc.server uses grpc.rt✕
- Connections
- 2 pairs of types, where a type in grpc.server uses a type in grpc.rt.
- The types involved
grpc.server.Server→grpc.rt.GrpcRuntimegrpc.server.Transport→grpc.rt.GrpcRuntime
- Direction
- grpc.server uses grpc.rt, so a change to grpc.rt can break grpc.server, while a change to grpc.server can't break grpc.rt.
- Position
- Below the diagonal: grpc.server uses a module listed above it, which is the healthy direction.
31→23 grpc.server uses grpc.core✕
- Connections
- 1 pair of types, where a type in grpc.server uses a type in grpc.core.
- The types involved
grpc.server.RequestHeaders→grpc.core.ConnectionInfo
- Direction
- grpc.server uses grpc.core, so a change to grpc.core can break grpc.server, while a change to grpc.server can't break grpc.core.
- Position
- Below the diagonal: grpc.server uses a module listed above it, which is the healthy direction.
31→26 grpc.server uses grpc.client✕
- Connections
- 10 pairs of types, where a type in grpc.server uses a type in grpc.client.
- The types involved
grpc.server.DynHandle→grpc.client.RequestHeadersgrpc.server.DynHandle→grpc.client.Trailersgrpc.server.DynHandleWrapper→grpc.client.RequestHeadersgrpc.server.DynHandleWrapper→grpc.client.Trailersgrpc.server.DynSendStream→grpc.client.ResponseStreamItemgrpc.server.DynSendStream→grpc.client.SendOptionsgrpc.server.Handle→grpc.client.RequestHeadersgrpc.server.Handle→grpc.client.Trailersgrpc.server.SendStream→grpc.client.ResponseStreamItemgrpc.server.SendStream→grpc.client.SendOptions
- Direction
- grpc.server uses grpc.client, so a change to grpc.client can break grpc.server, while a change to grpc.server can't break grpc.client.
- Position
- Below the diagonal: grpc.server uses a module listed above it, which is the healthy direction.
31→27 grpc.server uses grpc.client.transport✕
- Connections
- 1 pair of types, where a type in grpc.server uses a type in grpc.client.transport.
- The types involved
grpc.server.Listener→grpc.client.transport.Transport
- Direction
- grpc.server uses grpc.client.transport, so a change to grpc.client.transport can break grpc.server, while a change to grpc.server can't break grpc.client.transport.
- Position
- Below the diagonal: grpc.server uses a module listed above it, which is the healthy direction.
32→2 grpc.client.channel uses grpc.client.call_options✕
- Connections
- 1 pair of types, where a type in grpc.client.channel uses a type in grpc.client.call_options.
- The types involved
grpc.client.channel.Channel→grpc.client.call_options.CallOptions
- Direction
- grpc.client.channel uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc.client.channel, while a change to grpc.client.channel can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc.client.channel uses a module listed above it, which is the healthy direction.
32→4 grpc.client.channel uses grpc.credentials.common✕
- Connections
- 1 pair of types, where a type in grpc.client.channel uses a type in grpc.credentials.common.
- The types involved
grpc.client.channel.channel$module→grpc.credentials.common.Authority
- Direction
- grpc.client.channel uses grpc.credentials.common, so a change to grpc.credentials.common can break grpc.client.channel, while a change to grpc.client.channel can't break grpc.credentials.common.
- Position
- Below the diagonal: grpc.client.channel uses a module listed above it, which is the healthy direction.
32→10 grpc.client.channel uses grpc.client.name_resolution✕
- Connections
- 2 pairs of types, where a type in grpc.client.channel uses a type in grpc.client.name_resolution.
- The types involved
grpc.client.channel.PersistentChannel→grpc.client.name_resolution.Targetgrpc.client.channel.ResolverChannelController→grpc.client.name_resolution.ResolverUpdate
- Direction
- grpc.client.channel uses grpc.client.name_resolution, so a change to grpc.client.name_resolution can break grpc.client.channel, while a change to grpc.client.channel can't break grpc.client.name_resolution.
- Position
- Below the diagonal: grpc.client.channel uses a module listed above it, which is the healthy direction.
32→14 grpc.client.channel uses grpc.rt✕
- Connections
- 4 pairs of types, where a type in grpc.client.channel uses a type in grpc.rt.
- The types involved
grpc.client.channel.ChannelBuilder→grpc.rt.GrpcRuntimegrpc.client.channel.LbChannelController→grpc.rt.GrpcRuntimegrpc.client.channel.PersistentChannel→grpc.rt.GrpcRuntimegrpc.client.channel.ResolverChannelController→grpc.rt.GrpcRuntime
- Direction
- grpc.client.channel uses grpc.rt, so a change to grpc.rt can break grpc.client.channel, while a change to grpc.client.channel can't break grpc.rt.
- Position
- Below the diagonal: grpc.client.channel uses a module listed above it, which is the healthy direction.
32→23 grpc.client.channel uses grpc.core✕
- Connections
- 1 pair of types, where a type in grpc.client.channel uses a type in grpc.core.
- The types involved
grpc.client.channel.LbChannelController→grpc.core.Address
- Direction
- grpc.client.channel uses grpc.core, so a change to grpc.core can break grpc.client.channel, while a change to grpc.client.channel can't break grpc.core.
- Position
- Below the diagonal: grpc.client.channel uses a module listed above it, which is the healthy direction.
32→26 grpc.client.channel uses grpc.client✕
- Connections
- 5 pairs of types, where a type in grpc.client.channel uses a type in grpc.client.
- The types involved
grpc.client.channel.ActiveChannel→grpc.client.ConnectivityStategrpc.client.channel.Channel→grpc.client.ConnectivityStategrpc.client.channel.Channel→grpc.client.Invokegrpc.client.channel.Channel→grpc.client.RequestHeadersgrpc.client.channel.PersistentChannel→grpc.client.ConnectivityState
- Direction
- grpc.client.channel uses grpc.client, so a change to grpc.client can break grpc.client.channel, while a change to grpc.client.channel can't break grpc.client.
- Position
- Below the diagonal: grpc.client.channel uses a module listed above it, which is the healthy direction.
32→27 grpc.client.channel uses grpc.client.transport✕
- Connections
- 3 pairs of types, where a type in grpc.client.channel uses a type in grpc.client.transport.
- The types involved
grpc.client.channel.LbChannelController→grpc.client.transport.SecurityOptsgrpc.client.channel.PersistentChannel→grpc.client.transport.SecurityOptsgrpc.client.channel.ResolverChannelController→grpc.client.transport.SecurityOpts
- Direction
- grpc.client.channel uses grpc.client.transport, so a change to grpc.client.transport can break grpc.client.channel, while a change to grpc.client.channel can't break grpc.client.transport.
- Position
- Below the diagonal: grpc.client.channel uses a module listed above it, which is the healthy direction.
32→28 grpc.client.channel uses grpc.client.load_balancing✕
- Connections
- 5 pairs of types, where a type in grpc.client.channel uses a type in grpc.client.load_balancing.
- The types involved
grpc.client.channel.LbChannelController→grpc.client.load_balancing.ChannelControllergrpc.client.channel.LbChannelController→grpc.client.load_balancing.LbStategrpc.client.channel.LbWorkScheduler→grpc.client.load_balancing.WorkSchedulergrpc.client.channel.ResolverChannelController→grpc.client.load_balancing.ChannelControllergrpc.client.channel.ResolverWorkScheduler→grpc.client.load_balancing.WorkScheduler
- Direction
- grpc.client.channel uses grpc.client.load_balancing, so a change to grpc.client.load_balancing can break grpc.client.channel, while a change to grpc.client.channel can't break grpc.client.load_balancing.
- Position
- Below the diagonal: grpc.client.channel uses a module listed above it, which is the healthy direction.
33→10 grpc.client.load_balancing.child_manager uses grpc.client.name_resolution✕
- Connections
- 2 pairs of types, where a type in grpc.client.load_balancing.child_manager uses a type in grpc.client.name_resolution.
- The types involved
grpc.client.load_balancing.child_manager.Child→grpc.client.name_resolution.ResolverUpdategrpc.client.load_balancing.child_manager.ChildManager→grpc.client.name_resolution.ResolverUpdate
- Direction
- grpc.client.load_balancing.child_manager uses grpc.client.name_resolution, so a change to grpc.client.name_resolution can break grpc.client.load_balancing.child_manager, while a change to grpc.client.load_balancing.child_manager can't break grpc.client.name_resolution.
- Position
- Below the diagonal: grpc.client.load_balancing.child_manager uses a module listed above it, which is the healthy direction.
33→14 grpc.client.load_balancing.child_manager uses grpc.rt✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing.child_manager uses a type in grpc.rt.
- The types involved
grpc.client.load_balancing.child_manager.ChildManager→grpc.rt.GrpcRuntime
- Direction
- grpc.client.load_balancing.child_manager uses grpc.rt, so a change to grpc.rt can break grpc.client.load_balancing.child_manager, while a change to grpc.client.load_balancing.child_manager can't break grpc.rt.
- Position
- Below the diagonal: grpc.client.load_balancing.child_manager uses a module listed above it, which is the healthy direction.
33→23 grpc.client.load_balancing.child_manager uses grpc.core✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing.child_manager uses a type in grpc.core.
- The types involved
grpc.client.load_balancing.child_manager.WrappedController→grpc.core.Address
- Direction
- grpc.client.load_balancing.child_manager uses grpc.core, so a change to grpc.core can break grpc.client.load_balancing.child_manager, while a change to grpc.client.load_balancing.child_manager can't break grpc.core.
- Position
- Below the diagonal: grpc.client.load_balancing.child_manager uses a module listed above it, which is the healthy direction.
33→26 grpc.client.load_balancing.child_manager uses grpc.client✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing.child_manager uses a type in grpc.client.
- The types involved
grpc.client.load_balancing.child_manager.ChildManager→grpc.client.ConnectivityState
- Direction
- grpc.client.load_balancing.child_manager uses grpc.client, so a change to grpc.client can break grpc.client.load_balancing.child_manager, while a change to grpc.client.load_balancing.child_manager can't break grpc.client.
- Position
- Below the diagonal: grpc.client.load_balancing.child_manager uses a module listed above it, which is the healthy direction.
33→28 grpc.client.load_balancing.child_manager uses grpc.client.load_balancing✕
- Connections
- 5 pairs of types, where a type in grpc.client.load_balancing.child_manager uses a type in grpc.client.load_balancing.
- The types involved
grpc.client.load_balancing.child_manager.Child→grpc.client.load_balancing.LbPolicyOptionsgrpc.client.load_balancing.child_manager.Child→grpc.client.load_balancing.LbStategrpc.client.load_balancing.child_manager.ChildWorkScheduler→grpc.client.load_balancing.WorkSchedulergrpc.client.load_balancing.child_manager.WrappedController→grpc.client.load_balancing.ChannelControllergrpc.client.load_balancing.child_manager.WrappedController→grpc.client.load_balancing.LbState
- Direction
- grpc.client.load_balancing.child_manager uses grpc.client.load_balancing, so a change to grpc.client.load_balancing can break grpc.client.load_balancing.child_manager, while a change to grpc.client.load_balancing.child_manager can't break grpc.client.load_balancing.
- Position
- Below the diagonal: grpc.client.load_balancing.child_manager uses a module listed above it, which is the healthy direction.
34→10 grpc.client.load_balancing.pick_first uses grpc.client.name_resolution✕
- Connections
- 2 pairs of types, where a type in grpc.client.load_balancing.pick_first uses a type in grpc.client.name_resolution.
- The types involved
grpc.client.load_balancing.pick_first.PickFirstPolicy→grpc.client.name_resolution.Endpointgrpc.client.load_balancing.pick_first.PickFirstPolicy→grpc.client.name_resolution.ResolverUpdate
- Direction
- grpc.client.load_balancing.pick_first uses grpc.client.name_resolution, so a change to grpc.client.name_resolution can break grpc.client.load_balancing.pick_first, while a change to grpc.client.load_balancing.pick_first can't break grpc.client.name_resolution.
- Position
- Below the diagonal: grpc.client.load_balancing.pick_first uses a module listed above it, which is the healthy direction.
34→14 grpc.client.load_balancing.pick_first uses grpc.rt✕
- Connections
- 2 pairs of types, where a type in grpc.client.load_balancing.pick_first uses a type in grpc.rt.
- The types involved
grpc.client.load_balancing.pick_first.PickFirstPolicy→grpc.rt.GrpcRuntimegrpc.client.load_balancing.pick_first.Timer→grpc.rt.GrpcRuntime
- Direction
- grpc.client.load_balancing.pick_first uses grpc.rt, so a change to grpc.rt can break grpc.client.load_balancing.pick_first, while a change to grpc.client.load_balancing.pick_first can't break grpc.rt.
- Position
- Below the diagonal: grpc.client.load_balancing.pick_first uses a module listed above it, which is the healthy direction.
34→23 grpc.client.load_balancing.pick_first uses grpc.core✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing.pick_first uses a type in grpc.core.
- The types involved
grpc.client.load_balancing.pick_first.PickFirstPolicy→grpc.core.Address
- Direction
- grpc.client.load_balancing.pick_first uses grpc.core, so a change to grpc.core can break grpc.client.load_balancing.pick_first, while a change to grpc.client.load_balancing.pick_first can't break grpc.core.
- Position
- Below the diagonal: grpc.client.load_balancing.pick_first uses a module listed above it, which is the healthy direction.
34→26 grpc.client.load_balancing.pick_first uses grpc.client✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing.pick_first uses a type in grpc.client.
- The types involved
grpc.client.load_balancing.pick_first.PickFirstPolicy→grpc.client.ConnectivityState
- Direction
- grpc.client.load_balancing.pick_first uses grpc.client, so a change to grpc.client can break grpc.client.load_balancing.pick_first, while a change to grpc.client.load_balancing.pick_first can't break grpc.client.
- Position
- Below the diagonal: grpc.client.load_balancing.pick_first uses a module listed above it, which is the healthy direction.
34→28 grpc.client.load_balancing.pick_first uses grpc.client.load_balancing✕
- Connections
- 11 pairs of types, where a type in grpc.client.load_balancing.pick_first uses a type in grpc.client.load_balancing.
- The types involved
grpc.client.load_balancing.pick_first.IdlePicker→grpc.client.load_balancing.PickOptionsgrpc.client.load_balancing.pick_first.IdlePicker→grpc.client.load_balancing.PickResultgrpc.client.load_balancing.pick_first.IdlePicker→grpc.client.load_balancing.Pickergrpc.client.load_balancing.pick_first.OneSubchannelPicker→grpc.client.load_balancing.PickOptionsgrpc.client.load_balancing.pick_first.OneSubchannelPicker→grpc.client.load_balancing.PickResultgrpc.client.load_balancing.pick_first.OneSubchannelPicker→grpc.client.load_balancing.Pickergrpc.client.load_balancing.pick_first.PickFirstBuilder→grpc.client.load_balancing.LbConfigJsongrpc.client.load_balancing.pick_first.PickFirstBuilder→grpc.client.load_balancing.LbPolicygrpc.client.load_balancing.pick_first.PickFirstBuilder→grpc.client.load_balancing.LbPolicyBuildergrpc.client.load_balancing.pick_first.PickFirstBuilder→grpc.client.load_balancing.LbPolicyOptionsgrpc.client.load_balancing.pick_first.PickFirstPolicy→grpc.client.load_balancing.LbPolicy
- Direction
- grpc.client.load_balancing.pick_first uses grpc.client.load_balancing, so a change to grpc.client.load_balancing can break grpc.client.load_balancing.pick_first, while a change to grpc.client.load_balancing.pick_first can't break grpc.client.load_balancing.
- Position
- Below the diagonal: grpc.client.load_balancing.pick_first uses a module listed above it, which is the healthy direction.
35→2 grpc.inmemory uses grpc.client.call_options✕
- Connections
- 1 pair of types, where a type in grpc.inmemory uses a type in grpc.client.call_options.
- The types involved
grpc.inmemory.InMemoryConnection→grpc.client.call_options.CallOptions
- Direction
- grpc.inmemory uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
35→3 grpc.inmemory uses grpc.client.load_balancing.subchannel.private✕
- Connections
- 1 pair of types, where a type in grpc.inmemory uses a type in grpc.client.load_balancing.subchannel.private.
- The types involved
grpc.inmemory.InMemoryListener→grpc.client.load_balancing.subchannel.private.Sealed
- Direction
- grpc.inmemory uses grpc.client.load_balancing.subchannel.private, so a change to grpc.client.load_balancing.subchannel.private can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.client.load_balancing.subchannel.private.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
35→5 grpc.inmemory uses grpc.private✕
- Connections
- 3 pairs of types, where a type in grpc.inmemory uses a type in grpc.private.
- The types involved
grpc.inmemory.InMemoryListener→grpc.private.Internalgrpc.inmemory.InMemoryServerCall→grpc.private.Internalgrpc.inmemory.InMemoryServingConnection→grpc.private.Internal
- Direction
- grpc.inmemory uses grpc.private, so a change to grpc.private can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.private.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
35→10 grpc.inmemory uses grpc.client.name_resolution✕
- Connections
- 4 pairs of types, where a type in grpc.inmemory uses a type in grpc.client.name_resolution.
- The types involved
grpc.inmemory.InMemoryResolver→grpc.client.name_resolution.Resolvergrpc.inmemory.InMemoryResolverBuilder→grpc.client.name_resolution.ResolverBuildergrpc.inmemory.InMemoryResolverBuilder→grpc.client.name_resolution.ResolverOptionsgrpc.inmemory.InMemoryResolverBuilder→grpc.client.name_resolution.Target
- Direction
- grpc.inmemory uses grpc.client.name_resolution, so a change to grpc.client.name_resolution can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.client.name_resolution.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
35→14 grpc.inmemory uses grpc.rt✕
- Connections
- 2 pairs of types, where a type in grpc.inmemory uses a type in grpc.rt.
- The types involved
grpc.inmemory.InMemoryServerCall→grpc.rt.GrpcRuntimegrpc.inmemory.InMemoryTransport→grpc.rt.GrpcRuntime
- Direction
- grpc.inmemory uses grpc.rt, so a change to grpc.rt can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.rt.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
35→23 grpc.inmemory uses grpc.core✕
- Connections
- 3 pairs of types, where a type in grpc.inmemory uses a type in grpc.core.
- The types involved
grpc.inmemory.InMemoryClientRecvStream→grpc.core.ConnectionInfogrpc.inmemory.InMemoryConnection→grpc.core.ConnectionInfogrpc.inmemory.InMemoryTransport→grpc.core.Address
- Direction
- grpc.inmemory uses grpc.core, so a change to grpc.core can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.core.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
35→26 grpc.inmemory uses grpc.client✕
- Connections
- 2 pairs of types, where a type in grpc.inmemory uses a type in grpc.client.
- The types involved
grpc.inmemory.InMemoryClientRecvStream→grpc.client.ResponseStreamItemgrpc.inmemory.InMemoryConnection→grpc.client.Invoke
- Direction
- grpc.inmemory uses grpc.client, so a change to grpc.client can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.client.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
35→27 grpc.inmemory uses grpc.client.transport✕
- Connections
- 4 pairs of types, where a type in grpc.inmemory uses a type in grpc.client.transport.
- The types involved
grpc.inmemory.InMemoryListener→grpc.client.transport.Transportgrpc.inmemory.InMemoryTransport→grpc.client.transport.SecurityOptsgrpc.inmemory.InMemoryTransport→grpc.client.transport.Transportgrpc.inmemory.InMemoryTransport→grpc.client.transport.TransportOptions
- Direction
- grpc.inmemory uses grpc.client.transport, so a change to grpc.client.transport can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.client.transport.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
35→31 grpc.inmemory uses grpc.server✕
- Connections
- 2 pairs of types, where a type in grpc.inmemory uses a type in grpc.server.
- The types involved
grpc.inmemory.InMemoryListener→grpc.server.Listenergrpc.inmemory.InMemoryServingConnection→grpc.server.GracefulConnection
- Direction
- grpc.inmemory uses grpc.server, so a change to grpc.server can break grpc.inmemory, while a change to grpc.inmemory can't break grpc.server.
- Position
- Below the diagonal: grpc.inmemory uses a module listed above it, which is the healthy direction.
36→2 grpc.server.interceptor uses grpc.client.call_options✕
- Connections
- 5 pairs of types, where a type in grpc.server.interceptor uses a type in grpc.client.call_options.
- The types involved
grpc.server.interceptor.Identity→grpc.client.call_options.CallOptionsgrpc.server.interceptor.Intercept→grpc.client.call_options.CallOptionsgrpc.server.interceptor.Intercepted→grpc.client.call_options.CallOptionsgrpc.server.interceptor.InterceptorChain→grpc.client.call_options.CallOptionsgrpc.server.interceptor.SecondThenNext→grpc.client.call_options.CallOptions
- Direction
- grpc.server.interceptor uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc.server.interceptor, while a change to grpc.server.interceptor can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc.server.interceptor uses a module listed above it, which is the healthy direction.
36→26 grpc.server.interceptor uses grpc.client✕
- Connections
- 7 pairs of types, where a type in grpc.server.interceptor uses a type in grpc.client.
- The types involved
grpc.server.interceptor.Identity→grpc.client.RequestHeadersgrpc.server.interceptor.Intercept→grpc.client.RequestHeadersgrpc.server.interceptor.Intercept→grpc.client.Trailersgrpc.server.interceptor.Intercepted→grpc.client.RequestHeadersgrpc.server.interceptor.InterceptorChain→grpc.client.RequestHeadersgrpc.server.interceptor.InterceptorChain→grpc.client.Trailersgrpc.server.interceptor.SecondThenNext→grpc.client.RequestHeaders
- Direction
- grpc.server.interceptor uses grpc.client, so a change to grpc.client can break grpc.server.interceptor, while a change to grpc.server.interceptor can't break grpc.client.
- Position
- Below the diagonal: grpc.server.interceptor uses a module listed above it, which is the healthy direction.
36→31 grpc.server.interceptor uses grpc.server✕
- Connections
- 3 pairs of types, where a type in grpc.server.interceptor uses a type in grpc.server.
- The types involved
grpc.server.interceptor.HandleExt→grpc.server.Handlegrpc.server.interceptor.Intercepted→grpc.server.Handlegrpc.server.interceptor.SecondThenNext→grpc.server.Handle
- Direction
- grpc.server.interceptor uses grpc.server, so a change to grpc.server can break grpc.server.interceptor, while a change to grpc.server.interceptor can't break grpc.server.
- Position
- Below the diagonal: grpc.server.interceptor uses a module listed above it, which is the healthy direction.
37→6 tonic.transport.server uses grpc.server.service✕
- Connections
- 2 pairs of types, where a type in tonic.transport.server uses a type in grpc.server.service.
- The types involved
tonic.transport.server.MakeSvc→grpc.server.service.Servicetonic.transport.server.Svc→grpc.server.service.Service
- Direction
- tonic.transport.server uses grpc.server.service, so a change to grpc.server.service can break tonic.transport.server, while a change to tonic.transport.server can't break grpc.server.service.
- Position
- Below the diagonal: tonic.transport.server uses a module listed above it, which is the healthy direction.
37→16 tonic.transport.server uses tonic.request✕
- Connections
- 1 pair of types, where a type in tonic.transport.server uses a type in tonic.request.
- The types involved
tonic.transport.server.Svc→tonic.request.Request
- Direction
- tonic.transport.server uses tonic.request, so a change to tonic.request can break tonic.transport.server, while a change to tonic.transport.server can't break tonic.request.
- Position
- Below the diagonal: tonic.transport.server uses a module listed above it, which is the healthy direction.
37→31 tonic.transport.server uses grpc.server✕
- Connections
- 2 pairs of types, where a type in tonic.transport.server uses a type in grpc.server.
- The types involved
tonic.transport.server.Router→grpc.server.Servertonic.transport.server.Server→grpc.server.Server
- Direction
- tonic.transport.server uses grpc.server, so a change to grpc.server can break tonic.transport.server, while a change to tonic.transport.server can't break grpc.server.
- Position
- Below the diagonal: tonic.transport.server uses a module listed above it, which is the healthy direction.
38→10 grpc.client.load_balancing.priority uses grpc.client.name_resolution✕
- Connections
- 3 pairs of types, where a type in grpc.client.load_balancing.priority uses a type in grpc.client.name_resolution.
- The types involved
grpc.client.load_balancing.priority.ChildData→grpc.client.name_resolution.ResolverUpdategrpc.client.load_balancing.priority.PriorityPolicy→grpc.client.name_resolution.ResolverUpdategrpc.client.load_balancing.priority.priority$module→grpc.client.name_resolution.ResolverUpdate
- Direction
- grpc.client.load_balancing.priority uses grpc.client.name_resolution, so a change to grpc.client.name_resolution can break grpc.client.load_balancing.priority, while a change to grpc.client.load_balancing.priority can't break grpc.client.name_resolution.
- Position
- Below the diagonal: grpc.client.load_balancing.priority uses a module listed above it, which is the healthy direction.
38→14 grpc.client.load_balancing.priority uses grpc.rt✕
- Connections
- 4 pairs of types, where a type in grpc.client.load_balancing.priority uses a type in grpc.rt.
- The types involved
grpc.client.load_balancing.priority.ChildState→grpc.rt.GrpcRuntimegrpc.client.load_balancing.priority.CreatedChild→grpc.rt.GrpcRuntimegrpc.client.load_balancing.priority.PriorityPolicy→grpc.rt.GrpcRuntimegrpc.client.load_balancing.priority.Timer→grpc.rt.GrpcRuntime
- Direction
- grpc.client.load_balancing.priority uses grpc.rt, so a change to grpc.rt can break grpc.client.load_balancing.priority, while a change to grpc.client.load_balancing.priority can't break grpc.rt.
- Position
- Below the diagonal: grpc.client.load_balancing.priority uses a module listed above it, which is the healthy direction.
38→26 grpc.client.load_balancing.priority uses grpc.client✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing.priority uses a type in grpc.client.
- The types involved
grpc.client.load_balancing.priority.ChildState→grpc.client.ConnectivityState
- Direction
- grpc.client.load_balancing.priority uses grpc.client, so a change to grpc.client can break grpc.client.load_balancing.priority, while a change to grpc.client.load_balancing.priority can't break grpc.client.
- Position
- Below the diagonal: grpc.client.load_balancing.priority uses a module listed above it, which is the healthy direction.
38→28 grpc.client.load_balancing.priority uses grpc.client.load_balancing✕
- Connections
- 7 pairs of types, where a type in grpc.client.load_balancing.priority uses a type in grpc.client.load_balancing.
- The types involved
grpc.client.load_balancing.priority.Builder→grpc.client.load_balancing.LbConfigJsongrpc.client.load_balancing.priority.Builder→grpc.client.load_balancing.LbPolicygrpc.client.load_balancing.priority.Builder→grpc.client.load_balancing.LbPolicyBuildergrpc.client.load_balancing.priority.Builder→grpc.client.load_balancing.LbPolicyOptionsgrpc.client.load_balancing.priority.PriorityChildConfig→grpc.client.load_balancing.ParsedLbConfiggrpc.client.load_balancing.priority.PriorityPolicy→grpc.client.load_balancing.LbPolicygrpc.client.load_balancing.priority.PriorityPolicy→grpc.client.load_balancing.LbState
- Direction
- grpc.client.load_balancing.priority uses grpc.client.load_balancing, so a change to grpc.client.load_balancing can break grpc.client.load_balancing.priority, while a change to grpc.client.load_balancing.priority can't break grpc.client.load_balancing.
- Position
- Below the diagonal: grpc.client.load_balancing.priority uses a module listed above it, which is the healthy direction.
38→33 grpc.client.load_balancing.priority uses grpc.client.load_balancing.child_manager✕
- Connections
- 2 pairs of types, where a type in grpc.client.load_balancing.priority uses a type in grpc.client.load_balancing.child_manager.
- The types involved
grpc.client.load_balancing.priority.CreatedChild→grpc.client.load_balancing.child_manager.Childgrpc.client.load_balancing.priority.priority$module→grpc.client.load_balancing.child_manager.Child
- Direction
- grpc.client.load_balancing.priority uses grpc.client.load_balancing.child_manager, so a change to grpc.client.load_balancing.child_manager can break grpc.client.load_balancing.priority, while a change to grpc.client.load_balancing.priority can't break grpc.client.load_balancing.child_manager.
- Position
- Below the diagonal: grpc.client.load_balancing.priority uses a module listed above it, which is the healthy direction.
38→34 grpc.client.load_balancing.priority uses grpc.client.load_balancing.pick_first✕
- Connections
- 1 pair of types, where a type in grpc.client.load_balancing.priority uses a type in grpc.client.load_balancing.pick_first.
- The types involved
grpc.client.load_balancing.priority.Timer→grpc.client.load_balancing.pick_first.Timer
- Direction
- grpc.client.load_balancing.priority uses grpc.client.load_balancing.pick_first, so a change to grpc.client.load_balancing.pick_first can break grpc.client.load_balancing.priority, while a change to grpc.client.load_balancing.priority can't break grpc.client.load_balancing.pick_first.
- Position
- Below the diagonal: grpc.client.load_balancing.priority uses a module listed above it, which is the healthy direction.
39→3 xds_client.transport.tonic uses grpc.client.load_balancing.subchannel.private✕
- Connections
- 2 pairs of types, where a type in xds_client.transport.tonic uses a type in grpc.client.load_balancing.subchannel.private.
- The types involved
xds_client.transport.tonic.TonicAdsReceiver→grpc.client.load_balancing.subchannel.private.Sealedxds_client.transport.tonic.TonicAdsSender→grpc.client.load_balancing.subchannel.private.Sealed
- Direction
- xds_client.transport.tonic uses grpc.client.load_balancing.subchannel.private, so a change to grpc.client.load_balancing.subchannel.private can break xds_client.transport.tonic, while a change to xds_client.transport.tonic can't break grpc.client.load_balancing.subchannel.private.
- Position
- Below the diagonal: xds_client.transport.tonic uses a module listed above it, which is the healthy direction.
39→13 xds_client.transport.tonic uses grpc.metadata.map✕
- Connections
- 1 pair of types, where a type in xds_client.transport.tonic uses a type in grpc.metadata.map.
- The types involved
xds_client.transport.tonic.TonicCallCredentials→grpc.metadata.map.MetadataMap
- Direction
- xds_client.transport.tonic uses grpc.metadata.map, so a change to grpc.metadata.map can break xds_client.transport.tonic, while a change to xds_client.transport.tonic can't break grpc.metadata.map.
- Position
- Below the diagonal: xds_client.transport.tonic uses a module listed above it, which is the healthy direction.
39→25 xds_client.transport.tonic uses xds_client.client.config✕
- Connections
- 1 pair of types, where a type in xds_client.transport.tonic uses a type in xds_client.client.config.
- The types involved
xds_client.transport.tonic.TonicTransportBuilder→xds_client.client.config.ServerConfig
- Direction
- xds_client.transport.tonic uses xds_client.client.config, so a change to xds_client.client.config can break xds_client.transport.tonic, while a change to xds_client.transport.tonic can't break xds_client.client.config.
- Position
- Below the diagonal: xds_client.transport.tonic uses a module listed above it, which is the healthy direction.
39→27 xds_client.transport.tonic uses grpc.client.transport✕
- Connections
- 1 pair of types, where a type in xds_client.transport.tonic uses a type in grpc.client.transport.
- The types involved
xds_client.transport.tonic.TonicTransport→grpc.client.transport.Transport
- Direction
- xds_client.transport.tonic uses grpc.client.transport, so a change to grpc.client.transport can break xds_client.transport.tonic, while a change to xds_client.transport.tonic can't break grpc.client.transport.
- Position
- Below the diagonal: xds_client.transport.tonic uses a module listed above it, which is the healthy direction.
39→30 xds_client.transport.tonic uses grpc.client.transport.tonic✕
- Connections
- 1 pair of types, where a type in xds_client.transport.tonic uses a type in grpc.client.transport.tonic.
- The types involved
xds_client.transport.tonic.TonicTransportBuilder→grpc.client.transport.tonic.TransportBuilder
- Direction
- xds_client.transport.tonic uses grpc.client.transport.tonic, so a change to grpc.client.transport.tonic can break xds_client.transport.tonic, while a change to xds_client.transport.tonic can't break grpc.client.transport.tonic.
- Position
- Below the diagonal: xds_client.transport.tonic uses a module listed above it, which is the healthy direction.
39→32 xds_client.transport.tonic uses grpc.client.channel✕
- Connections
- 1 pair of types, where a type in xds_client.transport.tonic uses a type in grpc.client.channel.
- The types involved
xds_client.transport.tonic.TonicTransport→grpc.client.channel.Channel
- Direction
- xds_client.transport.tonic uses grpc.client.channel, so a change to grpc.client.channel can break xds_client.transport.tonic, while a change to xds_client.transport.tonic can't break grpc.client.channel.
- Position
- Below the diagonal: xds_client.transport.tonic uses a module listed above it, which is the healthy direction.
40→2 grpc_protobuf.client uses grpc.client.call_options✕
- Connections
- 1 pair of types, where a type in grpc_protobuf.client uses a type in grpc.client.call_options.
- The types involved
grpc_protobuf.client.CallBuilder→grpc.client.call_options.CallOptions
- Direction
- grpc_protobuf.client uses grpc.client.call_options, so a change to grpc.client.call_options can break grpc_protobuf.client, while a change to grpc_protobuf.client can't break grpc.client.call_options.
- Position
- Below the diagonal: grpc_protobuf.client uses a module listed above it, which is the healthy direction.
40→5 grpc_protobuf.client uses grpc.private✕
- Connections
- 1 pair of types, where a type in grpc_protobuf.client uses a type in grpc.private.
- The types involved
grpc_protobuf.client.CallBuilder→grpc.private.Internal
- Direction
- grpc_protobuf.client uses grpc.private, so a change to grpc.private can break grpc_protobuf.client, while a change to grpc_protobuf.client can't break grpc.private.
- Position
- Below the diagonal: grpc_protobuf.client uses a module listed above it, which is the healthy direction.
40→17 grpc_protobuf.client uses tonic.status✕
- Connections
- 1 pair of types, where a type in grpc_protobuf.client uses a type in tonic.status.
- The types involved
grpc_protobuf.client.GrpcStreamingResponse→tonic.status.Status
- Direction
- grpc_protobuf.client uses tonic.status, so a change to tonic.status can break grpc_protobuf.client, while a change to grpc_protobuf.client can't break tonic.status.
- Position
- Below the diagonal: grpc_protobuf.client uses a module listed above it, which is the healthy direction.
40→23 grpc_protobuf.client uses grpc.core✕
- Connections
- 1 pair of types, where a type in grpc_protobuf.client uses a type in grpc.core.
- The types involved
grpc_protobuf.client.NopRecvMessage→grpc.core.RecvMessage
- Direction
- grpc_protobuf.client uses grpc.core, so a change to grpc.core can break grpc_protobuf.client, while a change to grpc_protobuf.client can't break grpc.core.
- Position
- Below the diagonal: grpc_protobuf.client uses a module listed above it, which is the healthy direction.
40→38 grpc_protobuf.client uses grpc.client.load_balancing.priority✕
- Connections
- 1 pair of types, where a type in grpc_protobuf.client uses a type in grpc.client.load_balancing.priority.
- The types involved
grpc_protobuf.client.CallBuilder→grpc.client.load_balancing.priority.Builder
- Direction
- grpc_protobuf.client uses grpc.client.load_balancing.priority, so a change to grpc.client.load_balancing.priority can break grpc_protobuf.client, while a change to grpc_protobuf.client can't break grpc.client.load_balancing.priority.
- Position
- Below the diagonal: grpc_protobuf.client 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 — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 80 | High / Critical |
| A07:2025 — Authentication Failures | 23 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Immediately resolve the eight leaked secrets, prioritizing REDACTED, REDACTED, and REDACTED, and address the orphaned knowledge in mod.rs to secure the codebase. Establish a draft release or approval gate to prevent bad builds from reaching users, while simultaneously creating the first architecture decision record to document significant design choices. Finally, organize these records in a dedicated folder to ensure architecture documentation remains current and accessible.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. | +10.4 pts | Low | REDACTED Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.3 pts | Low | ADR Quality |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with mod.rs. | +1.7 pts | Low | Knowledge Freshness |
| 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. | +3.2 pts | Medium | Deployment & Rollback |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.1 pts | Medium | Architecture documentation |
| Interpolated log message defeats structured logging | +1.3 pts | Medium | Structured logging |
| Resolve the 14 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2), REDACTED (2). | +1.2 pts | Medium | Secrets (history) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. | +0.6 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| grpc-protobuf-build/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| tonic/src/codec/decode.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| grpc-xds/src/resource/endpoint.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| grpc-benchmark/src/client.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| xds-client/src/client/worker.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| tonic/src/transport/channel/endpoint.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| grpc/src/client/subchannel.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| grpc/src/client/load_balancing/pick_first.rs | 6.5 | Mixed | Explicit Debt: TodoComment |
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
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 63 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 63 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, 314 of 338 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 180 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares Cargo manifests but commits no Cargo.lock, so its dependency graph was closed from the manifests over the crates.io index, and part of it could not be read: no published release of protobuf satisfies `4.36.2-release`. A licence verdict over part of a dependency graph is not a licence verdict. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust, c, cpp is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust, c, cpp is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Cpp, Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was interop::bin::client::main at 20. A further 6 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 Code::from_bytes at 20 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: tonic/src/status.rs (Code::from_bytes at 20), grpc-protobuf/src/status.rs (StatusCodeError::from at 17), grpc/src/status/status_code.rs (StatusCodeError::from at 17). 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 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with interop::bin::client::main (cyclomatic 20), Builder::compile_with_config (cyclomatic 19), Builder::compile_fds_with_config (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was StreamingInner::decode_chunk at 34.
What to do
- Bring the 17 bodies over 15 down to 15 or less in Cognitive Complexity — start with StreamingInner::decode_chunk (cognitive 34), GrpcWebCall::poll_frame (cognitive 29), EndpointsResource::validate (cognitive 24). — 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 17 together lifts Cognitive Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
13 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with mod.rs (2), endpoint.rs, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with worker.rs, map.rs, mod.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with bench.rs, server.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
44 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with client.rs, listener.rs, string_matcher.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with gzip.rs, server.rs, endpoint.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with manual.rs, worker.rs, mod.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
22 production modules (Cargo+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 6 module(s) off the main sequence, with abstractness counted on 19 of the 22 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
5 of 237 classes have LCOM4 above 3.
What to do
- Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (2), tls_stream.rs, manual.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1300 test methods: 1237 unit, 57 integration, 0 BDD, 6 e2e. The Rust suite contributes 1300 `#[test]` function(s) across 180 file(s) declaring at least one; its unit/integration split is Cargo's own — 29 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · REDACTED Scanning
8 secret(s) detected.
What to do
- Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: tonic-xds/src/xds/resource/route_config.rs (3 of 5 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with route_config.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
22 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is grpc-xds/src/resource/endpoint.rs. Counted over 261 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
67 deducted task-comment markers across 98374 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 61 TodoComment finding(s) in Explicit Debt — start with mod.rs (11), pick_first.rs (6), status.u.pb.rs (5). — One of this dimension's main actionable groups (61 warning-level).
- Resolve the 6 FixmeComment finding(s) in Explicit Debt — start with compression.rs (3), status.rs, endpoint.rs. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 19 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 22 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
14 finding(s): 0 critical, 14 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 14 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
80 finding(s): 0 critical, 80 high, 0 medium, 0 low. 77 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `interop/update_binaries.sh` (line 12), `tonic-xds/src/client/circuit_breaking.rs` (line 561), `tonic-xds/src/xds/routing.rs` (line 327) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 77 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 (77 issue-level, 0 of them charged here).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
27 of 261 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is tonic-types/src/richer_error/error_details/mod.rs. Counted over 261 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with mod.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with manual.rs, service.rs, server.rs. — One of this dimension's main actionable groups (26 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: REDACTED↔REDACTED 81%; REDACTED↔REDACTED 71%; REDACTED↔REDACTED 65%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with request.rs, decode.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
C2 · Access Controls
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 9 of 23 project(s) that lack one — worth up to 0.8 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 5/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `codegen`, `grpc`, `grpc-benchmark`, `grpc-rustls`, `xds-client`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
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.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `Server::builder()` (tonic-xds/src/testutil/grpc.rs:120).
What to do
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `trace!` at line 198 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/loadbalancer.rs:198
- `trace!` at line 211 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/loadbalancer.rs:211
- `debug!` at line 268 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/loadbalancer.rs:268
- `debug!` at line 305 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/loadbalancer.rs:305
- `debug!` at line 331 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/loadbalancer.rs:331
- `debug!` at line 339 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/loadbalancer.rs:339
- `warn!` at line 381 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/loadbalancer.rs:381
- `trace!` at line 385 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/loadbalancer.rs:385
- `debug!` at line 209 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/outlier_detection.rs:209
- `debug!` at line 298 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic-xds/src/client/loadbalance/outlier_detection.rs:298
- `debug!` at line 728 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/status.rs:728
- `trace!` at line 67 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/service/grpc_timeout.rs:67
- `warn!` at line 176 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/server/incoming.rs:176
- `warn!` at line 182 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/server/incoming.rs:182
- `trace!` at line 878 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/server/mod.rs:878
- `trace!` at line 905 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/server/mod.rs:905
- `debug!` at line 979 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/server/mod.rs:979
- `debug!` at line 234 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/channel/service/connection.rs:234
- `debug!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/channel/service/reconnect.rs:128
- `debug!` at line 167 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/channel/service/reconnect.rs:167
- `debug!` at line 114 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/transport/channel/service/tls.rs:114
- `debug!` at line 290 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/codec/decode.rs:290
- `trace!` at line 296 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — tonic/src/codec/decode.rs:296
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 69% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 53% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 76% | Adequate — gated by D28, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 91% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~15720 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D14 License Compliance — Crate licences not graded — the lock-less Cargo graph could not be read in full
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 53 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Python, Rust source (service entry point: tonic-xds/src/testutil/grpc.rs:120 (Server::builder()))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — 103 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge tonic-types/src/richer_error/error_details/mod.rs:1
Serious — 168 finding(s)
- TodoComment xds-client/src/runtime/mod.rs:36
- TodoComment xds-client/src/client/worker.rs:72
- TodoComment tonic-xds/src/xds/routing.rs:176
- TodoComment tonic-xds/src/xds/resource/mod.rs:25
- TodoComment tonic-xds/src/xds/resource/route_config.rs:504
- TodoComment tonic-xds/src/xds/resource/route_config.rs:513
- TodoComment tonic-xds/src/client/circuit_breaking.rs:422
- TodoComment tonic-xds/src/client/circuit_breaking.rs:1233
- TodoComment tonic-xds/src/client/loadbalance/channel_state.rs:219
- TodoComment tonic-xds/src/client/loadbalance/cluster_factory.rs:120
- TodoComment tonic-xds/src/client/loadbalance/loadbalancer.rs:44
- TodoComment tonic-xds/src/client/loadbalance/pickers/ring_hash.rs:98
- TodoComment tests/integration_tests/tests/max_message_size.rs:111
- TodoComment tests/integration_tests/tests/status.rs:428
- TodoComment grpc-xds/src/xds_config.rs:32
- TodoComment grpc-xds/src/routing/mod.rs:30
- TodoComment grpc-xds/src/routing/virtual_host.rs:37
- TodoComment grpc-xds/src/routing/route.rs:39
- TodoComment grpc-xds/src/resource/cluster.rs:42
- TodoComment grpc-xds/src/resource/endpoint.rs:55
- TodoComment grpc-xds/src/resource/endpoint.rs:75
- TodoComment grpc-xds/src/resource/mod.rs:31
- TodoComment grpc-xds/src/resource/route.rs:495
- TodoComment grpc-xds/src/load_balancing/cluster_manager.rs:34
- TodoComment grpc-protobuf-build/src/lib.rs:163
- FixmeComment tonic/src/status.rs:406
- FixmeComment tonic/src/transport/channel/endpoint.rs:86
- FixmeComment tonic/src/codec/compression.rs:254
- FixmeComment tonic/src/codec/compression.rs:263
- FixmeComment tonic/src/codec/compression.rs:272
- FixmeComment tonic/src/codec/decode.rs:294
- Duplicated block (6 lines × 2) tonic-build/src/client.rs:265
- Duplicated block (6 lines × 2) grpc-xds/src/resource/listener.rs:154
- Duplicated block (6 lines × 2) grpc-xds/src/resource/string_matcher.rs:215
- Duplicated block (6 lines × 2) grpc/src/client/load_balancing/lazy.rs:173
- Duplicated block (6 lines × 2) grpc/src/client/name_resolution/unix.rs:46
- Duplicated block (6 lines × 2) tonic/src/body.rs:105
- Off the main sequence: tonic-build
- Off the main sequence: tonic-prost
- Off the main sequence: xds-client
- Off the main sequence: tonic
- Off the main sequence: grpc-protobuf-build
- Off the main sequence: tonic-prost-build
- TooManyMethods: ErrorDetails tonic-types/src/richer_error/error_details/mod.rs:41
- TooManyMethods: Endpoint tonic/src/transport/channel/endpoint.rs:56
- TooManyMethods: Builder tonic-prost-build/src/lib.rs:424
- TooManyMethods: MetadataMap tonic/src/metadata/map.rs:61
- TooManyMethods: Server tonic/src/transport/server/mod.rs:114
- Duplicated block (11 lines × 2) grpc/src/codec/compression/gzip.rs:102
- Duplicated block (11 lines × 2) tonic-build/src/server.rs:335
- Duplicated block (11 lines × 2) grpc-xds/src/resource/endpoint.rs:303
- Duplicated block (11 lines × 2) grpc/src/metadata/key.rs:126
- Duplicated block (11 lines × 2) codegen/src/main.rs:51
- Low cohesion: ErrorDetails (LCOM4 10) tonic-types/src/richer_error/error_details/mod.rs:41
- Low cohesion: TlsStream (LCOM4 7) grpc-rustls/src/tls_stream.rs:39
- Low cohesion: TokioRuntime (LCOM4 6) grpc/src/rt/tokio/mod.rs:77
- Low cohesion: Builder (LCOM4 4) tonic-build/src/manual.rs:440
- Low cohesion: XdsChannelConfig (LCOM4 4) tonic-xds/src/client/channel.rs:65
- FileTooLong: client/worker.rs xds-client/src/client/worker.rs
- FileTooLong: metadata/map.rs tonic/src/metadata/map.rs
- FileTooLong: server/mod.rs tonic/src/transport/server/mod.rs
- FileTooLong: REDACTED tonic-prost-build/src/lib.rs
- Duplicated block (12 lines × 2) tonic-build/src/manual.rs:409
- Duplicated block (12 lines × 2) xds-client/src/client/worker.rs:1295
- Duplicated block (12 lines × 2) grpc-rustls/src/client/mod.rs:136
- Duplicated block (9 lines × 2) grpc-rustls/src/server/mod.rs:254
- Duplicated block (9 lines × 2) grpc-protobuf/src/client/server_streaming.rs:94
- Duplicated block (9 lines × 2) tonic-types/src/richer_error/std_messages/bad_request.rs:110
- Duplicated block (8 lines × 2) tonic-build/src/client.rs:56
- Duplicated block (8 lines × 2) grpc-protobuf/src/client/bidi.rs:91
- Duplicated block (8 lines × 2) tonic-types/src/richer_error/std_messages/bad_request.rs:125
- Builder::compile_with_config (cyclomatic 19) tonic-prost-build/src/lib.rs:753
- Builder::compile_fds_with_config (cyclomatic 18) tonic-prost-build/src/lib.rs:875
- grpc_benchmark::client::blocking_streaming (cognitive 22) grpc-benchmark/src/client.rs:384
- grpc_benchmark::client::blocking_unary (cognitive 20) grpc-benchmark/src/client.rs:338
- Builder::compile_with_config (cognitive 19) tonic-prost-build/src/lib.rs:753
- Builder::compile_fds_with_config (cognitive 18) tonic-prost-build/src/lib.rs:875
- FunctionTooLong: grpc_benchmark::bin::bench::main grpc-benchmark/src/bin/bench.rs:135
- FunctionTooLong: tonic_build::server::generate_internal tonic-build/src/server.rs:37
- Change coupling: request.rs ↔ response.rs tonic/src/request.rs:1
- Change coupling: decode.rs ↔ encode.rs tonic/src/codec/decode.rs:1
- Duplicated block (26 lines × 2) grpc/src/metadata/map.rs:1056
- Duplicated block (26 lines × 2) tonic/src/transport/channel/endpoint.rs:109
- Duplicated block (20 lines × 2) grpc-protobuf/src/status.rs:137
- Duplicated block (20 lines × 2) tonic-build/src/server.rs:532
- Duplicated block (7 lines × 2) grpc/src/client/subchannel.rs:127
- Duplicated block (7 lines × 2) interop/src/bin/client.rs:58
- interop::bin::client::main (cyclomatic 20) interop/src/bin/client.rs:81
- GrpcWebCall::poll_frame (cyclomatic 18) tonic-web/src/call.rs:282
- TonicBuildMethod::request_response_name (cyclomatic 17) tonic-prost-build/src/lib.rs:228
- CodeGen::compile (cyclomatic 16) grpc-protobuf-build/src/lib.rs:322
- TlsConnector::new (cyclomatic 16) tonic/src/transport/channel/service/tls.rs:57
- Repeated repair: tonic-xds/src/xds/resource/route_config.rs tonic-xds/src/xds/resource/route_config.rs:437
- StreamingInner::decode_chunk (cognitive 34) tonic/src/codec/decode.rs:172
- GrpcWebCall::poll_frame (cognitive 29) tonic-web/src/call.rs:282
- EndpointsResource::validate (cognitive 24) grpc-xds/src/resource/endpoint.rs:133
- CodeGen::compile (cognitive 21) grpc-protobuf-build/src/lib.rs:322
- TlsConnector::new (cognitive 21) tonic/src/transport/channel/service/tls.rs:57
- grpc::client::transport::http_connect::do_connect_handshake (cognitive 20) grpc/src/client/transport/http_connect/mod.rs:54
- TonicBuildMethod::request_response_name (cognitive 20) tonic-prost-build/src/lib.rs:228
- Reconnect::poll_ready (cognitive 19) tonic/src/transport/channel/service/reconnect.rs:86
- TransportContext::run (cognitive 19) xds-client/src/client/worker.rs:1458
- grpc_xds::resource::route::validate_route_action (cognitive 18) grpc-xds/src/resource/route.rs:436
- interop::bin::client::main (cognitive 18) interop/src/bin/client.rs:81
- UnencodedHeaderValue::fmt (cognitive 17) grpc/src/metadata/value.rs:96
- BenchmarkClient::start (cognitive 16) grpc-benchmark/src/client.rs:73
- ClassTooLong: AdsWorker xds-client/src/client/worker.rs:628
- MethodTooLong: BenchmarkClient.start grpc-benchmark/src/client.rs:73
- Change coupling clique: REDACTED, REDACTED, REDACTED, REDACTED, REDACTED tonic-build/src/lib.rs
- REDACTED
- Near-duplicate member family (4 members, 29 shared lines) tonic-build/src/server.rs:470
- Edited copy of a member (70 corresponding lines) tonic-reflection/src/server/v1.rs:53
- Edited copy of a member (35 corresponding lines) grpc-protobuf/src/server/server_streaming.rs:91
- Members sharing a duplicated core (4 members, 50+ identical tokens) tonic-build/src/client.rs:251
- Duplicated block (43 lines × 2) tonic-prost-build/src/lib.rs:782
- Duplicated block (31 lines × 2) grpc-protobuf/src/server/server_streaming.rs:94
- Duplicated block (29 lines × 2) tonic-prost-build/src/lib.rs:834
- Duplicated block (22–23 lines × 2) grpc-benchmark/src/client.rs:350
- Duplicated block (20 lines × 4) tonic-build/src/server.rs:492
- Duplicated block (18 lines × 2) tonic/src/transport/server/incoming.rs:196
- Duplicated block (16 lines × 2) tonic-reflection/src/server/v1.rs:107
- Duplicated block (11–15 lines × 2) grpc-protobuf/src/server/client_streaming.rs:96
- Duplicated block (13–14 lines × 2) grpc-benchmark/src/client.rs:247
- Duplicated block (14 lines × 2) tonic/src/server/grpc.rs:270
- Duplicated block (13 lines × 2) tonic-reflection/src/server/v1.rs:54
- Duplicated block (10 lines × 2) tonic/src/status.rs:876
- Duplicated block (9 lines × 4) tonic-build/src/server.rs:477
- Duplicated block (8 lines × 4) tonic-build/src/client.rs:254
- Duplicated block (5 lines × 3) tonic-build/src/server.rs:471
- Duplicated block (5 lines × 2) tonic-build/src/client.rs:327
- Duplicated block (8 lines × 10) tonic-types/src/richer_error/std_messages/bad_request.rs:142
- Duplicated block (6 lines × 10) tonic-types/src/richer_error/std_messages/bad_request.rs:160
Minor — 67 finding(s)
- Orphaned file tonic-build/src/manual.rs:1
- Orphaned file tonic-web/src/service.rs:1
- Orphaned file tonic-health/src/server.rs:1
- Orphaned file tonic/src/service/interceptor.rs:1
- Orphaned file tonic/src/transport/service/grpc_timeout.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/quota_failure.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/prec_failure.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/help.rs:1
- Orphaned file tonic-reflection/src/server/v1alpha.rs:1
- Orphaned file tonic-reflection/src/server/v1.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/retry_info.rs:1
- Orphaned file tonic/src/transport/channel/service/user_agent.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/error_info.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/resource_info.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/loc_message.rs:1
- Orphaned file tonic/src/service/recover_error.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/request_info.rs:1
- Orphaned file tonic-types/src/richer_error/std_messages/debug_info.rs:1
- Orphaned file tonic/src/codec/buffer.rs:1
- Orphaned file tonic/benches-disabled/benchmarks/request_response_diverse_types.rs:1
- Orphaned file tonic/src/transport/server/service/tls.rs:1
- Orphaned file tonic-types/src/richer_error/error_details/vec.rs:1
- Orphaned file tonic/src/service/layered.rs:1
- Orphaned file tonic/src/transport/channel/uds_connector.rs:1
- Orphaned file tonic/src/transport/channel/service/io.rs:1
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/loadbalancer.rs:198
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/loadbalancer.rs:211
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/loadbalancer.rs:268
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/loadbalancer.rs:305
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/loadbalancer.rs:331
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/loadbalancer.rs:339
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/loadbalancer.rs:381
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/loadbalancer.rs:385
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/outlier_detection.rs:209
- Interpolated log message defeats structured logging tonic-xds/src/client/loadbalance/outlier_detection.rs:298
- Interpolated log message defeats structured logging tonic/src/status.rs:728
- Interpolated log message defeats structured logging tonic/src/transport/service/grpc_timeout.rs:67
- Interpolated log message defeats structured logging tonic/src/transport/server/incoming.rs:176
- Interpolated log message defeats structured logging tonic/src/transport/server/incoming.rs:182
- Interpolated log message defeats structured logging tonic/src/transport/server/mod.rs:878
- Interpolated log message defeats structured logging tonic/src/transport/server/mod.rs:905
- Interpolated log message defeats structured logging tonic/src/transport/server/mod.rs:979
- Interpolated log message defeats structured logging tonic/src/transport/channel/service/connection.rs:234
- Interpolated log message defeats structured logging tonic/src/transport/channel/service/reconnect.rs:128
- Interpolated log message defeats structured logging tonic/src/transport/channel/service/reconnect.rs:167
- Interpolated log message defeats structured logging tonic/src/transport/channel/service/tls.rs:114
- Interpolated log message defeats structured logging tonic/src/codec/decode.rs:290
- Interpolated log message defeats structured logging tonic/src/codec/decode.rs:296
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No release approval gate
- No security response headers detected
- Duplicated predicate grpc-xds/src/resource/cluster.rs:130
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e05f4573355d432f84f5e2385f419f2a/history.json --exit-code 0 --source . | 11 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e05f4573355d432f84f5e2385f419f2a/tree.json --exit-code 0 --source . | 8 | 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/watchdog-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 --exclude grpc/src/generated --exclude grpc-rustls/tests/generated --exclude tonic-health/src/generated --exclude tonic-reflection/src/generated --exclude tonic-types/src/generated . | 80 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| 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 | — |
| 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |