Executive summary
raystack/raccoon is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 59 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Code Health, at 53, is the weakest lens and counts most in the score. The best first steps are adding type checking and declaring which values may be missing, each worth about 5 points. Raising Code Health to 67 would lift the score to about 64.
Forty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seventeen known security holes in the packages the code depends on can be used by attackers, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. The three unsafe settings in infrastructure or container files need changing to safe values. The password or key in the code's history needs replacing, with the old one switched off.
The product code is 5,083 lines, about €10,000 to rebuild.
If Code Health rose from 53 to 67, the lowest score rated Strong, the score would rise from 59 to about 64.
Fixed since the last survey: 1 finding
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €10,000 · Estimate
| Cost to rebuild | €3,400 to €17,000, for 57 to 181 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,083 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: which parts of the code depend on which
| uses → | 1 clients.js.lib.rest | 2 clients.python.raccoon_client.client | 3 clients.python.raccoon_client.serde.enum | 4 clients.python.raccoon_client.serde.serde | 5 clients.python.raccoon_client.serde.wire | 6 github.com/raystack/raccoon/clients/go | 7 github.com/raystack/raccoon/clients/go/log | 8 github.com/raystack/raccoon/clients/go/serializer | 9 github.com/raystack/raccoon/clients/go/wire | 10 github.com/raystack/raccoon/config | 11 github.com/raystack/raccoon/core/identification | 12 github.com/raystack/raccoon/core/serde | 13 github.com/raystack/raccoon/pkg/clock | 14 github.com/raystack/raccoon/pkg/metrics | 15 io.odpf.raccoon.model | 16 io.odpf.raccoon.serializer | 17 io.odpf.raccoon.wire | 18 clients.python.raccoon_client.rest.option | 19 clients.python.raccoon_client.serde | 20 clients.python.raccoon_client.serde.json_serde | 21 clients.python.raccoon_client.serde.protobuf_serde | 22 github.com/raystack/raccoon/clients/go/grpc | 23 github.com/raystack/raccoon/clients/go/rest | 24 github.com/raystack/raccoon/clients/go/ws | 25 github.com/raystack/raccoon/cmd | 26 github.com/raystack/raccoon/core/collector | 27 github.com/raystack/raccoon/server/rest/websocket/connection | 28 io.odpf.raccoon.client | 29 clients.python.raccoon_client.rest.client | 30 github.com/raystack/raccoon/core/worker | 31 github.com/raystack/raccoon/server | 32 github.com/raystack/raccoon/server/rest/websocket | 33 github.com/raystack/raccoon/app | 34 github.com/raystack/raccoon/server/grpc | 35 github.com/raystack/raccoon/server/pprof | 36 github.com/raystack/raccoon/server/rest | 37 github.com/raystack/raccoon/publisher/kafka | 38 github.com/raystack/raccoon/publisher/kinesis | 39 github.com/raystack/raccoon/publisher/log | 40 github.com/raystack/raccoon/publisher/pubsub |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 clients.js.lib.rest | ||||||||||||||||||||||||||||||||||||||||
| 2 clients.python.raccoon_client.client | ||||||||||||||||||||||||||||||||||||||||
| 3 clients.python.raccoon_client.serde.enum | ||||||||||||||||||||||||||||||||||||||||
| 4 clients.python.raccoon_client.serde.serde | ||||||||||||||||||||||||||||||||||||||||
| 5 clients.python.raccoon_client.serde.wire | ||||||||||||||||||||||||||||||||||||||||
| 6 github.com/raystack/raccoon/clients/go | ||||||||||||||||||||||||||||||||||||||||
| 7 github.com/raystack/raccoon/clients/go/log | ||||||||||||||||||||||||||||||||||||||||
| 8 github.com/raystack/raccoon/clients/go/serializer | ||||||||||||||||||||||||||||||||||||||||
| 9 github.com/raystack/raccoon/clients/go/wire | ||||||||||||||||||||||||||||||||||||||||
| 10 github.com/raystack/raccoon/config | ||||||||||||||||||||||||||||||||||||||||
| 11 github.com/raystack/raccoon/core/identification | ||||||||||||||||||||||||||||||||||||||||
| 12 github.com/raystack/raccoon/core/serde | ||||||||||||||||||||||||||||||||||||||||
| 13 github.com/raystack/raccoon/pkg/clock | ||||||||||||||||||||||||||||||||||||||||
| 14 github.com/raystack/raccoon/pkg/metrics | ||||||||||||||||||||||||||||||||||||||||
| 15 io.odpf.raccoon.model | ||||||||||||||||||||||||||||||||||||||||
| 16 io.odpf.raccoon.serializer | ||||||||||||||||||||||||||||||||||||||||
| 17 io.odpf.raccoon.wire | ||||||||||||||||||||||||||||||||||||||||
| 18 clients.python.raccoon_client.rest.option | 4 | |||||||||||||||||||||||||||||||||||||||
| 19 clients.python.raccoon_client.serde | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 clients.python.raccoon_client.serde.json_serde | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 clients.python.raccoon_client.serde.protobuf_serde | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 github.com/raystack/raccoon/clients/go/grpc | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 github.com/raystack/raccoon/clients/go/rest | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 github.com/raystack/raccoon/clients/go/ws | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 github.com/raystack/raccoon/cmd | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 github.com/raystack/raccoon/core/collector | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 github.com/raystack/raccoon/server/rest/websocket/connection | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 io.odpf.raccoon.client | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 clients.python.raccoon_client.rest.client | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 30 github.com/raystack/raccoon/core/worker | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 github.com/raystack/raccoon/server | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 github.com/raystack/raccoon/server/rest/websocket | 5 | 3 | 5 | |||||||||||||||||||||||||||||||||||||
| 33 github.com/raystack/raccoon/app | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 github.com/raystack/raccoon/server/grpc | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 github.com/raystack/raccoon/server/pprof | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 github.com/raystack/raccoon/server/rest | 1 | 4 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 github.com/raystack/raccoon/publisher/kafka | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 github.com/raystack/raccoon/publisher/kinesis | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 github.com/raystack/raccoon/publisher/log | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 github.com/raystack/raccoon/publisher/pubsub | 1 | 1 |
18→3 clients.python.raccoon_client.rest.option uses clients.python.raccoon_client.serde.enum✕
- Connections
- 4 pairs of types, where a type in clients.python.raccoon_client.rest.option uses a type in clients.python.raccoon_client.serde.enum.
- The types involved
clients.python.raccoon_client.rest.option.RestClientConfig→clients.python.raccoon_client.serde.enum.Serialiserclients.python.raccoon_client.rest.option.RestClientConfig→clients.python.raccoon_client.serde.enum.WireTypeclients.python.raccoon_client.rest.option.RestClientConfigBuilder→clients.python.raccoon_client.serde.enum.Serialiserclients.python.raccoon_client.rest.option.RestClientConfigBuilder→clients.python.raccoon_client.serde.enum.WireType
- Direction
- clients.python.raccoon_client.rest.option uses clients.python.raccoon_client.serde.enum, so a change to clients.python.raccoon_client.serde.enum can break clients.python.raccoon_client.rest.option, while a change to clients.python.raccoon_client.rest.option can't break clients.python.raccoon_client.serde.enum.
- Position
- Below the diagonal: clients.python.raccoon_client.rest.option uses a module listed above it, which is the healthy direction.
19→4 clients.python.raccoon_client.serde uses clients.python.raccoon_client.serde.serde✕
- Connections
- 1 pair of types, where a type in clients.python.raccoon_client.serde uses a type in clients.python.raccoon_client.serde.serde.
- The types involved
clients.python.raccoon_client.serde.util→clients.python.raccoon_client.serde.serde.Serde
- Direction
- clients.python.raccoon_client.serde uses clients.python.raccoon_client.serde.serde, so a change to clients.python.raccoon_client.serde.serde can break clients.python.raccoon_client.serde, while a change to clients.python.raccoon_client.serde can't break clients.python.raccoon_client.serde.serde.
- Position
- Below the diagonal: clients.python.raccoon_client.serde uses a module listed above it, which is the healthy direction.
19→5 clients.python.raccoon_client.serde uses clients.python.raccoon_client.serde.wire✕
- Connections
- 1 pair of types, where a type in clients.python.raccoon_client.serde uses a type in clients.python.raccoon_client.serde.wire.
- The types involved
clients.python.raccoon_client.serde.util→clients.python.raccoon_client.serde.wire.Wire
- Direction
- clients.python.raccoon_client.serde uses clients.python.raccoon_client.serde.wire, so a change to clients.python.raccoon_client.serde.wire can break clients.python.raccoon_client.serde, while a change to clients.python.raccoon_client.serde can't break clients.python.raccoon_client.serde.wire.
- Position
- Below the diagonal: clients.python.raccoon_client.serde uses a module listed above it, which is the healthy direction.
20→4 clients.python.raccoon_client.serde.json_serde uses clients.python.raccoon_client.serde.serde✕
- Connections
- 1 pair of types, where a type in clients.python.raccoon_client.serde.json_serde uses a type in clients.python.raccoon_client.serde.serde.
- The types involved
clients.python.raccoon_client.serde.json_serde.JsonSerde→clients.python.raccoon_client.serde.serde.Serde
- Direction
- clients.python.raccoon_client.serde.json_serde uses clients.python.raccoon_client.serde.serde, so a change to clients.python.raccoon_client.serde.serde can break clients.python.raccoon_client.serde.json_serde, while a change to clients.python.raccoon_client.serde.json_serde can't break clients.python.raccoon_client.serde.serde.
- Position
- Below the diagonal: clients.python.raccoon_client.serde.json_serde uses a module listed above it, which is the healthy direction.
20→5 clients.python.raccoon_client.serde.json_serde uses clients.python.raccoon_client.serde.wire✕
- Connections
- 1 pair of types, where a type in clients.python.raccoon_client.serde.json_serde uses a type in clients.python.raccoon_client.serde.wire.
- The types involved
clients.python.raccoon_client.serde.json_serde.JsonSerde→clients.python.raccoon_client.serde.wire.Wire
- Direction
- clients.python.raccoon_client.serde.json_serde uses clients.python.raccoon_client.serde.wire, so a change to clients.python.raccoon_client.serde.wire can break clients.python.raccoon_client.serde.json_serde, while a change to clients.python.raccoon_client.serde.json_serde can't break clients.python.raccoon_client.serde.wire.
- Position
- Below the diagonal: clients.python.raccoon_client.serde.json_serde uses a module listed above it, which is the healthy direction.
21→4 clients.python.raccoon_client.serde.protobuf_serde uses clients.python.raccoon_client.serde.serde✕
- Connections
- 1 pair of types, where a type in clients.python.raccoon_client.serde.protobuf_serde uses a type in clients.python.raccoon_client.serde.serde.
- The types involved
clients.python.raccoon_client.serde.protobuf_serde.ProtobufSerde→clients.python.raccoon_client.serde.serde.Serde
- Direction
- clients.python.raccoon_client.serde.protobuf_serde uses clients.python.raccoon_client.serde.serde, so a change to clients.python.raccoon_client.serde.serde can break clients.python.raccoon_client.serde.protobuf_serde, while a change to clients.python.raccoon_client.serde.protobuf_serde can't break clients.python.raccoon_client.serde.serde.
- Position
- Below the diagonal: clients.python.raccoon_client.serde.protobuf_serde uses a module listed above it, which is the healthy direction.
21→5 clients.python.raccoon_client.serde.protobuf_serde uses clients.python.raccoon_client.serde.wire✕
- Connections
- 1 pair of types, where a type in clients.python.raccoon_client.serde.protobuf_serde uses a type in clients.python.raccoon_client.serde.wire.
- The types involved
clients.python.raccoon_client.serde.protobuf_serde.ProtobufSerde→clients.python.raccoon_client.serde.wire.Wire
- Direction
- clients.python.raccoon_client.serde.protobuf_serde uses clients.python.raccoon_client.serde.wire, so a change to clients.python.raccoon_client.serde.wire can break clients.python.raccoon_client.serde.protobuf_serde, while a change to clients.python.raccoon_client.serde.protobuf_serde can't break clients.python.raccoon_client.serde.wire.
- Position
- Below the diagonal: clients.python.raccoon_client.serde.protobuf_serde uses a module listed above it, which is the healthy direction.
22→6 github.com/raystack/raccoon/clients/go/grpc uses github.com/raystack/raccoon/clients/go✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/clients/go/grpc uses a type in github.com/raystack/raccoon/clients/go.
- The types involved
github.com/raystack/raccoon/clients/go/grpc.Grpc→github.com/raystack/raccoon/clients/go.Event
- Direction
- github.com/raystack/raccoon/clients/go/grpc uses github.com/raystack/raccoon/clients/go, so a change to github.com/raystack/raccoon/clients/go can break github.com/raystack/raccoon/clients/go/grpc, while a change to github.com/raystack/raccoon/clients/go/grpc can't break github.com/raystack/raccoon/clients/go.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/grpc uses a module listed above it, which is the healthy direction.
22→7 github.com/raystack/raccoon/clients/go/grpc uses github.com/raystack/raccoon/clients/go/log✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/clients/go/grpc uses a type in github.com/raystack/raccoon/clients/go/log.
- The types involved
github.com/raystack/raccoon/clients/go/grpc.Grpc→github.com/raystack/raccoon/clients/go/log.Loggergithub.com/raystack/raccoon/clients/go/grpc.grpc→github.com/raystack/raccoon/clients/go/log.Logger
- Direction
- github.com/raystack/raccoon/clients/go/grpc uses github.com/raystack/raccoon/clients/go/log, so a change to github.com/raystack/raccoon/clients/go/log can break github.com/raystack/raccoon/clients/go/grpc, while a change to github.com/raystack/raccoon/clients/go/grpc can't break github.com/raystack/raccoon/clients/go/log.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/grpc uses a module listed above it, which is the healthy direction.
22→8 github.com/raystack/raccoon/clients/go/grpc uses github.com/raystack/raccoon/clients/go/serializer✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/clients/go/grpc uses a type in github.com/raystack/raccoon/clients/go/serializer.
- The types involved
github.com/raystack/raccoon/clients/go/grpc.Grpc→github.com/raystack/raccoon/clients/go/serializer.SerializerFuncgithub.com/raystack/raccoon/clients/go/grpc.grpc→github.com/raystack/raccoon/clients/go/serializer.SerializerFunc
- Direction
- github.com/raystack/raccoon/clients/go/grpc uses github.com/raystack/raccoon/clients/go/serializer, so a change to github.com/raystack/raccoon/clients/go/serializer can break github.com/raystack/raccoon/clients/go/grpc, while a change to github.com/raystack/raccoon/clients/go/grpc can't break github.com/raystack/raccoon/clients/go/serializer.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/grpc uses a module listed above it, which is the healthy direction.
23→6 github.com/raystack/raccoon/clients/go/rest uses github.com/raystack/raccoon/clients/go✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/clients/go/rest uses a type in github.com/raystack/raccoon/clients/go.
- The types involved
github.com/raystack/raccoon/clients/go/rest.Rest→github.com/raystack/raccoon/clients/go.Event
- Direction
- github.com/raystack/raccoon/clients/go/rest uses github.com/raystack/raccoon/clients/go, so a change to github.com/raystack/raccoon/clients/go can break github.com/raystack/raccoon/clients/go/rest, while a change to github.com/raystack/raccoon/clients/go/rest can't break github.com/raystack/raccoon/clients/go.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/rest uses a module listed above it, which is the healthy direction.
23→7 github.com/raystack/raccoon/clients/go/rest uses github.com/raystack/raccoon/clients/go/log✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/clients/go/rest uses a type in github.com/raystack/raccoon/clients/go/log.
- The types involved
github.com/raystack/raccoon/clients/go/rest.Rest→github.com/raystack/raccoon/clients/go/log.Loggergithub.com/raystack/raccoon/clients/go/rest.rest→github.com/raystack/raccoon/clients/go/log.Logger
- Direction
- github.com/raystack/raccoon/clients/go/rest uses github.com/raystack/raccoon/clients/go/log, so a change to github.com/raystack/raccoon/clients/go/log can break github.com/raystack/raccoon/clients/go/rest, while a change to github.com/raystack/raccoon/clients/go/rest can't break github.com/raystack/raccoon/clients/go/log.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/rest uses a module listed above it, which is the healthy direction.
23→8 github.com/raystack/raccoon/clients/go/rest uses github.com/raystack/raccoon/clients/go/serializer✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/clients/go/rest uses a type in github.com/raystack/raccoon/clients/go/serializer.
- The types involved
github.com/raystack/raccoon/clients/go/rest.Rest→github.com/raystack/raccoon/clients/go/serializer.SerializerFuncgithub.com/raystack/raccoon/clients/go/rest.rest→github.com/raystack/raccoon/clients/go/serializer.SerializerFunc
- Direction
- github.com/raystack/raccoon/clients/go/rest uses github.com/raystack/raccoon/clients/go/serializer, so a change to github.com/raystack/raccoon/clients/go/serializer can break github.com/raystack/raccoon/clients/go/rest, while a change to github.com/raystack/raccoon/clients/go/rest can't break github.com/raystack/raccoon/clients/go/serializer.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/rest uses a module listed above it, which is the healthy direction.
23→9 github.com/raystack/raccoon/clients/go/rest uses github.com/raystack/raccoon/clients/go/wire✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/clients/go/rest uses a type in github.com/raystack/raccoon/clients/go/wire.
- The types involved
github.com/raystack/raccoon/clients/go/rest.Rest→github.com/raystack/raccoon/clients/go/wire.WireMarshaler
- Direction
- github.com/raystack/raccoon/clients/go/rest uses github.com/raystack/raccoon/clients/go/wire, so a change to github.com/raystack/raccoon/clients/go/wire can break github.com/raystack/raccoon/clients/go/rest, while a change to github.com/raystack/raccoon/clients/go/rest can't break github.com/raystack/raccoon/clients/go/wire.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/rest uses a module listed above it, which is the healthy direction.
24→6 github.com/raystack/raccoon/clients/go/ws uses github.com/raystack/raccoon/clients/go✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/clients/go/ws uses a type in github.com/raystack/raccoon/clients/go.
- The types involved
github.com/raystack/raccoon/clients/go/ws.WS→github.com/raystack/raccoon/clients/go.Eventgithub.com/raystack/raccoon/clients/go/ws.WS→github.com/raystack/raccoon/clients/go.Response
- Direction
- github.com/raystack/raccoon/clients/go/ws uses github.com/raystack/raccoon/clients/go, so a change to github.com/raystack/raccoon/clients/go can break github.com/raystack/raccoon/clients/go/ws, while a change to github.com/raystack/raccoon/clients/go/ws can't break github.com/raystack/raccoon/clients/go.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/ws uses a module listed above it, which is the healthy direction.
24→7 github.com/raystack/raccoon/clients/go/ws uses github.com/raystack/raccoon/clients/go/log✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/clients/go/ws uses a type in github.com/raystack/raccoon/clients/go/log.
- The types involved
github.com/raystack/raccoon/clients/go/ws.WS→github.com/raystack/raccoon/clients/go/log.Loggergithub.com/raystack/raccoon/clients/go/ws.ws→github.com/raystack/raccoon/clients/go/log.Logger
- Direction
- github.com/raystack/raccoon/clients/go/ws uses github.com/raystack/raccoon/clients/go/log, so a change to github.com/raystack/raccoon/clients/go/log can break github.com/raystack/raccoon/clients/go/ws, while a change to github.com/raystack/raccoon/clients/go/ws can't break github.com/raystack/raccoon/clients/go/log.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/ws uses a module listed above it, which is the healthy direction.
24→8 github.com/raystack/raccoon/clients/go/ws uses github.com/raystack/raccoon/clients/go/serializer✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/clients/go/ws uses a type in github.com/raystack/raccoon/clients/go/serializer.
- The types involved
github.com/raystack/raccoon/clients/go/ws.WS→github.com/raystack/raccoon/clients/go/serializer.SerializerFuncgithub.com/raystack/raccoon/clients/go/ws.ws→github.com/raystack/raccoon/clients/go/serializer.SerializerFunc
- Direction
- github.com/raystack/raccoon/clients/go/ws uses github.com/raystack/raccoon/clients/go/serializer, so a change to github.com/raystack/raccoon/clients/go/serializer can break github.com/raystack/raccoon/clients/go/ws, while a change to github.com/raystack/raccoon/clients/go/ws can't break github.com/raystack/raccoon/clients/go/serializer.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/ws uses a module listed above it, which is the healthy direction.
24→9 github.com/raystack/raccoon/clients/go/ws uses github.com/raystack/raccoon/clients/go/wire✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/clients/go/ws uses a type in github.com/raystack/raccoon/clients/go/wire.
- The types involved
github.com/raystack/raccoon/clients/go/ws.WS→github.com/raystack/raccoon/clients/go/wire.WireMarshaler
- Direction
- github.com/raystack/raccoon/clients/go/ws uses github.com/raystack/raccoon/clients/go/wire, so a change to github.com/raystack/raccoon/clients/go/wire can break github.com/raystack/raccoon/clients/go/ws, while a change to github.com/raystack/raccoon/clients/go/ws can't break github.com/raystack/raccoon/clients/go/wire.
- Position
- Below the diagonal: github.com/raystack/raccoon/clients/go/ws uses a module listed above it, which is the healthy direction.
25→10 github.com/raystack/raccoon/cmd uses github.com/raystack/raccoon/config✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/cmd uses a type in github.com/raystack/raccoon/config.
- The types involved
github.com/raystack/raccoon/cmd.ackTypeFlag→github.com/raystack/raccoon/config.AckType
- Direction
- github.com/raystack/raccoon/cmd uses github.com/raystack/raccoon/config, so a change to github.com/raystack/raccoon/config can break github.com/raystack/raccoon/cmd, while a change to github.com/raystack/raccoon/cmd can't break github.com/raystack/raccoon/config.
- Position
- Below the diagonal: github.com/raystack/raccoon/cmd uses a module listed above it, which is the healthy direction.
26→11 github.com/raystack/raccoon/core/collector uses github.com/raystack/raccoon/core/identification✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/core/collector uses a type in github.com/raystack/raccoon/core/identification.
- The types involved
github.com/raystack/raccoon/core/collector.CollectRequest→github.com/raystack/raccoon/core/identification.Identifier
- Direction
- github.com/raystack/raccoon/core/collector uses github.com/raystack/raccoon/core/identification, so a change to github.com/raystack/raccoon/core/identification can break github.com/raystack/raccoon/core/collector, while a change to github.com/raystack/raccoon/core/collector can't break github.com/raystack/raccoon/core/identification.
- Position
- Below the diagonal: github.com/raystack/raccoon/core/collector uses a module listed above it, which is the healthy direction.
26→13 github.com/raystack/raccoon/core/collector uses github.com/raystack/raccoon/pkg/clock✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/core/collector uses a type in github.com/raystack/raccoon/pkg/clock.
- The types involved
github.com/raystack/raccoon/core/collector.ChannelCollector→github.com/raystack/raccoon/pkg/clock.Clock
- Direction
- github.com/raystack/raccoon/core/collector uses github.com/raystack/raccoon/pkg/clock, so a change to github.com/raystack/raccoon/pkg/clock can break github.com/raystack/raccoon/core/collector, while a change to github.com/raystack/raccoon/core/collector can't break github.com/raystack/raccoon/pkg/clock.
- Position
- Below the diagonal: github.com/raystack/raccoon/core/collector uses a module listed above it, which is the healthy direction.
27→11 github.com/raystack/raccoon/server/rest/websocket/connection uses github.com/raystack/raccoon/core/identification✕
- Connections
- 3 pairs of types, where a type in github.com/raystack/raccoon/server/rest/websocket/connection uses a type in github.com/raystack/raccoon/core/identification.
- The types involved
github.com/raystack/raccoon/server/rest/websocket/connection.Conn→github.com/raystack/raccoon/core/identification.Identifiergithub.com/raystack/raccoon/server/rest/websocket/connection.Table→github.com/raystack/raccoon/core/identification.Identifiergithub.com/raystack/raccoon/server/rest/websocket/connection.Upgrader→github.com/raystack/raccoon/core/identification.Identifier
- Direction
- github.com/raystack/raccoon/server/rest/websocket/connection uses github.com/raystack/raccoon/core/identification, so a change to github.com/raystack/raccoon/core/identification can break github.com/raystack/raccoon/server/rest/websocket/connection, while a change to github.com/raystack/raccoon/server/rest/websocket/connection can't break github.com/raystack/raccoon/core/identification.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest/websocket/connection uses a module listed above it, which is the healthy direction.
28→15 io.odpf.raccoon.client uses io.odpf.raccoon.model✕
- Connections
- 4 pairs of types, where a type in io.odpf.raccoon.client uses a type in io.odpf.raccoon.model.
- The types involved
io.odpf.raccoon.client.RaccoonClient→io.odpf.raccoon.model.Eventio.odpf.raccoon.client.RaccoonClient→io.odpf.raccoon.model.Responseio.odpf.raccoon.client.RestClient→io.odpf.raccoon.model.Eventio.odpf.raccoon.client.RestClient→io.odpf.raccoon.model.Response
- Direction
- io.odpf.raccoon.client uses io.odpf.raccoon.model, so a change to io.odpf.raccoon.model can break io.odpf.raccoon.client, while a change to io.odpf.raccoon.client can't break io.odpf.raccoon.model.
- Position
- Below the diagonal: io.odpf.raccoon.client uses a module listed above it, which is the healthy direction.
28→16 io.odpf.raccoon.client uses io.odpf.raccoon.serializer✕
- Connections
- 1 pair of types, where a type in io.odpf.raccoon.client uses a type in io.odpf.raccoon.serializer.
- The types involved
io.odpf.raccoon.client.RestConfig→io.odpf.raccoon.serializer.Serializer
- Direction
- io.odpf.raccoon.client uses io.odpf.raccoon.serializer, so a change to io.odpf.raccoon.serializer can break io.odpf.raccoon.client, while a change to io.odpf.raccoon.client can't break io.odpf.raccoon.serializer.
- Position
- Below the diagonal: io.odpf.raccoon.client uses a module listed above it, which is the healthy direction.
28→17 io.odpf.raccoon.client uses io.odpf.raccoon.wire✕
- Connections
- 1 pair of types, where a type in io.odpf.raccoon.client uses a type in io.odpf.raccoon.wire.
- The types involved
io.odpf.raccoon.client.RestConfig→io.odpf.raccoon.wire.WireMarshaler
- Direction
- io.odpf.raccoon.client uses io.odpf.raccoon.wire, so a change to io.odpf.raccoon.wire can break io.odpf.raccoon.client, while a change to io.odpf.raccoon.client can't break io.odpf.raccoon.wire.
- Position
- Below the diagonal: io.odpf.raccoon.client uses a module listed above it, which is the healthy direction.
29→2 clients.python.raccoon_client.rest.client uses clients.python.raccoon_client.client✕
- Connections
- 2 pairs of types, where a type in clients.python.raccoon_client.rest.client uses a type in clients.python.raccoon_client.client.
- The types involved
clients.python.raccoon_client.rest.client.RestClient→clients.python.raccoon_client.client.Clientclients.python.raccoon_client.rest.client.RestClient→clients.python.raccoon_client.client.Event
- Direction
- clients.python.raccoon_client.rest.client uses clients.python.raccoon_client.client, so a change to clients.python.raccoon_client.client can break clients.python.raccoon_client.rest.client, while a change to clients.python.raccoon_client.rest.client can't break clients.python.raccoon_client.client.
- Position
- Below the diagonal: clients.python.raccoon_client.rest.client uses a module listed above it, which is the healthy direction.
29→4 clients.python.raccoon_client.rest.client uses clients.python.raccoon_client.serde.serde✕
- Connections
- 1 pair of types, where a type in clients.python.raccoon_client.rest.client uses a type in clients.python.raccoon_client.serde.serde.
- The types involved
clients.python.raccoon_client.rest.client.RestClient→clients.python.raccoon_client.serde.serde.Serde
- Direction
- clients.python.raccoon_client.rest.client uses clients.python.raccoon_client.serde.serde, so a change to clients.python.raccoon_client.serde.serde can break clients.python.raccoon_client.rest.client, while a change to clients.python.raccoon_client.rest.client can't break clients.python.raccoon_client.serde.serde.
- Position
- Below the diagonal: clients.python.raccoon_client.rest.client uses a module listed above it, which is the healthy direction.
29→5 clients.python.raccoon_client.rest.client uses clients.python.raccoon_client.serde.wire✕
- Connections
- 1 pair of types, where a type in clients.python.raccoon_client.rest.client uses a type in clients.python.raccoon_client.serde.wire.
- The types involved
clients.python.raccoon_client.rest.client.RestClient→clients.python.raccoon_client.serde.wire.Wire
- Direction
- clients.python.raccoon_client.rest.client uses clients.python.raccoon_client.serde.wire, so a change to clients.python.raccoon_client.serde.wire can break clients.python.raccoon_client.rest.client, while a change to clients.python.raccoon_client.rest.client can't break clients.python.raccoon_client.serde.wire.
- Position
- Below the diagonal: clients.python.raccoon_client.rest.client uses a module listed above it, which is the healthy direction.
29→18 clients.python.raccoon_client.rest.client uses clients.python.raccoon_client.rest.option✕
- Connections
- 2 pairs of types, where a type in clients.python.raccoon_client.rest.client uses a type in clients.python.raccoon_client.rest.option.
- The types involved
clients.python.raccoon_client.rest.client.RestClient→clients.python.raccoon_client.rest.option.HttpConfigclients.python.raccoon_client.rest.client.RestClient→clients.python.raccoon_client.rest.option.RestClientConfig
- Direction
- clients.python.raccoon_client.rest.client uses clients.python.raccoon_client.rest.option, so a change to clients.python.raccoon_client.rest.option can break clients.python.raccoon_client.rest.client, while a change to clients.python.raccoon_client.rest.client can't break clients.python.raccoon_client.rest.option.
- Position
- Below the diagonal: clients.python.raccoon_client.rest.client uses a module listed above it, which is the healthy direction.
30→13 github.com/raystack/raccoon/core/worker uses github.com/raystack/raccoon/pkg/clock✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/core/worker uses a type in github.com/raystack/raccoon/pkg/clock.
- The types involved
github.com/raystack/raccoon/core/worker.Pool→github.com/raystack/raccoon/pkg/clock.Clock
- Direction
- github.com/raystack/raccoon/core/worker uses github.com/raystack/raccoon/pkg/clock, so a change to github.com/raystack/raccoon/pkg/clock can break github.com/raystack/raccoon/core/worker, while a change to github.com/raystack/raccoon/core/worker can't break github.com/raystack/raccoon/pkg/clock.
- Position
- Below the diagonal: github.com/raystack/raccoon/core/worker uses a module listed above it, which is the healthy direction.
30→14 github.com/raystack/raccoon/core/worker uses github.com/raystack/raccoon/pkg/metrics✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/core/worker uses a type in github.com/raystack/raccoon/pkg/metrics.
- The types involved
github.com/raystack/raccoon/core/worker.Pool→github.com/raystack/raccoon/pkg/metrics.MetricInstrument
- Direction
- github.com/raystack/raccoon/core/worker uses github.com/raystack/raccoon/pkg/metrics, so a change to github.com/raystack/raccoon/pkg/metrics can break github.com/raystack/raccoon/core/worker, while a change to github.com/raystack/raccoon/core/worker can't break github.com/raystack/raccoon/pkg/metrics.
- Position
- Below the diagonal: github.com/raystack/raccoon/core/worker uses a module listed above it, which is the healthy direction.
30→26 github.com/raystack/raccoon/core/worker uses github.com/raystack/raccoon/core/collector✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/core/worker uses a type in github.com/raystack/raccoon/core/collector.
- The types involved
github.com/raystack/raccoon/core/worker.Pool→github.com/raystack/raccoon/core/collector.CollectRequestgithub.com/raystack/raccoon/core/worker.worker→github.com/raystack/raccoon/core/collector.CollectRequest
- Direction
- github.com/raystack/raccoon/core/worker uses github.com/raystack/raccoon/core/collector, so a change to github.com/raystack/raccoon/core/collector can break github.com/raystack/raccoon/core/worker, while a change to github.com/raystack/raccoon/core/worker can't break github.com/raystack/raccoon/core/collector.
- Position
- Below the diagonal: github.com/raystack/raccoon/core/worker uses a module listed above it, which is the healthy direction.
31→26 github.com/raystack/raccoon/server uses github.com/raystack/raccoon/core/collector✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/server uses a type in github.com/raystack/raccoon/core/collector.
- The types involved
github.com/raystack/raccoon/server.server→github.com/raystack/raccoon/core/collector.CollectRequest
- Direction
- github.com/raystack/raccoon/server uses github.com/raystack/raccoon/core/collector, so a change to github.com/raystack/raccoon/core/collector can break github.com/raystack/raccoon/server, while a change to github.com/raystack/raccoon/server can't break github.com/raystack/raccoon/core/collector.
- Position
- Below the diagonal: github.com/raystack/raccoon/server uses a module listed above it, which is the healthy direction.
32→12 github.com/raystack/raccoon/server/rest/websocket uses github.com/raystack/raccoon/core/serde✕
- Connections
- 5 pairs of types, where a type in github.com/raystack/raccoon/server/rest/websocket uses a type in github.com/raystack/raccoon/core/serde.
- The types involved
github.com/raystack/raccoon/server/rest/websocket.AckInfo→github.com/raystack/raccoon/core/serde.SerializeFuncgithub.com/raystack/raccoon/server/rest/websocket.Handler→github.com/raystack/raccoon/core/serde.SerializeFuncgithub.com/raystack/raccoon/server/rest/websocket.serDe→github.com/raystack/raccoon/core/serde.DeserializeFuncgithub.com/raystack/raccoon/server/rest/websocket.serDe→github.com/raystack/raccoon/core/serde.SerializeFuncgithub.com/raystack/raccoon/server/rest/websocket.websocket→github.com/raystack/raccoon/core/serde.SerializeFunc
- Direction
- github.com/raystack/raccoon/server/rest/websocket uses github.com/raystack/raccoon/core/serde, so a change to github.com/raystack/raccoon/core/serde can break github.com/raystack/raccoon/server/rest/websocket, while a change to github.com/raystack/raccoon/server/rest/websocket can't break github.com/raystack/raccoon/core/serde.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest/websocket uses a module listed above it, which is the healthy direction.
32→26 github.com/raystack/raccoon/server/rest/websocket uses github.com/raystack/raccoon/core/collector✕
- Connections
- 3 pairs of types, where a type in github.com/raystack/raccoon/server/rest/websocket uses a type in github.com/raystack/raccoon/core/collector.
- The types involved
github.com/raystack/raccoon/server/rest/websocket.Handler→github.com/raystack/raccoon/core/collector.AckFuncgithub.com/raystack/raccoon/server/rest/websocket.Handler→github.com/raystack/raccoon/core/collector.Collectorgithub.com/raystack/raccoon/server/rest/websocket.websocket→github.com/raystack/raccoon/core/collector.Collector
- Direction
- github.com/raystack/raccoon/server/rest/websocket uses github.com/raystack/raccoon/core/collector, so a change to github.com/raystack/raccoon/core/collector can break github.com/raystack/raccoon/server/rest/websocket, while a change to github.com/raystack/raccoon/server/rest/websocket can't break github.com/raystack/raccoon/core/collector.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest/websocket uses a module listed above it, which is the healthy direction.
32→27 github.com/raystack/raccoon/server/rest/websocket uses github.com/raystack/raccoon/server/rest/websocket/connection✕
- Connections
- 5 pairs of types, where a type in github.com/raystack/raccoon/server/rest/websocket uses a type in github.com/raystack/raccoon/server/rest/websocket/connection.
- The types involved
github.com/raystack/raccoon/server/rest/websocket.AckInfo→github.com/raystack/raccoon/server/rest/websocket/connection.Conngithub.com/raystack/raccoon/server/rest/websocket.Handler→github.com/raystack/raccoon/server/rest/websocket/connection.Conngithub.com/raystack/raccoon/server/rest/websocket.Handler→github.com/raystack/raccoon/server/rest/websocket/connection.Tablegithub.com/raystack/raccoon/server/rest/websocket.Handler→github.com/raystack/raccoon/server/rest/websocket/connection.Upgradergithub.com/raystack/raccoon/server/rest/websocket.websocket→github.com/raystack/raccoon/server/rest/websocket/connection.Conn
- Direction
- github.com/raystack/raccoon/server/rest/websocket uses github.com/raystack/raccoon/server/rest/websocket/connection, so a change to github.com/raystack/raccoon/server/rest/websocket/connection can break github.com/raystack/raccoon/server/rest/websocket, while a change to github.com/raystack/raccoon/server/rest/websocket can't break github.com/raystack/raccoon/server/rest/websocket/connection.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest/websocket uses a module listed above it, which is the healthy direction.
33→26 github.com/raystack/raccoon/app uses github.com/raystack/raccoon/core/collector✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/app uses a type in github.com/raystack/raccoon/core/collector.
- The types involved
github.com/raystack/raccoon/app.app→github.com/raystack/raccoon/core/collector.CollectRequest
- Direction
- github.com/raystack/raccoon/app uses github.com/raystack/raccoon/core/collector, so a change to github.com/raystack/raccoon/core/collector can break github.com/raystack/raccoon/app, while a change to github.com/raystack/raccoon/app can't break github.com/raystack/raccoon/core/collector.
- Position
- Below the diagonal: github.com/raystack/raccoon/app uses a module listed above it, which is the healthy direction.
33→30 github.com/raystack/raccoon/app uses github.com/raystack/raccoon/core/worker✕
- Connections
- 2 pairs of types, where a type in github.com/raystack/raccoon/app uses a type in github.com/raystack/raccoon/core/worker.
- The types involved
github.com/raystack/raccoon/app.Publisher→github.com/raystack/raccoon/core/worker.Producergithub.com/raystack/raccoon/app.app→github.com/raystack/raccoon/core/worker.Pool
- Direction
- github.com/raystack/raccoon/app uses github.com/raystack/raccoon/core/worker, so a change to github.com/raystack/raccoon/core/worker can break github.com/raystack/raccoon/app, while a change to github.com/raystack/raccoon/app can't break github.com/raystack/raccoon/core/worker.
- Position
- Below the diagonal: github.com/raystack/raccoon/app uses a module listed above it, which is the healthy direction.
33→31 github.com/raystack/raccoon/app uses github.com/raystack/raccoon/server✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/app uses a type in github.com/raystack/raccoon/server.
- The types involved
github.com/raystack/raccoon/app.app→github.com/raystack/raccoon/server.Services
- Direction
- github.com/raystack/raccoon/app uses github.com/raystack/raccoon/server, so a change to github.com/raystack/raccoon/server can break github.com/raystack/raccoon/app, while a change to github.com/raystack/raccoon/app can't break github.com/raystack/raccoon/server.
- Position
- Below the diagonal: github.com/raystack/raccoon/app uses a module listed above it, which is the healthy direction.
34→10 github.com/raystack/raccoon/server/grpc uses github.com/raystack/raccoon/config✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/server/grpc uses a type in github.com/raystack/raccoon/config.
- The types involved
github.com/raystack/raccoon/server/grpc.Handler→github.com/raystack/raccoon/config.AckType
- Direction
- github.com/raystack/raccoon/server/grpc uses github.com/raystack/raccoon/config, so a change to github.com/raystack/raccoon/config can break github.com/raystack/raccoon/server/grpc, while a change to github.com/raystack/raccoon/server/grpc can't break github.com/raystack/raccoon/config.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/grpc uses a module listed above it, which is the healthy direction.
34→26 github.com/raystack/raccoon/server/grpc uses github.com/raystack/raccoon/core/collector✕
- Connections
- 4 pairs of types, where a type in github.com/raystack/raccoon/server/grpc uses a type in github.com/raystack/raccoon/core/collector.
- The types involved
github.com/raystack/raccoon/server/grpc.Handler→github.com/raystack/raccoon/core/collector.AckFuncgithub.com/raystack/raccoon/server/grpc.Handler→github.com/raystack/raccoon/core/collector.Collectorgithub.com/raystack/raccoon/server/grpc.Service→github.com/raystack/raccoon/core/collector.Collectorgithub.com/raystack/raccoon/server/grpc.grpc→github.com/raystack/raccoon/core/collector.Collector
- Direction
- github.com/raystack/raccoon/server/grpc uses github.com/raystack/raccoon/core/collector, so a change to github.com/raystack/raccoon/core/collector can break github.com/raystack/raccoon/server/grpc, while a change to github.com/raystack/raccoon/server/grpc can't break github.com/raystack/raccoon/core/collector.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/grpc uses a module listed above it, which is the healthy direction.
34→31 github.com/raystack/raccoon/server/grpc uses github.com/raystack/raccoon/server✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/server/grpc uses a type in github.com/raystack/raccoon/server.
- The types involved
github.com/raystack/raccoon/server/grpc.Service→github.com/raystack/raccoon/server.bootstrapper
- Direction
- github.com/raystack/raccoon/server/grpc uses github.com/raystack/raccoon/server, so a change to github.com/raystack/raccoon/server can break github.com/raystack/raccoon/server/grpc, while a change to github.com/raystack/raccoon/server/grpc can't break github.com/raystack/raccoon/server.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/grpc uses a module listed above it, which is the healthy direction.
35→31 github.com/raystack/raccoon/server/pprof uses github.com/raystack/raccoon/server✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/server/pprof uses a type in github.com/raystack/raccoon/server.
- The types involved
github.com/raystack/raccoon/server/pprof.Service→github.com/raystack/raccoon/server.bootstrapper
- Direction
- github.com/raystack/raccoon/server/pprof uses github.com/raystack/raccoon/server, so a change to github.com/raystack/raccoon/server can break github.com/raystack/raccoon/server/pprof, while a change to github.com/raystack/raccoon/server/pprof can't break github.com/raystack/raccoon/server.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/pprof uses a module listed above it, which is the healthy direction.
36→10 github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/config✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/server/rest uses a type in github.com/raystack/raccoon/config.
- The types involved
github.com/raystack/raccoon/server/rest.Handler→github.com/raystack/raccoon/config.AckType
- Direction
- github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/config, so a change to github.com/raystack/raccoon/config can break github.com/raystack/raccoon/server/rest, while a change to github.com/raystack/raccoon/server/rest can't break github.com/raystack/raccoon/config.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest uses a module listed above it, which is the healthy direction.
36→12 github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/core/serde✕
- Connections
- 4 pairs of types, where a type in github.com/raystack/raccoon/server/rest uses a type in github.com/raystack/raccoon/core/serde.
- The types involved
github.com/raystack/raccoon/server/rest.Handler→github.com/raystack/raccoon/core/serde.SerializeFuncgithub.com/raystack/raccoon/server/rest.Response→github.com/raystack/raccoon/core/serde.SerializeFuncgithub.com/raystack/raccoon/server/rest.serDe→github.com/raystack/raccoon/core/serde.DeserializeFuncgithub.com/raystack/raccoon/server/rest.serDe→github.com/raystack/raccoon/core/serde.SerializeFunc
- Direction
- github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/core/serde, so a change to github.com/raystack/raccoon/core/serde can break github.com/raystack/raccoon/server/rest, while a change to github.com/raystack/raccoon/server/rest can't break github.com/raystack/raccoon/core/serde.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest uses a module listed above it, which is the healthy direction.
36→26 github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/core/collector✕
- Connections
- 4 pairs of types, where a type in github.com/raystack/raccoon/server/rest uses a type in github.com/raystack/raccoon/core/collector.
- The types involved
github.com/raystack/raccoon/server/rest.Handler→github.com/raystack/raccoon/core/collector.AckFuncgithub.com/raystack/raccoon/server/rest.Handler→github.com/raystack/raccoon/core/collector.Collectorgithub.com/raystack/raccoon/server/rest.Service→github.com/raystack/raccoon/core/collector.Collectorgithub.com/raystack/raccoon/server/rest.rest→github.com/raystack/raccoon/core/collector.Collector
- Direction
- github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/core/collector, so a change to github.com/raystack/raccoon/core/collector can break github.com/raystack/raccoon/server/rest, while a change to github.com/raystack/raccoon/server/rest can't break github.com/raystack/raccoon/core/collector.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest uses a module listed above it, which is the healthy direction.
36→27 github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/server/rest/websocket/connection✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/server/rest uses a type in github.com/raystack/raccoon/server/rest/websocket/connection.
- The types involved
github.com/raystack/raccoon/server/rest.rest→github.com/raystack/raccoon/server/rest/websocket/connection.Table
- Direction
- github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/server/rest/websocket/connection, so a change to github.com/raystack/raccoon/server/rest/websocket/connection can break github.com/raystack/raccoon/server/rest, while a change to github.com/raystack/raccoon/server/rest can't break github.com/raystack/raccoon/server/rest/websocket/connection.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest uses a module listed above it, which is the healthy direction.
36→31 github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/server✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/server/rest uses a type in github.com/raystack/raccoon/server.
- The types involved
github.com/raystack/raccoon/server/rest.Service→github.com/raystack/raccoon/server.bootstrapper
- Direction
- github.com/raystack/raccoon/server/rest uses github.com/raystack/raccoon/server, so a change to github.com/raystack/raccoon/server can break github.com/raystack/raccoon/server/rest, while a change to github.com/raystack/raccoon/server/rest can't break github.com/raystack/raccoon/server.
- Position
- Below the diagonal: github.com/raystack/raccoon/server/rest uses a module listed above it, which is the healthy direction.
37→30 github.com/raystack/raccoon/publisher/kafka uses github.com/raystack/raccoon/core/worker✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/publisher/kafka uses a type in github.com/raystack/raccoon/core/worker.
- The types involved
github.com/raystack/raccoon/publisher/kafka.Kafka→github.com/raystack/raccoon/core/worker.Producer
- Direction
- github.com/raystack/raccoon/publisher/kafka uses github.com/raystack/raccoon/core/worker, so a change to github.com/raystack/raccoon/core/worker can break github.com/raystack/raccoon/publisher/kafka, while a change to github.com/raystack/raccoon/publisher/kafka can't break github.com/raystack/raccoon/core/worker.
- Position
- Below the diagonal: github.com/raystack/raccoon/publisher/kafka uses a module listed above it, which is the healthy direction.
37→33 github.com/raystack/raccoon/publisher/kafka uses github.com/raystack/raccoon/app✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/publisher/kafka uses a type in github.com/raystack/raccoon/app.
- The types involved
github.com/raystack/raccoon/publisher/kafka.Kafka→github.com/raystack/raccoon/app.Publisher
- Direction
- github.com/raystack/raccoon/publisher/kafka uses github.com/raystack/raccoon/app, so a change to github.com/raystack/raccoon/app can break github.com/raystack/raccoon/publisher/kafka, while a change to github.com/raystack/raccoon/publisher/kafka can't break github.com/raystack/raccoon/app.
- Position
- Below the diagonal: github.com/raystack/raccoon/publisher/kafka uses a module listed above it, which is the healthy direction.
38→30 github.com/raystack/raccoon/publisher/kinesis uses github.com/raystack/raccoon/core/worker✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/publisher/kinesis uses a type in github.com/raystack/raccoon/core/worker.
- The types involved
github.com/raystack/raccoon/publisher/kinesis.Publisher→github.com/raystack/raccoon/core/worker.Producer
- Direction
- github.com/raystack/raccoon/publisher/kinesis uses github.com/raystack/raccoon/core/worker, so a change to github.com/raystack/raccoon/core/worker can break github.com/raystack/raccoon/publisher/kinesis, while a change to github.com/raystack/raccoon/publisher/kinesis can't break github.com/raystack/raccoon/core/worker.
- Position
- Below the diagonal: github.com/raystack/raccoon/publisher/kinesis uses a module listed above it, which is the healthy direction.
38→33 github.com/raystack/raccoon/publisher/kinesis uses github.com/raystack/raccoon/app✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/publisher/kinesis uses a type in github.com/raystack/raccoon/app.
- The types involved
github.com/raystack/raccoon/publisher/kinesis.Publisher→github.com/raystack/raccoon/app.Publisher
- Direction
- github.com/raystack/raccoon/publisher/kinesis uses github.com/raystack/raccoon/app, so a change to github.com/raystack/raccoon/app can break github.com/raystack/raccoon/publisher/kinesis, while a change to github.com/raystack/raccoon/publisher/kinesis can't break github.com/raystack/raccoon/app.
- Position
- Below the diagonal: github.com/raystack/raccoon/publisher/kinesis uses a module listed above it, which is the healthy direction.
39→30 github.com/raystack/raccoon/publisher/log uses github.com/raystack/raccoon/core/worker✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/publisher/log uses a type in github.com/raystack/raccoon/core/worker.
- The types involved
github.com/raystack/raccoon/publisher/log.Publisher→github.com/raystack/raccoon/core/worker.Producer
- Direction
- github.com/raystack/raccoon/publisher/log uses github.com/raystack/raccoon/core/worker, so a change to github.com/raystack/raccoon/core/worker can break github.com/raystack/raccoon/publisher/log, while a change to github.com/raystack/raccoon/publisher/log can't break github.com/raystack/raccoon/core/worker.
- Position
- Below the diagonal: github.com/raystack/raccoon/publisher/log uses a module listed above it, which is the healthy direction.
39→33 github.com/raystack/raccoon/publisher/log uses github.com/raystack/raccoon/app✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/publisher/log uses a type in github.com/raystack/raccoon/app.
- The types involved
github.com/raystack/raccoon/publisher/log.Publisher→github.com/raystack/raccoon/app.Publisher
- Direction
- github.com/raystack/raccoon/publisher/log uses github.com/raystack/raccoon/app, so a change to github.com/raystack/raccoon/app can break github.com/raystack/raccoon/publisher/log, while a change to github.com/raystack/raccoon/publisher/log can't break github.com/raystack/raccoon/app.
- Position
- Below the diagonal: github.com/raystack/raccoon/publisher/log uses a module listed above it, which is the healthy direction.
40→30 github.com/raystack/raccoon/publisher/pubsub uses github.com/raystack/raccoon/core/worker✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/publisher/pubsub uses a type in github.com/raystack/raccoon/core/worker.
- The types involved
github.com/raystack/raccoon/publisher/pubsub.Publisher→github.com/raystack/raccoon/core/worker.Producer
- Direction
- github.com/raystack/raccoon/publisher/pubsub uses github.com/raystack/raccoon/core/worker, so a change to github.com/raystack/raccoon/core/worker can break github.com/raystack/raccoon/publisher/pubsub, while a change to github.com/raystack/raccoon/publisher/pubsub can't break github.com/raystack/raccoon/core/worker.
- Position
- Below the diagonal: github.com/raystack/raccoon/publisher/pubsub uses a module listed above it, which is the healthy direction.
40→33 github.com/raystack/raccoon/publisher/pubsub uses github.com/raystack/raccoon/app✕
- Connections
- 1 pair of types, where a type in github.com/raystack/raccoon/publisher/pubsub uses a type in github.com/raystack/raccoon/app.
- The types involved
github.com/raystack/raccoon/publisher/pubsub.Publisher→github.com/raystack/raccoon/app.Publisher
- Direction
- github.com/raystack/raccoon/publisher/pubsub uses github.com/raystack/raccoon/app, so a change to github.com/raystack/raccoon/app can break github.com/raystack/raccoon/publisher/pubsub, while a change to github.com/raystack/raccoon/publisher/pubsub can't break github.com/raystack/raccoon/app.
- Position
- Below the diagonal: github.com/raystack/raccoon/publisher/pubsub uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 77 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 55 | High / Critical |
| A02:2025 — Security Misconfiguration | 11 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor); Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +5.0 pts | Medium | Type Safety |
| Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor). | +4.6 pts | Medium | Nullable reference types |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.8 pts | Low | ADR Quality |
| Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +1.6 pts | Low | Dependency Hygiene |
| Resolve the 1 Deprecated module finding(s) in Dependency Hygiene. | +1.1 pts | Low | Dependency Hygiene |
| Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with handler.go (3), server.go (2), REDACTED. | +1.8 pts | Medium | Knowledge Freshness |
| Swallowed exception (caught, then discarded) | +1.7 pts | Medium | Exception handling |
| Resolve the 1 TooManyFields finding(s) in God Classes — start with publisher.go. | +0.8 pts | Low | God Classes |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.1 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.3 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 76 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, 183 of 228 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 54 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 40 test source file(s) (.go, .py) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the JavaScript/TypeScript suite (jest via `npm ci --ignore-scripts` in clients/js/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 22 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 22 of the 102 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — kafka Pulling pubsub-emulator Pulling zookeeper Pulling localstack Pulling pubsub-emulator Error Get "https://gcr.io/v2/": Forbidden kafka Error context canceled localstack Error context canceled zookeeper Error context canceled Error response from daemon: Get "https://gcr.io/v2/": Forbidden; the earlier `compose pull` step reported: cs Skipped - No image to be pulled kafka Pulling localstack Pulling pubsub-emulator Pulling zookeeper Pulling pubsub-emulator Error Get "https://gcr.io/v2/": Forbidden kafka Error context canceled localstack Error context canceled zookeeper Error context canceled Error response from daemon: Get "https://gcr.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go, Java, Python is most of its product and 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Go, Python is most of its product and 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was Pool.worker at 19.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with Pool.worker (cognitive 19), config.cfgMetadata (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.6 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
1 god class(es) detected.
What to do
- Resolve the 1 TooManyFields finding(s) in God Classes — start with publisher.go. — One of this dimension's main actionable groups (1 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
8 duplicated block group(s) detected. 2 of the 8 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with handler.go (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with rest.go. — One of this dimension's main actionable groups (1 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
5 production modules (Gradle+npm+Go+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 4 of the 5 (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).
D6 · Cohesion (LCOM4)
0 of 20 classes have LCOM4 above 3.
D9 · Test Distribution
158 test methods: 156 unit, 2 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 54 `it`/`test` case(s) across 6 test file(s) declaring at least one beside 11 .NET test method(s); its tier split is read from package names and paths only. The Python suite contributes 29 test function(s) across 4 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Go suite contributes 64 test case(s) across 31 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 4 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 54 tests. Measured on the JavaScript/TypeScript suite only — at least 40 test source file(s) (.go, .py) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
24 outdated, 1 author-deprecated direct Go module(s), 2 pinning or checksum defect(s). 34 of 34 direct requirement(s) were graded against proxy.golang.org (0 not served there, 3 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
What to do
- Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 2 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
4 deducted task-comment markers across 5083 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 4 TodoComment finding(s) in Explicit Debt — start with handler_test.go, pubsub.go, config.go. — One of this dimension's main actionable groups (4 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. 28 document(s) read across 3 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
0 of 6 build units (Go, Gradle, Python, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
63 % of calls cross a namespace and 17 % go through an interface, but 61 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 7.9/10. — 63 % of calls cross a namespace and 17 % go through an interface, but 61 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 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 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)
77 finding(s): 0 critical, 52 high, 23 medium, 2 low. 47 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 1 file(s) — `clients/java/gradlew` (line 72, line 173) — 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.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 47 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 (47 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
37 finding(s): 6 critical, 11 high, 18 medium, 2 low.
What to do
- Resolve the 17 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED (6). — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 issue-level).
D31 · IaC & Container Security
11 finding(s): 0 critical, 3 high, 7 medium, 1 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
22 of 22 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is config/publisher.go. Counted over 22 of the 102 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 21 Orphaned file finding(s) in Knowledge Freshness — start with handler.go (3), server.go (2), REDACTED. — One of this dimension's main actionable groups (21 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with publisher.go. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 11 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 7 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.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
- 45/62 types (73%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Go: an unexported name, or move it under `internal/`; Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P2 · Observability
P3 · Security & performance tooling
- `clients/js/examples/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — clients/js/examples/package.json:11
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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
- Deployment 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 reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
P6 · Release Hygiene
PF1 · Benchmark discipline
- A Go testing.B suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — server/rest/websocket/connection/table_test.go
What to do
- Call b.ReportAllocs() in the benchmarks, or run them with `go test -bench . -benchmem`, so allocation regressions are visible, not just time.
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 15 plain JS — the untyped files are clients/js/lib/rest.js, clients/js/lib/retry/retry.js, clients/js/lib/serializer/json_serializer.js, clients/js/lib/serializer/proto_serializer.js, clients/js/lib/types/serialization_type.js, clients/js/lib/types/wire_type.js (+9 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- clients/js/lib/serializer/proto_serializer.js:2 · clients/js/lib/wire/proto_wire.js:4 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — clients/js/lib/serializer/proto_serializer.js:2
- clients/js/lib/wire/json_wire.js:3 · clients/js/lib/wire/proto_wire.js:3 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — clients/js/lib/wire/json_wire.js:3
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- constructor has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — clients/js/lib/rest.js:31
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. — clients/js/main.js:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
R8 · Dependency Hygiene
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
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
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — clients/go/ws/ws.go:112, clients/go/grpc/grpc.go:75
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- 0/5 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 53% | Adequate — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 83% | Strong | Solid. |
| Maturity | 67% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate | Acceptable, with room to improve. |
| Security | 62% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 91% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 51 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: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — kafka Pulling pubsub-emulator Pulling zookeeper Pulling localstack Pulling pubsub-emulator Error Get "https://gcr.io/v2/": Forbidden kafka Error context canceled localstack Error context canceled zookeeper Error context canceled Error response from daemon: Get "https://gcr.io/v2/": Forbidden; the earlier `compose pull` step reported: cs Skipped - No image to be pulled kafka Pulling localstack Pulling pubsub-emulator Pulling zookeeper Pulling pubsub-emulator Error Get "https://gcr.io/v2/": Forbidden kafka Error context canceled localstack Error context canceled zookeeper Error context canceled Error response from daemon: Get "https://gcr.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — No tests discovered
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- 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# and TypeScript only; Go, Java, JavaScript, Python not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go, .java, .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- 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 MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in clients/js/ ran and not one test passed (FAIL test/rest.test.js), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 4 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- M4 Documentation accuracy — Not applicable: the 28 current-state document(s) make no claim of a kind M4 checks. 37 claim(s) of kinds M4 does not check were not checked (command argument 5, install 1, environment variable 28, route 2, cd 1); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Go, JVM, JavaScript/TypeScript, Python source (service entry point: REDACTED:34 (mux.NewRouter())
- 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 (`go test -coverprofile=coverage.out ./...`) 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Python were read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; 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
- 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.
- 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 — 73 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
- REDACTED
Serious — 89 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
- TodoComment server/grpc/handler_test.go:21
- TodoComment publisher/pubsub/pubsub.go:27
- TodoComment config/config.go:37
- TodoComment config/walk.go:13
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency pinned to a stale untagged commit: golang.org/x/lint
- Dependency pinned to a stale untagged commit: github.com/alecthomas/assert
- Duplicated block (5 lines × 2) server/rest/handler.go:148
- Duplicated block (5 lines × 2) server/rest/handler.go:167
- Duplicated block (12 lines × 2 locations) clients/js/lib/serializer/proto_serializer.js:2
- Duplicated block (12 lines × 2 locations) clients/js/lib/wire/json_wire.js:3
- Swallowed exception (caught, then discarded) clients/go/ws/ws.go:112
- Swallowed exception (caught, then discarded) clients/go/grpc/grpc.go:75
- Deprecated module: cloud.google.com/go/pubsub
- Pool.worker (cognitive 19) core/worker/worker.go:47
- config.cfgMetadata (cognitive 16) config/errors.go:9
- REDACTED
- TooManyFields: kafkaClientConfig config/publisher.go:33
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2) REDACTED:254
- Duplicated block (12 lines × 2) clients/go/rest/rest.go:55
- Duplicated block (10 lines × 2) clients/go/rest/rest.go:43
- Duplicated block (7 lines × 2) clients/go/serializer/serializer.go:19
- Duplicated block (24 lines × 2) clients/go/examples/grpc/main.go:32
- Duplicated block (14–16 lines × 3) clients/go/examples/grpc/main.go:40
- Coverage not measured — JavaScript/TypeScript suite
- Coverage collected but not gated
- Type Safety
- Complex function constructor (cyclomatic 11, cognitive 10) clients/js/lib/rest.js:31
- No test reaches this file clients/js/main.js:1
Minor — 42 finding(s)
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file app/server.go:1
- Orphaned file server/rest/websocket/handler.go:1
- Orphaned file publisher/pubsub/pubsub.go:1
- Orphaned file server/rest/handler.go:1
- Orphaned file clients/java/src/main/java/io/odpf/raccoon/client/RestClient.java:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file core/worker/worker.go:1
- Orphaned file config/server.go:1
- Orphaned file clients/go/ws/ws.go:1
- Orphaned file clients/java/build.gradle:1
- Orphaned file pkg/metrics/metrics.go:1
- Orphaned file clients/python/raccoon_client/rest/client.py:1
- Orphaned file clients/go/rest/rest.go:1
- Orphaned file server/grpc/handler.go:1
- Orphaned file clients/go/grpc/grpc.go:1
- Orphaned file REDACTED:1
- Orphaned file config/config.go:1
- Orphaned file clients/java/src/main/java/io/odpf/raccoon/wire/JsonWire.java:1
- REDACTED
- REDACTED
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dormant codebase
- Most significant orphaned file config/publisher.go:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Large public API surface
- No dependency-update automation clients/js/examples/package.json:11
- No rollback/health safety
- No release approval gate
- Benchmarks don't track allocations server/rest/websocket/connection/table_test.go
- Duplicated predicate clients/js/lib/serializer/proto_serializer.js:8
- Java packages are not null-marked everywhere
Minor — 24 finding(s)
- Outdated: github.com/alecthomas/assert
- Outdated: github.com/aws/aws-sdk-go-v2
- Outdated: github.com/aws/aws-sdk-go-v2/config
- Outdated: github.com/aws/aws-sdk-go-v2/service/kinesis
- Outdated: github.com/gojek/heimdall/v7
- Outdated: github.com/googleapis/gax-go/v2
- Outdated: github.com/gorilla/handlers
- Outdated: github.com/gorilla/mux
- Outdated: github.com/gorilla/websocket
- Outdated: github.com/gorilla/websocket
- Outdated: github.com/prometheus/client_golang
- Outdated: github.com/raystack/salt
- Outdated: github.com/sirupsen/logrus
- Outdated: github.com/spf13/cast
- Outdated: github.com/spf13/cobra
- Outdated: github.com/spf13/pflag
- Outdated: github.com/stretchr/testify
- Outdated: github.com/stretchr/testify
- Outdated: google.golang.org/api
- Outdated: google.golang.org/grpc
- Outdated: google.golang.org/grpc
- Outdated: google.golang.org/protobuf
- Outdated: google.golang.org/protobuf
- Outdated: honnef.co/go/tools
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-896fbbb7203647f18cd662c53d53d5a8/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-896fbbb7203647f18cd662c53d53d5a8/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude clients/java/src/main/java/io/odpf/proton --exclude clients/java/src/test/java/sample --exclude clients/js/protos --exclude proto . | 77 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 37 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |