Executive summary
yaes-io/yaes meets our standard for a preview release. It scores 69 out of 100 and is rated Strong, and all 18 of its critical findings are security problems in the build pipeline and in its servers and containers.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first steps are recording design decisions and declaring which values may be missing, each worth about 2 points.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven settings leave the servers or containers unsafe, and one secret can leak from the build pipeline. Pinning each tool to an exact version, correcting the unsafe settings and limiting the secret to its own step would close these risks.
The product code is 12,751 lines, about €39,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
The weakest lenses score close to each other, so improving any of them moves the score.
Rebuild cost: about €39,000 · Estimate
| Cost to rebuild | €13,000 to €65,000, for 214 to 680 hours of work, about 0.3 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 | ×1.0 at a score of 69. 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: 12,751 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Clock | 2 Flow | 3 Output | 4 Random | 5 Reader | 6 Resource | 7 Shutdown | 8 State | 9 System | 10 Unscoped | 11 Writer | 12 http.core | 13 http.server.params.path | 14 http.server.params.query | 15 Channel | 16 http.server.params.path.PathParamError | 17 http.server.params.query.QueryParamError | 18 http.server.routing | 19 io.yaes | 20 Channel.Type | 21 Async | 22 CircuitBreaker | 23 Input | 24 Log | 25 Raise | 26 Retry | 27 Sync | 28 cats | 29 http.client | 30 http.core.DecodingError | 31 instances.RaiseInstances | 32 interop.catseffect | 33 slf4j | 34 Log.Level | 35 Raise.LazyValue | 36 http.client.ConnectionError | 37 http.client.HttpError | 38 http.server | 39 http.server.parsing | 40 http.server.parsing.HttpParseError |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Clock | ||||||||||||||||||||||||||||||||||||||||
| 2 Flow | ||||||||||||||||||||||||||||||||||||||||
| 3 Output | ||||||||||||||||||||||||||||||||||||||||
| 4 Random | ||||||||||||||||||||||||||||||||||||||||
| 5 Reader | ||||||||||||||||||||||||||||||||||||||||
| 6 Resource | ||||||||||||||||||||||||||||||||||||||||
| 7 Shutdown | ||||||||||||||||||||||||||||||||||||||||
| 8 State | ||||||||||||||||||||||||||||||||||||||||
| 9 System | ||||||||||||||||||||||||||||||||||||||||
| 10 Unscoped | ||||||||||||||||||||||||||||||||||||||||
| 11 Writer | ||||||||||||||||||||||||||||||||||||||||
| 12 http.core | ||||||||||||||||||||||||||||||||||||||||
| 13 http.server.params.path | ||||||||||||||||||||||||||||||||||||||||
| 14 http.server.params.query | ||||||||||||||||||||||||||||||||||||||||
| 15 Channel | 8 | |||||||||||||||||||||||||||||||||||||||
| 16 http.server.params.path.PathParamError | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 http.server.params.query.QueryParamError | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 http.server.routing | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 19 io.yaes | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Channel.Type | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 Async | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 CircuitBreaker | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 Input | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Log | 4 | |||||||||||||||||||||||||||||||||||||||
| 25 Raise | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Retry | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 Sync | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 cats | 3 | |||||||||||||||||||||||||||||||||||||||
| 29 http.client | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 http.core.DecodingError | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 instances.RaiseInstances | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 interop.catseffect | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 slf4j | 3 | |||||||||||||||||||||||||||||||||||||||
| 34 Log.Level | 6 | |||||||||||||||||||||||||||||||||||||||
| 35 Raise.LazyValue | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 http.client.ConnectionError | 4 | |||||||||||||||||||||||||||||||||||||||
| 37 http.client.HttpError | 16 | |||||||||||||||||||||||||||||||||||||||
| 38 http.server | 1 | 2 | 2 | 5 | 6 | 3 | ||||||||||||||||||||||||||||||||||
| 39 http.server.parsing | 3 | |||||||||||||||||||||||||||||||||||||||
| 40 http.server.parsing.HttpParseError | 9 | 9 |
15→19 Channel uses io.yaes part of a loop✕
- Connections
- 8 pairs of types, where a type in Channel uses a type in io.yaes.
- The types involved
io.yaes.Channel.BoundedChannel→io.yaes.Channelio.yaes.Channel.BoundedChannel→io.yaes.Raiseio.yaes.Channel.ReceiveChannel→io.yaes.Raiseio.yaes.Channel.RendezvousChannel→io.yaes.Channelio.yaes.Channel.RendezvousChannel→io.yaes.Raiseio.yaes.Channel.SendChannel→io.yaes.Raiseio.yaes.Channel.UnboundedChannel→io.yaes.Channelio.yaes.Channel.UnboundedChannel→io.yaes.Raise
- Direction
- Channel uses io.yaes, so a change to io.yaes can break Channel, while a change to Channel can't break io.yaes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→13 http.server.params.path.PathParamError uses http.server.params.path✕
- Connections
- 2 pairs of types, where a type in http.server.params.path.PathParamError uses a type in http.server.params.path.
- The types involved
io.yaes.http.server.params.path.PathParamError.InvalidType→io.yaes.http.server.params.path.PathParamErrorio.yaes.http.server.params.path.PathParamError.MissingParam→io.yaes.http.server.params.path.PathParamError
- Direction
- http.server.params.path.PathParamError uses http.server.params.path, so a change to http.server.params.path can break http.server.params.path.PathParamError, while a change to http.server.params.path.PathParamError can't break http.server.params.path.
- Position
- Below the diagonal: http.server.params.path.PathParamError uses a module listed above it, which is the healthy direction.
17→14 http.server.params.query.QueryParamError uses http.server.params.query✕
- Connections
- 3 pairs of types, where a type in http.server.params.query.QueryParamError uses a type in http.server.params.query.
- The types involved
io.yaes.http.server.params.query.QueryParamError.InvalidFormat→io.yaes.http.server.params.query.QueryParamErrorio.yaes.http.server.params.query.QueryParamError.InvalidType→io.yaes.http.server.params.query.QueryParamErrorio.yaes.http.server.params.query.QueryParamError.MissingParam→io.yaes.http.server.params.query.QueryParamError
- Direction
- http.server.params.query.QueryParamError uses http.server.params.query, so a change to http.server.params.query can break http.server.params.query.QueryParamError, while a change to http.server.params.query.QueryParamError can't break http.server.params.query.
- Position
- Below the diagonal: http.server.params.query.QueryParamError uses a module listed above it, which is the healthy direction.
18→12 http.server.routing uses http.core✕
- Connections
- 1 pair of types, where a type in http.server.routing uses a type in http.core.
- The types involved
io.yaes.http.server.routing.Route→io.yaes.http.core.Method
- Direction
- http.server.routing uses http.core, so a change to http.core can break http.server.routing, while a change to http.server.routing can't break http.core.
- Position
- Below the diagonal: http.server.routing uses a module listed above it, which is the healthy direction.
18→13 http.server.routing uses http.server.params.path✕
- Connections
- 1 pair of types, where a type in http.server.routing uses a type in http.server.params.path.
- The types involved
io.yaes.http.server.routing.PathPattern→io.yaes.http.server.params.path.PathSegment
- Direction
- http.server.routing uses http.server.params.path, so a change to http.server.params.path can break http.server.routing, while a change to http.server.routing can't break http.server.params.path.
- Position
- Below the diagonal: http.server.routing uses a module listed above it, which is the healthy direction.
18→14 http.server.routing uses http.server.params.query✕
- Connections
- 1 pair of types, where a type in http.server.routing uses a type in http.server.params.query.
- The types involved
io.yaes.http.server.routing.PathPattern→io.yaes.http.server.params.query.QueryParamSpec
- Direction
- http.server.routing uses http.server.params.query, so a change to http.server.params.query can break http.server.routing, while a change to http.server.routing can't break http.server.params.query.
- Position
- Below the diagonal: http.server.routing uses a module listed above it, which is the healthy direction.
18→38 http.server.routing uses http.server part of a loop✕
- Connections
- 3 pairs of types, where a type in http.server.routing uses a type in http.server.
- The types involved
io.yaes.http.server.routing.PathPattern→io.yaes.http.server.Requestio.yaes.http.server.routing.Route→io.yaes.http.server.Requestio.yaes.http.server.routing.Route→io.yaes.http.server.Response
- Direction
- http.server.routing uses http.server, so a change to http.server can break http.server.routing, while a change to http.server.routing can't break http.server.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→15 io.yaes uses Channel✕
- Connections
- 1 pair of types, where a type in io.yaes uses a type in Channel.
- The types involved
io.yaes.Channel→io.yaes.Channel.SendChannel
- Direction
- io.yaes uses Channel, so a change to Channel can break io.yaes, while a change to io.yaes can't break Channel.
- Position
- Below the diagonal: io.yaes uses a module listed above it, which is the healthy direction.
20→15 Channel.Type uses Channel✕
- Connections
- 4 pairs of types, where a type in Channel.Type uses a type in Channel.
- The types involved
io.yaes.Channel.Type.Bounded→io.yaes.Channel.OverflowStrategyio.yaes.Channel.Type.Bounded→io.yaes.Channel.Typeio.yaes.Channel.Type.Rendezvous→io.yaes.Channel.Typeio.yaes.Channel.Type.Unbounded→io.yaes.Channel.Type
- Direction
- Channel.Type uses Channel, so a change to Channel can break Channel.Type, while a change to Channel.Type can't break Channel.
- Position
- Below the diagonal: Channel.Type uses a module listed above it, which is the healthy direction.
21→19 Async uses io.yaes✕
- Connections
- 1 pair of types, where a type in Async uses a type in io.yaes.
- The types involved
io.yaes.Async.Unsafe→io.yaes.Fiber
- Direction
- Async uses io.yaes, so a change to io.yaes can break Async, while a change to Async can't break io.yaes.
- Position
- Below the diagonal: Async uses a module listed above it, which is the healthy direction.
22→19 CircuitBreaker uses io.yaes✕
- Connections
- 3 pairs of types, where a type in CircuitBreaker uses a type in io.yaes.
- The types involved
io.yaes.CircuitBreaker.ProtectPartiallyApplied→io.yaes.CircuitBreakerio.yaes.CircuitBreaker.ProtectPartiallyApplied→io.yaes.Clockio.yaes.CircuitBreaker.ProtectPartiallyApplied→io.yaes.Raise
- Direction
- CircuitBreaker uses io.yaes, so a change to io.yaes can break CircuitBreaker, while a change to CircuitBreaker can't break io.yaes.
- Position
- Below the diagonal: CircuitBreaker uses a module listed above it, which is the healthy direction.
23→19 Input uses io.yaes✕
- Connections
- 1 pair of types, where a type in Input uses a type in io.yaes.
- The types involved
io.yaes.Input.Unsafe→io.yaes.Raise
- Direction
- Input uses io.yaes, so a change to io.yaes can break Input, while a change to Input can't break io.yaes.
- Position
- Below the diagonal: Input uses a module listed above it, which is the healthy direction.
24→19 Log uses io.yaes✕
- Connections
- 4 pairs of types, where a type in Log uses a type in io.yaes.
- The types involved
io.yaes.Log.ConsoleLogger→io.yaes.Clockio.yaes.Log.ConsoleLogger→io.yaes.Logio.yaes.Log.ConsoleLogger→io.yaes.Loggerio.yaes.Log.Unsafe→io.yaes.Logger
- Direction
- Log uses io.yaes, so a change to io.yaes can break Log, while a change to Log can't break io.yaes.
- Position
- Below the diagonal: Log uses a module listed above it, which is the healthy direction.
25→19 Raise uses io.yaes✕
- Connections
- 1 pair of types, where a type in Raise uses a type in io.yaes.
- The types involved
io.yaes.Raise.MapError→io.yaes.Raise
- Direction
- Raise uses io.yaes, so a change to io.yaes can break Raise, while a change to Raise can't break io.yaes.
- Position
- Below the diagonal: Raise uses a module listed above it, which is the healthy direction.
26→19 Retry uses io.yaes✕
- Connections
- 3 pairs of types, where a type in Retry uses a type in io.yaes.
- The types involved
io.yaes.Retry.RetryPartiallyApplied→io.yaes.Asyncio.yaes.Retry.RetryPartiallyApplied→io.yaes.Raiseio.yaes.Retry.RetryPartiallyApplied→io.yaes.Schedule
- Direction
- Retry uses io.yaes, so a change to io.yaes can break Retry, while a change to Retry can't break io.yaes.
- Position
- Below the diagonal: Retry uses a module listed above it, which is the healthy direction.
27→19 Sync uses io.yaes✕
- Connections
- 1 pair of types, where a type in Sync uses a type in io.yaes.
- The types involved
io.yaes.Sync.Unsafe→io.yaes.Executor
- Direction
- Sync uses io.yaes, so a change to io.yaes can break Sync, while a change to Sync can't break io.yaes.
- Position
- Below the diagonal: Sync uses a module listed above it, which is the healthy direction.
28→19 cats uses io.yaes✕
- Connections
- 3 pairs of types, where a type in cats uses a type in io.yaes.
- The types involved
io.yaes.cats.accumulate→io.yaes.NonEmptyListio.yaes.cats.accumulate→io.yaes.Raiseio.yaes.cats.validated→io.yaes.Raise
- Direction
- cats uses io.yaes, so a change to io.yaes can break cats, while a change to cats can't break io.yaes.
- Position
- Below the diagonal: cats uses a module listed above it, which is the healthy direction.
29→12 http.client uses http.core✕
- Connections
- 1 pair of types, where a type in http.client uses a type in http.core.
- The types involved
io.yaes.http.client.HttpRequest→io.yaes.http.core.Method
- Direction
- http.client uses http.core, so a change to http.core can break http.client, while a change to http.client can't break http.core.
- Position
- Below the diagonal: http.client uses a module listed above it, which is the healthy direction.
29→19 http.client uses io.yaes✕
- Connections
- 2 pairs of types, where a type in http.client uses a type in io.yaes.
- The types involved
io.yaes.http.client.YaesClient→io.yaes.Raiseio.yaes.http.client.YaesClient→io.yaes.Sync
- Direction
- http.client uses io.yaes, so a change to io.yaes can break http.client, while a change to http.client can't break io.yaes.
- Position
- Below the diagonal: http.client uses a module listed above it, which is the healthy direction.
30→12 http.core.DecodingError uses http.core✕
- Connections
- 2 pairs of types, where a type in http.core.DecodingError uses a type in http.core.
- The types involved
io.yaes.http.core.DecodingError.ParseError→io.yaes.http.core.DecodingErrorio.yaes.http.core.DecodingError.ValidationErrors→io.yaes.http.core.DecodingError
- Direction
- http.core.DecodingError uses http.core, so a change to http.core can break http.core.DecodingError, while a change to http.core.DecodingError can't break http.core.
- Position
- Below the diagonal: http.core.DecodingError uses a module listed above it, which is the healthy direction.
30→19 http.core.DecodingError uses io.yaes✕
- Connections
- 1 pair of types, where a type in http.core.DecodingError uses a type in io.yaes.
- The types involved
io.yaes.http.core.DecodingError.ValidationErrors→io.yaes.NonEmptyList
- Direction
- http.core.DecodingError uses io.yaes, so a change to io.yaes can break http.core.DecodingError, while a change to http.core.DecodingError can't break io.yaes.
- Position
- Below the diagonal: http.core.DecodingError uses a module listed above it, which is the healthy direction.
31→19 instances.RaiseInstances uses io.yaes✕
- Connections
- 1 pair of types, where a type in instances.RaiseInstances uses a type in io.yaes.
- The types involved
io.yaes.instances.RaiseInstances.RaiseMonadError→io.yaes.Raise
- Direction
- instances.RaiseInstances uses io.yaes, so a change to io.yaes can break instances.RaiseInstances, while a change to instances.RaiseInstances can't break io.yaes.
- Position
- Below the diagonal: instances.RaiseInstances uses a module listed above it, which is the healthy direction.
32→19 interop.catseffect uses io.yaes✕
- Connections
- 2 pairs of types, where a type in interop.catseffect uses a type in io.yaes.
- The types involved
io.yaes.interop.catseffect.SyncExecutor→io.yaes.Executorio.yaes.interop.catseffect.syncUnsafe→io.yaes.Executor
- Direction
- interop.catseffect uses io.yaes, so a change to io.yaes can break interop.catseffect, while a change to interop.catseffect can't break io.yaes.
- Position
- Below the diagonal: interop.catseffect uses a module listed above it, which is the healthy direction.
33→19 slf4j uses io.yaes✕
- Connections
- 3 pairs of types, where a type in slf4j uses a type in io.yaes.
- The types involved
io.yaes.slf4j.Slf4jLog→io.yaes.Logio.yaes.slf4j.Slf4jLogger→io.yaes.Logio.yaes.slf4j.Slf4jLogger→io.yaes.Logger
- Direction
- slf4j uses io.yaes, so a change to io.yaes can break slf4j, while a change to slf4j can't break io.yaes.
- Position
- Below the diagonal: slf4j uses a module listed above it, which is the healthy direction.
34→24 Log.Level uses Log✕
- Connections
- 6 pairs of types, where a type in Log.Level uses a type in Log.
- The types involved
io.yaes.Log.Level.Debug→io.yaes.Log.Levelio.yaes.Log.Level.Error→io.yaes.Log.Levelio.yaes.Log.Level.Fatal→io.yaes.Log.Levelio.yaes.Log.Level.Info→io.yaes.Log.Levelio.yaes.Log.Level.Trace→io.yaes.Log.Levelio.yaes.Log.Level.Warn→io.yaes.Log.Level
- Direction
- Log.Level uses Log, so a change to Log can break Log.Level, while a change to Log.Level can't break Log.
- Position
- Below the diagonal: Log.Level uses a module listed above it, which is the healthy direction.
35→25 Raise.LazyValue uses Raise✕
- Connections
- 2 pairs of types, where a type in Raise.LazyValue uses a type in Raise.
- The types involved
io.yaes.Raise.LazyValue.Empty→io.yaes.Raise.LazyValueio.yaes.Raise.LazyValue.Value→io.yaes.Raise.LazyValue
- Direction
- Raise.LazyValue uses Raise, so a change to Raise can break Raise.LazyValue, while a change to Raise.LazyValue can't break Raise.
- Position
- Below the diagonal: Raise.LazyValue uses a module listed above it, which is the healthy direction.
36→29 http.client.ConnectionError uses http.client✕
- Connections
- 4 pairs of types, where a type in http.client.ConnectionError uses a type in http.client.
- The types involved
io.yaes.http.client.ConnectionError.ConnectTimeout→io.yaes.http.client.ConnectionErrorio.yaes.http.client.ConnectionError.ConnectionRefused→io.yaes.http.client.ConnectionErrorio.yaes.http.client.ConnectionError.RequestTimeout→io.yaes.http.client.ConnectionErrorio.yaes.http.client.ConnectionError.Unexpected→io.yaes.http.client.ConnectionError
- Direction
- http.client.ConnectionError uses http.client, so a change to http.client can break http.client.ConnectionError, while a change to http.client.ConnectionError can't break http.client.
- Position
- Below the diagonal: http.client.ConnectionError uses a module listed above it, which is the healthy direction.
37→29 http.client.HttpError uses http.client✕
- Connections
- 16 pairs of types, where a type in http.client.HttpError uses a type in http.client.
- The types involved
io.yaes.http.client.HttpError.BadGateway→io.yaes.http.client.ServerHttpErrorio.yaes.http.client.HttpError.BadRequest→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.Conflict→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.Forbidden→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.GatewayTimeout→io.yaes.http.client.ServerHttpErrorio.yaes.http.client.HttpError.Gone→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.InternalServerError→io.yaes.http.client.ServerHttpErrorio.yaes.http.client.HttpError.MethodNotAllowed→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.NotFound→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.OtherClientError→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.OtherServerError→io.yaes.http.client.ServerHttpErrorio.yaes.http.client.HttpError.ServiceUnavailable→io.yaes.http.client.ServerHttpErrorio.yaes.http.client.HttpError.TooManyRequests→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.Unauthorized→io.yaes.http.client.ClientHttpErrorio.yaes.http.client.HttpError.UnexpectedStatus→io.yaes.http.client.HttpErrorio.yaes.http.client.HttpError.UnprocessableEntity→io.yaes.http.client.ClientHttpError
- Direction
- http.client.HttpError uses http.client, so a change to http.client can break http.client.HttpError, while a change to http.client.HttpError can't break http.client.
- Position
- Below the diagonal: http.client.HttpError uses a module listed above it, which is the healthy direction.
38→12 http.server uses http.core✕
- Connections
- 1 pair of types, where a type in http.server uses a type in http.core.
- The types involved
io.yaes.http.server.Request→io.yaes.http.core.Method
- Direction
- http.server uses http.core, so a change to http.core can break http.server, while a change to http.server can't break http.core.
- Position
- Below the diagonal: http.server uses a module listed above it, which is the healthy direction.
38→13 http.server uses http.server.params.path✕
- Connections
- 2 pairs of types, where a type in http.server uses a type in http.server.params.path.
- The types involved
io.yaes.http.server.PathBuilder→io.yaes.http.server.params.path.PathSegmentio.yaes.http.server.TypedParam→io.yaes.http.server.params.path.PathParamParser
- Direction
- http.server uses http.server.params.path, so a change to http.server.params.path can break http.server, while a change to http.server can't break http.server.params.path.
- Position
- Below the diagonal: http.server uses a module listed above it, which is the healthy direction.
38→14 http.server uses http.server.params.query✕
- Connections
- 2 pairs of types, where a type in http.server uses a type in http.server.params.query.
- The types involved
io.yaes.http.server.PathBuilder→io.yaes.http.server.params.query.QueryParamSpecio.yaes.http.server.PathBuilder→io.yaes.http.server.params.query.TypedQueryParam
- Direction
- http.server uses http.server.params.query, so a change to http.server.params.query can break http.server, while a change to http.server can't break http.server.params.query.
- Position
- Below the diagonal: http.server uses a module listed above it, which is the healthy direction.
38→18 http.server uses http.server.routing✕
- Connections
- 5 pairs of types, where a type in http.server uses a type in http.server.routing.
- The types involved
io.yaes.http.server.MethodBuilder→io.yaes.http.server.routing.PathPatternio.yaes.http.server.MethodBuilder→io.yaes.http.server.routing.Routeio.yaes.http.server.PathBuilder→io.yaes.http.server.routing.PathPatternio.yaes.http.server.Routes→io.yaes.http.server.routing.Routeio.yaes.http.server.YaesServer→io.yaes.http.server.routing.Route
- Direction
- http.server uses http.server.routing, so a change to http.server.routing can break http.server, while a change to http.server can't break http.server.routing.
- Position
- Below the diagonal: http.server uses a module listed above it, which is the healthy direction.
38→19 http.server uses io.yaes✕
- Connections
- 6 pairs of types, where a type in http.server uses a type in io.yaes.
- The types involved
io.yaes.http.server.ServerDef→io.yaes.Logio.yaes.http.server.ServerDef→io.yaes.Shutdownio.yaes.http.server.ServerDef→io.yaes.Syncio.yaes.http.server.YaesServer→io.yaes.Logio.yaes.http.server.YaesServer→io.yaes.Shutdownio.yaes.http.server.YaesServer→io.yaes.Sync
- Direction
- http.server uses io.yaes, so a change to io.yaes can break http.server, while a change to http.server can't break io.yaes.
- Position
- Below the diagonal: http.server uses a module listed above it, which is the healthy direction.
38→21 http.server uses Async✕
- Connections
- 3 pairs of types, where a type in http.server uses a type in Async.
- The types involved
io.yaes.http.server.ServerConfig→io.yaes.Async.Deadlineio.yaes.http.server.ServerDef→io.yaes.Async.Deadlineio.yaes.http.server.YaesServer→io.yaes.Async.Deadline
- Direction
- http.server uses Async, so a change to Async can break http.server, while a change to http.server can't break Async.
- Position
- Below the diagonal: http.server uses a module listed above it, which is the healthy direction.
39→38 http.server.parsing uses http.server✕
- Connections
- 3 pairs of types, where a type in http.server.parsing uses a type in http.server.
- The types involved
io.yaes.http.server.parsing.HttpParseError→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParser→io.yaes.http.server.ServerConfigio.yaes.http.server.parsing.HttpWriter→io.yaes.http.server.Response
- Direction
- http.server.parsing uses http.server, so a change to http.server can break http.server.parsing, while a change to http.server.parsing can't break http.server.
- Position
- Below the diagonal: http.server.parsing uses a module listed above it, which is the healthy direction.
40→38 http.server.parsing.HttpParseError uses http.server✕
- Connections
- 9 pairs of types, where a type in http.server.parsing.HttpParseError uses a type in http.server.
- The types involved
io.yaes.http.server.parsing.HttpParseError.InvalidContentLength→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParseError.MalformedHeaders→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParseError.MalformedPath→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParseError.MalformedQueryString→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParseError.MalformedRequestLine→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParseError.PayloadTooLarge→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParseError.UnexpectedEndOfStream→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParseError.UnsupportedHttpVersion→io.yaes.http.server.Responseio.yaes.http.server.parsing.HttpParseError.UnsupportedMethod→io.yaes.http.server.Response
- Direction
- http.server.parsing.HttpParseError uses http.server, so a change to http.server can break http.server.parsing.HttpParseError, while a change to http.server.parsing.HttpParseError can't break http.server.
- Position
- Below the diagonal: http.server.parsing.HttpParseError uses a module listed above it, which is the healthy direction.
40→39 http.server.parsing.HttpParseError uses http.server.parsing✕
- Connections
- 9 pairs of types, where a type in http.server.parsing.HttpParseError uses a type in http.server.parsing.
- The types involved
io.yaes.http.server.parsing.HttpParseError.InvalidContentLength→io.yaes.http.server.parsing.HttpParseErrorio.yaes.http.server.parsing.HttpParseError.MalformedHeaders→io.yaes.http.server.parsing.HttpParseErrorio.yaes.http.server.parsing.HttpParseError.MalformedPath→io.yaes.http.server.parsing.HttpParseErrorio.yaes.http.server.parsing.HttpParseError.MalformedQueryString→io.yaes.http.server.parsing.HttpParseErrorio.yaes.http.server.parsing.HttpParseError.MalformedRequestLine→io.yaes.http.server.parsing.HttpParseErrorio.yaes.http.server.parsing.HttpParseError.PayloadTooLarge→io.yaes.http.server.parsing.HttpParseErrorio.yaes.http.server.parsing.HttpParseError.UnexpectedEndOfStream→io.yaes.http.server.parsing.HttpParseErrorio.yaes.http.server.parsing.HttpParseError.UnsupportedHttpVersion→io.yaes.http.server.parsing.HttpParseErrorio.yaes.http.server.parsing.HttpParseError.UnsupportedMethod→io.yaes.http.server.parsing.HttpParseError
- Direction
- http.server.parsing.HttpParseError uses http.server.parsing, so a change to http.server.parsing can break http.server.parsing.HttpParseError, while a change to http.server.parsing.HttpParseError can't break http.server.parsing.
- Position
- Below the diagonal: http.server.parsing.HttpParseError 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 | 11 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it; Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.0 pts | Medium | Architecture documentation |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.6 pts | Medium | Nullable reference types |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.7 pts | Low | Project Cohesion |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +1.1 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.1 pts | Medium | Release Hygiene |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +1.0 pts | Medium | Security & performance tooling |
| Reconcile the README with reality: README.md links to `docs/yaes-app.md`, but `docs/yaes-app.md` does not exist. | +0.7 pts | Medium | Documentation accuracy |
| Swallowed exception (empty catch) | +0.6 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| yaes-data/src/main/scala/io/yaes/FlowPublisher.scala | 7.8 | Near-clean | Cyclomatic Complexity: FlowPublisher.subscribe (cyclomatic 20) |
| yaes-core/src/test/scala/io/yaes/AsyncSpec.scala | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| yaes-core/src/main/scala/io/yaes/Retry.scala | 8.5 | Near-clean | Cognitive Complexity: Schedule.exponential (cognitive 21) |
| yaes-http/server/src/main/scala/io/yaes/http/server/parsing/HttpParser.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (28 lines × 2) |
| yaes-data/src/main/scala/io/yaes/Channel.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (12–14 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 59 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 — 59 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, 28 of 36 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — 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 source is present (.scala) and this repository declares an sbt build (repository root, 120 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/ch/epfl/scala/scalafix-core_3/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- 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. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 1187 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 3 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (project/plugins.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `yaes-core/src/main/scala/io/yaes/CircuitBreaker.scala`, `yaes-core/src/main/scala/io/yaes/Raise.scala`, `yaes-core/src/main/scala/io/yaes/Reader.scala`, `yaes-core/src/main/scala/io/yaes/System.scala`, `yaes-core/src/main/scala/io/yaes/Writer.scala`, … (+5 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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 DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FlowPublisher.subscribe at 20. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being HttpError.fromStatus at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: yaes-http/client/src/main/scala/io/yaes/http/client/HttpError.scala (HttpError.fromStatus at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with FlowPublisher.subscribe (cyclomatic 20). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was FlowPublisher.subscribe at 22.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with FlowPublisher.subscribe (cognitive 22), Schedule.exponential (cognitive 21). — 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.4 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
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (28 lines × 2) finding(s) in Code Duplication — start with HttpParser.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (12–14 lines × 2) finding(s) in Code Duplication — start with Channel.scala. — 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
15 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 8 of the 15 (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 4 classes have LCOM4 above 3.
D9 · Test Distribution
1230 test methods: 1179 unit, 51 integration, 0 BDD, 0 e2e. The Scala suite contributes 1230 test case(s) across 81 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted task-comment markers across 12751 LoC (0.0/KLoC) → score 10.0. 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 1 FixmeComment finding(s) in Explicit Debt — start with AsyncSpec.scala. — One of this dimension's main actionable groups (1 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. 34 document(s) read across 2 unit(s).
D26 · Project Cohesion
1 of 1 build units (sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 11 high, 0 medium, 0 low. 10 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 9 file(s) — `yaes-core/src/main/scala/io/yaes/CircuitBreaker.scala`, `yaes-core/src/main/scala/io/yaes/Raise.scala`, `yaes-core/src/main/scala/io/yaes/Reader.scala`, `yaes-core/src/main/scala/io/yaes/Writer.scala`, `yaes-data/src/main/scala/io/yaes/Channel.scala`, … (+4 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- 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 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
8 finding(s): 0 critical, 7 high, 1 medium, 0 low.
What to do
- Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 49 of the 76 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `docs/yaes-app.md`, but `docs/yaes-app.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:199
What to do
- Reconcile the README with reality: README.md links to `docs/yaes-app.md`, but `docs/yaes-app.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
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
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — yaes-core/src/main/scala/io/yaes/Async.scala:198
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 74 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 68% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Strong | Largest drag on the score — prioritise here. |
| Security | 71% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 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.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 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 Scala 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.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- 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 — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~17354 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 8 pinned sbt dependency coordinate(s) were read from its 1 sbt build file(s), but Maven Central could not be asked for the licence of 6 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/ch/epfl/scala/scalafix-core_3/0.14.3/scalafix-core_3-0.14.3.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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 — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 59 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 74 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository builds on an HTTP-server library (build.sbt:134 — depends on `yaes-http-server`) but serves no HTTP of its own: its production source starts no server (no `newServerAt`/`bindAndHandle`, server builder, `Server.serve`, `Http.serve`, tapir server interpreter or Netty HTTP pipeline), declares no application one runs (no Play application, servlet, cask `MainRoutes`, `HttpApp` or twitter-server), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 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 Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
- 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 — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 11 finding(s)
- FlowPublisher.subscribe (cyclomatic 20) yaes-data/src/main/scala/io/yaes/FlowPublisher.scala:48
- FixmeComment yaes-core/src/test/scala/io/yaes/AsyncSpec.scala:267
- FlowPublisher.subscribe (cognitive 22) yaes-data/src/main/scala/io/yaes/FlowPublisher.scala:48
- Schedule.exponential (cognitive 21) yaes-core/src/main/scala/io/yaes/Retry.scala:86
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (28 lines × 2) yaes-http/server/src/main/scala/io/yaes/http/server/parsing/HttpParser.scala:105
- Duplicated block (12–14 lines × 2) yaes-data/src/main/scala/io/yaes/Channel.scala:630
- Coverage collected but not gated
- Swallowed exception (empty catch) yaes-core/src/main/scala/io/yaes/Async.scala:198
Minor — 7 finding(s)
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- README/code drift README.md:199
- No changelog
- Scala's null is not held to the type system everywhere
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-42d82030f2bb46eab1734e4f44d55b6e/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-42d82030f2bb46eab1734e4f44d55b6e/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 . | 11 | 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 | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | 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. semgrep could not parse 10 file(s) — `yaes-core/src/main/scala/io/yaes/CircuitBreaker.scala`, `yaes-core/src/main/scala/io/yaes/Raise.scala`, `yaes-core/src/main/scala/io/yaes/Reader.scala`, `yaes-core/src/main/scala/io/yaes/System.scala`, `yaes-core/src/main/scala/io/yaes/Writer.scala`, … (+5 more) — so the PII/GDPR sweep did not cover them at all. | 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 |