Executive summary
wvlet/airframe falls short of our standard for production because the documentation refers to two links that don't exist. It scores 63 out of 100 and is rated Adequate, and 90 of its 93 critical findings are security problems.
Maturity, at 60, is the weakest lens and counts most in the score. The best first step is replacing the three packages under a banned licence, worth about 3 points. Recording design decisions would lift Maturity itself, also worth about 3. Raising Maturity to 70 would lift the score to about 65.
Eighty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six secrets can leak from the build pipeline, and two passwords or keys are open to anyone who can read the repository. Pinning each tool to an exact version, limiting each secret to its own step and replacing each exposed password or key would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and fixing the weaknesses the scanner points to would deal with the security weakness in the code. The three packages under a licence on your banned list need replacing, or clearing with your legal team.
The product code is 58,805 lines, about €120,000 to rebuild.
If Maturity rose from 60 to 70, the lowest score rated Strong, the score would rise from 63 to about 65.
New since the last survey: 7 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 9 findings
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-node-runtime-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-node-runtime-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-node-runtime-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-node-runtime-in-workflow REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] pnpm-lock.yaml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] pnpm-lock.yaml
- Supply-chain Provenance & Signing · Workflow holding a long-lived secret is unscoped
- Documentation (README) · README may be stale
Rebuild cost: about €120,000 · Estimate
| Cost to rebuild | €40,000 to €200,000, for 666 to 2,112 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 58,805 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 airframe.surface.Primitive | 2 airframe.control.Retry | 3 airframe.http.RPCEncoding | 4 airframe.log | 5 airframe.rx.html.widget.editor.monaco | 6 airframe.control | 7 airframe.metrics | 8 airframe.msgpack.spi | 9 airframe.sql.model | 10 airframe.surface.reflect | 11 airframe.launcher | 12 airframe.sql.model.Expression | 13 airframe.launcher.StringTree | 14 airframe.sql.catalog | 15 airframe.rx.html | 16 airframe.sql.analyzer | 17 airframe.rx | 18 airframe.sql.model.LogicalPlan | 19 airframe.surface | 20 airframe.http.openapi.OpenAPI | 21 airframe.lifecycle | 22 airframe.http.HttpMessage | 23 airframe.parquet | 24 airframe.tracing | 25 airframe.http.Http | 26 airframe.codec | 27 airframe.http.client | 28 airframe.http.router | 29 airframe.http.finagle | 30 airframe.http | 31 airframe | 32 airframe.http.codegen | 33 airframe.http.internal | 34 airframe.http.grpc.internal | 35 airframe.http.netty | 36 airspec.spi | 37 airframe.http.grpc | 38 airframe.http.recorder | 39 airspec | 40 airspec.runner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 airframe.surface.Primitive | 1 | |||||||||||||||||||||||||||||||||||||||
| 2 airframe.control.Retry | 11 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 3 airframe.http.RPCEncoding | 4 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 4 airframe.log | 36 | |||||||||||||||||||||||||||||||||||||||
| 5 airframe.rx.html.widget.editor.monaco | 35 | |||||||||||||||||||||||||||||||||||||||
| 6 airframe.control | 40 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 7 airframe.metrics | 21 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 airframe.msgpack.spi | 103 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 airframe.sql.model | 22 | 3 | 1 | 4 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 10 airframe.surface.reflect | 16 | 12 | 18 | 2 | ||||||||||||||||||||||||||||||||||||
| 11 airframe.launcher | 18 | 5 | 2 | 3 | 5 | 3 | ||||||||||||||||||||||||||||||||||
| 12 airframe.sql.model.Expression | 109 | 1 | 217 | 3 | 18 | |||||||||||||||||||||||||||||||||||
| 13 airframe.launcher.StringTree | 2 | 4 | 4 | |||||||||||||||||||||||||||||||||||||
| 14 airframe.sql.catalog | 13 | 2 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 15 airframe.rx.html | 15 | 5 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 16 airframe.sql.analyzer | 13 | 6 | 12 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 17 airframe.rx | 25 | 2 | 5 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 18 airframe.sql.model.LogicalPlan | 38 | 2 | 2 | 89 | 30 | 36 | ||||||||||||||||||||||||||||||||||
| 19 airframe.surface | 45 | 1 | 2 | 8 | 1 | |||||||||||||||||||||||||||||||||||
| 20 airframe.http.openapi.OpenAPI | 15 | 8 | ||||||||||||||||||||||||||||||||||||||
| 21 airframe.lifecycle | 17 | 2 | 7 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 airframe.http.HttpMessage | 25 | 1 | 3 | 19 | ||||||||||||||||||||||||||||||||||||
| 23 airframe.parquet | 34 | 7 | 14 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 24 airframe.tracing | 8 | 3 | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 25 airframe.http.Http | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 26 airframe.codec | 46 | 1 | 8 | 39 | 1 | 11 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 27 airframe.http.client | 27 | 5 | 7 | 5 | 7 | 3 | 11 | 11 | 1 | 33 | ||||||||||||||||||||||||||||||
| 28 airframe.http.router | 8 | 5 | 1 | 1 | 1 | 1 | 9 | 1 | 1 | 5 | 13 | 5 | ||||||||||||||||||||||||||||
| 29 airframe.http.finagle | 25 | 2 | 6 | 1 | 2 | 11 | 14 | 1 | 4 | 2 | 4 | 25 | 4 | |||||||||||||||||||||||||||
| 30 airframe.http | 98 | 1 | 3 | 3 | 3 | 5 | 3 | 5 | 10 | 16 | 5 | 7 | 3 | 4 | 1 | 1 | ||||||||||||||||||||||||
| 31 airframe | 28 | 7 | 5 | 4 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 airframe.http.codegen | 8 | 4 | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||
| 33 airframe.http.internal | 10 | 2 | 4 | 1 | 1 | 2 | 2 | 4 | 11 | |||||||||||||||||||||||||||||||
| 34 airframe.http.grpc.internal | 8 | 6 | 6 | 2 | 2 | 1 | 1 | 2 | 6 | |||||||||||||||||||||||||||||||
| 35 airframe.http.netty | 21 | 5 | 1 | 2 | 2 | 6 | 1 | 2 | 3 | 19 | 2 | 1 | ||||||||||||||||||||||||||||
| 36 airspec.spi | 17 | 1 | 8 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 airframe.http.grpc | 10 | 2 | 7 | 3 | 3 | 6 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 38 airframe.http.recorder | 13 | 2 | 3 | 3 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 39 airspec | 22 | 2 | 7 | 1 | 1 | 19 | 11 | |||||||||||||||||||||||||||||||||
| 40 airspec.runner | 19 | 7 | 3 | 2 | 4 |
1→19 airframe.surface.Primitive uses airframe.surface part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.surface.Primitive uses a type in airframe.surface.
- The types involved
wvlet.airframe.surface.Primitive.PrimitiveSurface→wvlet.airframe.surface.GenericSurface
- Direction
- airframe.surface.Primitive uses airframe.surface, so a change to airframe.surface can break airframe.surface.Primitive, while a change to airframe.surface.Primitive can't break airframe.surface.
- 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.
2→1 airframe.control.Retry uses airframe.surface.Primitive✕
- Connections
- 11 pairs of types, where a type in airframe.control.Retry uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.control.Retry.ExponentialBackOff→wvlet.airframe.surface.Primitive.Intwvlet.airframe.control.Retry.ExtraWait→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.control.Retry.ExtraWait→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.control.Retry.ExtraWait→wvlet.airframe.surface.Primitive.Intwvlet.airframe.control.Retry.Jitter→wvlet.airframe.surface.Primitive.Intwvlet.airframe.control.Retry.RetryContext→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.control.Retry.RetryContext→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.control.Retry.RetryContext→wvlet.airframe.surface.Primitive.Intwvlet.airframe.control.Retry.RetryPolicy→wvlet.airframe.surface.Primitive.Intwvlet.airframe.control.Retry.RetryPolicyConfig→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.control.Retry.RetryPolicyConfig→wvlet.airframe.surface.Primitive.Int
- Direction
- airframe.control.Retry uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.control.Retry, while a change to airframe.control.Retry can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.control.Retry uses a module listed above it, which is the healthy direction.
2→6 airframe.control.Retry uses airframe.control part of a loop✕
- Connections
- 2 pairs of types, where a type in airframe.control.Retry uses a type in airframe.control.
- The types involved
wvlet.airframe.control.Retry.RetryContext→wvlet.airframe.control.CircuitBreakerwvlet.airframe.control.Retry.RetryContext→wvlet.airframe.control.ResultClass
- Direction
- airframe.control.Retry uses airframe.control, so a change to airframe.control can break airframe.control.Retry, while a change to airframe.control.Retry can't break airframe.control.
- 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.
2→17 airframe.control.Retry uses airframe.rx part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.control.Retry uses a type in airframe.rx.
- The types involved
wvlet.airframe.control.Retry.RetryContext→wvlet.airframe.rx.Rx
- Direction
- airframe.control.Retry uses airframe.rx, so a change to airframe.rx can break airframe.control.Retry, while a change to airframe.control.Retry can't break airframe.rx.
- 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.
3→1 airframe.http.RPCEncoding uses airframe.surface.Primitive✕
- Connections
- 4 pairs of types, where a type in airframe.http.RPCEncoding uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.RPCEncoding.JSON→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.RPCEncoding.JSON→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.RPCEncoding.MsgPack→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.RPCEncoding.MsgPack→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.http.RPCEncoding uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.RPCEncoding, while a change to airframe.http.RPCEncoding can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.RPCEncoding uses a module listed above it, which is the healthy direction.
3→8 airframe.http.RPCEncoding uses airframe.msgpack.spi part of a loop✕
- Connections
- 2 pairs of types, where a type in airframe.http.RPCEncoding uses a type in airframe.msgpack.spi.
- The types involved
wvlet.airframe.http.RPCEncoding.JSON→wvlet.airframe.msgpack.spi.Valuewvlet.airframe.http.RPCEncoding.MsgPack→wvlet.airframe.msgpack.spi.Value
- Direction
- airframe.http.RPCEncoding uses airframe.msgpack.spi, so a change to airframe.msgpack.spi can break airframe.http.RPCEncoding, while a change to airframe.http.RPCEncoding can't break airframe.msgpack.spi.
- 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.
3→26 airframe.http.RPCEncoding uses airframe.codec part of a loop✕
- Connections
- 2 pairs of types, where a type in airframe.http.RPCEncoding uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.RPCEncoding.JSON→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.RPCEncoding.MsgPack→wvlet.airframe.codec.MessageCodec
- Direction
- airframe.http.RPCEncoding uses airframe.codec, so a change to airframe.codec can break airframe.http.RPCEncoding, while a change to airframe.http.RPCEncoding can't break airframe.codec.
- 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.
3→30 airframe.http.RPCEncoding uses airframe.http part of a loop✕
- Connections
- 2 pairs of types, where a type in airframe.http.RPCEncoding uses a type in airframe.http.
- The types involved
wvlet.airframe.http.RPCEncoding.JSON→wvlet.airframe.http.RPCEncodingwvlet.airframe.http.RPCEncoding.MsgPack→wvlet.airframe.http.RPCEncoding
- Direction
- airframe.http.RPCEncoding uses airframe.http, so a change to airframe.http can break airframe.http.RPCEncoding, while a change to airframe.http.RPCEncoding can't break airframe.http.
- 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.
4→1 airframe.log uses airframe.surface.Primitive✕
- Connections
- 36 pairs of types, where a type in airframe.log uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.log.AirframeLogManager→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.log.AsyncHandler→wvlet.airframe.surface.Primitive.Intwvlet.airframe.log.AsyncHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.log.BufferedLogHandler→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.BufferedLogHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.log.ConsoleLogHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.log.JSConsoleLogHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.log.JSLogger→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.log.JSLogger→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogEnv→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.log.LogEnv→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogEnv→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.log.LogEnvBase→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.log.LogEnvBase→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogEnvBase→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.log.LogFormatter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogLevel→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogLevelScanner→wvlet.airframe.surface.Primitive.Longwvlet.airframe.log.LogLevelScanner→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogLevelScanner→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.log.LogLevelScannerConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogRecord→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogSource→wvlet.airframe.surface.Primitive.Intwvlet.airframe.log.LogSource→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.log.LogTimestampFormatter→wvlet.airframe.surface.Primitive.Long
- Direction
- airframe.log uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.log, while a change to airframe.log can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.log uses a module listed above it, which is the healthy direction.
5→1 airframe.rx.html.widget.editor.monaco uses airframe.surface.Primitive✕
- Connections
- 35 pairs of types, where a type in airframe.rx.html.widget.editor.monaco uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.rx.html.widget.editor.monaco.CancellationToken→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.widget.editor.monaco.CancellationTokenSource→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.widget.editor.monaco.CancellationTokenSource→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.html.widget.editor.monaco.Emitter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.html.widget.editor.monaco.Environment→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.widget.editor.monaco.IDisposable→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.html.widget.editor.monaco.IKeyboardEvent→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.widget.editor.monaco.IKeyboardEvent→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.rx.html.widget.editor.monaco.IKeyboardEvent→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.widget.editor.monaco.IKeyboardEvent→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.html.widget.editor.monaco.IMarkdownString→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.widget.editor.monaco.IMarkdownString→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.widget.editor.monaco.IMouseEvent→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.widget.editor.monaco.IMouseEvent→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.rx.html.widget.editor.monaco.IMouseEvent→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.html.widget.editor.monaco.IPosition→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.rx.html.widget.editor.monaco.IRange→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.rx.html.widget.editor.monaco.IScrollEvent→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.widget.editor.monaco.IScrollEvent→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.rx.html.widget.editor.monaco.ISelection→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.rx.html.widget.editor.monaco.Position→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.widget.editor.monaco.Position→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.rx.html.widget.editor.monaco.Position→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.widget.editor.monaco.Range→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.widget.editor.monaco.Range→wvlet.airframe.surface.Primitive.Double
- Direction
- airframe.rx.html.widget.editor.monaco uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.rx.html.widget.editor.monaco, while a change to airframe.rx.html.widget.editor.monaco can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.rx.html.widget.editor.monaco uses a module listed above it, which is the healthy direction.
6→1 airframe.control uses airframe.surface.Primitive✕
- Connections
- 40 pairs of types, where a type in airframe.control uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.control.CircuitBreaker→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.control.CircuitBreaker→wvlet.airframe.surface.Primitive.Intwvlet.airframe.control.CircuitBreaker→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.control.CircuitBreakerContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.control.CircuitBreakerRecoveryPolicy→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.control.CircuitBreakerRecoveryPolicy→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.control.CommandLineTokenizer→wvlet.airframe.surface.Primitive.Intwvlet.airframe.control.CommandLineTokenizer→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.control.Compat→wvlet.airframe.surface.Primitive.Longwvlet.airframe.control.Compat→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.control.Control→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.control.HealthCheckPolicy→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.control.HealthCheckPolicy→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.control.IO→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.control.IO→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.control.IO→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.control.ManualTicker→wvlet.airframe.surface.Primitive.Longwvlet.airframe.control.ManualTicker→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.control.MultipleExceptions→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.control.OS→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.control.OS→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.control.Parallel→wvlet.airframe.surface.Primitive.Intwvlet.airframe.control.Parallel→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.control.RateLimitExceededException→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.control.RateLimiter→wvlet.airframe.surface.Primitive.Boolean
- Direction
- airframe.control uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.control, while a change to airframe.control can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.control uses a module listed above it, which is the healthy direction.
6→2 airframe.control uses airframe.control.Retry✕
- Connections
- 1 pair of types, where a type in airframe.control uses a type in airframe.control.Retry.
- The types involved
wvlet.airframe.control.Retry→wvlet.airframe.control.Retry.RetryContext
- Direction
- airframe.control uses airframe.control.Retry, so a change to airframe.control.Retry can break airframe.control, while a change to airframe.control can't break airframe.control.Retry.
- Position
- Below the diagonal: airframe.control uses a module listed above it, which is the healthy direction.
6→4 airframe.control uses airframe.log✕
- Connections
- 5 pairs of types, where a type in airframe.control uses a type in airframe.log.
- The types involved
wvlet.airframe.control.CircuitBreaker→wvlet.airframe.log.LogSupportwvlet.airframe.control.CommandLineTokenizer→wvlet.airframe.log.LogSupportwvlet.airframe.control.Parallel→wvlet.airframe.log.LogSupportwvlet.airframe.control.Retry→wvlet.airframe.log.LogSupportwvlet.airframe.control.Shell→wvlet.airframe.log.LogSupport
- Direction
- airframe.control uses airframe.log, so a change to airframe.log can break airframe.control, while a change to airframe.control can't break airframe.log.
- Position
- Below the diagonal: airframe.control uses a module listed above it, which is the healthy direction.
7→1 airframe.metrics uses airframe.surface.Primitive✕
- Connections
- 21 pairs of types, where a type in airframe.metrics uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.metrics.Count→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.metrics.Count→wvlet.airframe.surface.Primitive.Intwvlet.airframe.metrics.Count→wvlet.airframe.surface.Primitive.Longwvlet.airframe.metrics.Count→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.metrics.DataSize→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.metrics.DataSize→wvlet.airframe.surface.Primitive.Longwvlet.airframe.metrics.DataSize→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.metrics.ElapsedTime→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.metrics.ElapsedTime→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.metrics.TimeParser→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.metrics.TimeStampFormatter→wvlet.airframe.surface.Primitive.Longwvlet.airframe.metrics.TimeStampFormatter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.metrics.TimeVector→wvlet.airframe.surface.Primitive.Longwvlet.airframe.metrics.TimeVector→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.metrics.TimeWindow→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.metrics.TimeWindow→wvlet.airframe.surface.Primitive.Longwvlet.airframe.metrics.TimeWindowBuilder→wvlet.airframe.surface.Primitive.Longwvlet.airframe.metrics.TimeWindowBuilder→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.metrics.TimeWindowUnit→wvlet.airframe.surface.Primitive.Intwvlet.airframe.metrics.TimeWindowUnit→wvlet.airframe.surface.Primitive.Longwvlet.airframe.metrics.TimeWindowUnit→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.metrics uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.metrics, while a change to airframe.metrics can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.metrics uses a module listed above it, which is the healthy direction.
7→4 airframe.metrics uses airframe.log✕
- Connections
- 2 pairs of types, where a type in airframe.metrics uses a type in airframe.log.
- The types involved
wvlet.airframe.metrics.TimeParser→wvlet.airframe.log.LogSupportwvlet.airframe.metrics.TimeWindowBuilder→wvlet.airframe.log.LogSupport
- Direction
- airframe.metrics uses airframe.log, so a change to airframe.log can break airframe.metrics, while a change to airframe.metrics can't break airframe.log.
- Position
- Below the diagonal: airframe.metrics uses a module listed above it, which is the healthy direction.
8→1 airframe.msgpack.spi uses airframe.surface.Primitive✕
- Connections
- 103 pairs of types, where a type in airframe.msgpack.spi uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.msgpack.spi.Buffer→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.msgpack.spi.Buffer→wvlet.airframe.surface.Primitive.Intwvlet.airframe.msgpack.spi.Buffer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.msgpack.spi.BufferPacker→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.msgpack.spi.BufferPacker→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.msgpack.spi.Code→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.msgpack.spi.Code→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.msgpack.spi.Compat→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.msgpack.spi.Compat→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.msgpack.spi.Compat→wvlet.airframe.surface.Primitive.Floatwvlet.airframe.msgpack.spi.Compat→wvlet.airframe.surface.Primitive.Intwvlet.airframe.msgpack.spi.Compat→wvlet.airframe.surface.Primitive.Longwvlet.airframe.msgpack.spi.ExtTypeHeader→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.msgpack.spi.ExtTypeHeader→wvlet.airframe.surface.Primitive.Intwvlet.airframe.msgpack.spi.InsufficientBufferException→wvlet.airframe.surface.Primitive.Longwvlet.airframe.msgpack.spi.IntegerOverflowException→wvlet.airframe.surface.Primitive.BigIntegerwvlet.airframe.msgpack.spi.MessageException→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.msgpack.spi.MessagePack→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.msgpack.spi.MessagePack→wvlet.airframe.surface.Primitive.Intwvlet.airframe.msgpack.spi.MessagePack→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.msgpack.spi.MessageSink→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.msgpack.spi.MessageSink→wvlet.airframe.surface.Primitive.Intwvlet.airframe.msgpack.spi.MessageSink→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.msgpack.spi.MessageSource→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.msgpack.spi.OffsetPacker→wvlet.airframe.surface.Primitive.BigInteger
- Direction
- airframe.msgpack.spi uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.msgpack.spi, while a change to airframe.msgpack.spi can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.msgpack.spi uses a module listed above it, which is the healthy direction.
8→3 airframe.msgpack.spi uses airframe.http.RPCEncoding✕
- Connections
- 1 pair of types, where a type in airframe.msgpack.spi uses a type in airframe.http.RPCEncoding.
- The types involved
wvlet.airframe.msgpack.spi.MessagePack→wvlet.airframe.http.RPCEncoding.MsgPack
- Direction
- airframe.msgpack.spi uses airframe.http.RPCEncoding, so a change to airframe.http.RPCEncoding can break airframe.msgpack.spi, while a change to airframe.msgpack.spi can't break airframe.http.RPCEncoding.
- Position
- Below the diagonal: airframe.msgpack.spi uses a module listed above it, which is the healthy direction.
9→1 airframe.sql.model uses airframe.surface.Primitive✕
- Connections
- 22 pairs of types, where a type in airframe.sql.model uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.sql.model.Attribute→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.Attribute→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.BinaryExpression→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.CTERelationRef→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.ColumnPath→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.Expression→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.sql.model.LogicalPlan→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.LogicalPlan→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.sql.model.LogicalPlanPrinter→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.model.LogicalPlanPrinter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlanPrinter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.sql.model.NodeLocation→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.model.ResolvedAttribute→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.ResolvedGroupingKey→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.ResolvedGroupingKey→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.model.ResolvedGroupingKey→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.SQLSig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.SourceColumn→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.TableScan→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.sql.model uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.sql.model, while a change to airframe.sql.model can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.sql.model uses a module listed above it, which is the healthy direction.
9→4 airframe.sql.model uses airframe.log✕
- Connections
- 3 pairs of types, where a type in airframe.sql.model uses a type in airframe.log.
- The types involved
wvlet.airframe.sql.model.Attribute→wvlet.airframe.log.LogSupportwvlet.airframe.sql.model.LogicalPlanPrinter→wvlet.airframe.log.LogSupportwvlet.airframe.sql.model.ResolvedAttribute→wvlet.airframe.log.LogSupport
- Direction
- airframe.sql.model uses airframe.log, so a change to airframe.log can break airframe.sql.model, while a change to airframe.sql.model can't break airframe.log.
- Position
- Below the diagonal: airframe.sql.model uses a module listed above it, which is the healthy direction.
9→12 airframe.sql.model uses airframe.sql.model.Expression part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.sql.model uses a type in airframe.sql.model.Expression.
- The types involved
wvlet.airframe.sql.model.ResolvedGroupingKey→wvlet.airframe.sql.model.Expression.GroupingKey
- Direction
- airframe.sql.model uses airframe.sql.model.Expression, so a change to airframe.sql.model.Expression can break airframe.sql.model, while a change to airframe.sql.model can't break airframe.sql.model.Expression.
- 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.
9→16 airframe.sql.model uses airframe.sql.analyzer part of a loop✕
- Connections
- 4 pairs of types, where a type in airframe.sql.model uses a type in airframe.sql.analyzer.
- The types involved
wvlet.airframe.sql.model.Attribute→wvlet.airframe.sql.analyzer.AnalyzerContextwvlet.airframe.sql.model.CTERelationRef→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.SQLSig→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.TableScan→wvlet.airframe.sql.analyzer.QuerySignatureConfig
- Direction
- airframe.sql.model uses airframe.sql.analyzer, so a change to airframe.sql.analyzer can break airframe.sql.model, while a change to airframe.sql.model can't break airframe.sql.analyzer.
- 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.
9→18 airframe.sql.model uses airframe.sql.model.LogicalPlan part of a loop✕
- Connections
- 2 pairs of types, where a type in airframe.sql.model uses a type in airframe.sql.model.LogicalPlan.
- The types involved
wvlet.airframe.sql.model.CTERelationRef→wvlet.airframe.sql.model.LogicalPlan.Relationwvlet.airframe.sql.model.TableScan→wvlet.airframe.sql.model.LogicalPlan.Relation
- Direction
- airframe.sql.model uses airframe.sql.model.LogicalPlan, so a change to airframe.sql.model.LogicalPlan can break airframe.sql.model, while a change to airframe.sql.model can't break airframe.sql.model.LogicalPlan.
- 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.
9→26 airframe.sql.model uses airframe.codec part of a loop✕
- Connections
- 2 pairs of types, where a type in airframe.sql.model uses a type in airframe.codec.
- The types involved
wvlet.airframe.sql.model.Expression→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.ResolvedAttribute→wvlet.airframe.codec.DataType
- Direction
- airframe.sql.model uses airframe.codec, so a change to airframe.codec can break airframe.sql.model, while a change to airframe.sql.model can't break airframe.codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 airframe.surface.reflect uses airframe.surface.Primitive✕
- Connections
- 16 pairs of types, where a type in airframe.surface.reflect uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.surface.reflect.GenericBuilder→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.reflect.GenericBuilder→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.surface.reflect.MethodCallBuilder→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.reflect.Path→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.reflect.ReflectMethodSurface→wvlet.airframe.surface.Primitive.Intwvlet.airframe.surface.reflect.ReflectMethodSurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.reflect.ReflectSurfaceFactory→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.reflect.ReflectSurfaceFactory→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.reflect.ReflectTypeUtil→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.reflect.RuntimeMethodParameter→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.reflect.RuntimeMethodParameter→wvlet.airframe.surface.Primitive.Intwvlet.airframe.surface.reflect.RuntimeMethodParameter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.reflect.SimpleObjectBuilder→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.reflect.StandardBuilder→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.reflect.StandardBuilder→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.reflect.StandardBuilder→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.surface.reflect uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.surface.reflect, while a change to airframe.surface.reflect can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.surface.reflect uses a module listed above it, which is the healthy direction.
10→4 airframe.surface.reflect uses airframe.log✕
- Connections
- 12 pairs of types, where a type in airframe.surface.reflect uses a type in airframe.log.
- The types involved
wvlet.airframe.surface.reflect.MethodCallBuilder→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.ObjectBuilder→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.Path→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.ReflectMethodSurface→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.ReflectSurfaceFactory→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.ReflectTypeUtil→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.RuntimeGenericSurface→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.RuntimeMethodParameter→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.RuntimeSurface→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.SimpleObjectBuilder→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.StandardBuilder→wvlet.airframe.log.LogSupportwvlet.airframe.surface.reflect.TypeConverter→wvlet.airframe.log.LogSupport
- Direction
- airframe.surface.reflect uses airframe.log, so a change to airframe.log can break airframe.surface.reflect, while a change to airframe.surface.reflect can't break airframe.log.
- Position
- Below the diagonal: airframe.surface.reflect uses a module listed above it, which is the healthy direction.
10→19 airframe.surface.reflect uses airframe.surface part of a loop✕
- Connections
- 18 pairs of types, where a type in airframe.surface.reflect uses a type in airframe.surface.
- The types involved
wvlet.airframe.surface.reflect.MethodCallBuilder→wvlet.airframe.surface.MethodParameterwvlet.airframe.surface.reflect.ObjectBuilder→wvlet.airframe.surface.Surfacewvlet.airframe.surface.reflect.ReflectMethodSurface→wvlet.airframe.surface.MethodParameterwvlet.airframe.surface.reflect.ReflectMethodSurface→wvlet.airframe.surface.MethodSurfacewvlet.airframe.surface.reflect.ReflectMethodSurface→wvlet.airframe.surface.Surfacewvlet.airframe.surface.reflect.ReflectSurfaceFactory→wvlet.airframe.surface.MethodSurfacewvlet.airframe.surface.reflect.ReflectSurfaceFactory→wvlet.airframe.surface.Surfacewvlet.airframe.surface.reflect.ReflectSurfaceFactory→wvlet.airframe.surface.TypeNamewvlet.airframe.surface.reflect.ReflectTypeUtil→wvlet.airframe.surface.Surfacewvlet.airframe.surface.reflect.RuntimeGenericSurface→wvlet.airframe.surface.GenericSurfacewvlet.airframe.surface.reflect.RuntimeGenericSurface→wvlet.airframe.surface.ObjectFactorywvlet.airframe.surface.reflect.RuntimeGenericSurface→wvlet.airframe.surface.Surfacewvlet.airframe.surface.reflect.RuntimeMethodParameter→wvlet.airframe.surface.MethodParameterwvlet.airframe.surface.reflect.RuntimeMethodParameter→wvlet.airframe.surface.MethodRefwvlet.airframe.surface.reflect.RuntimeMethodParameter→wvlet.airframe.surface.Surfacewvlet.airframe.surface.reflect.RuntimeSurface→wvlet.airframe.surface.Surfacewvlet.airframe.surface.reflect.StandardBuilder→wvlet.airframe.surface.Surfacewvlet.airframe.surface.reflect.TypeConverter→wvlet.airframe.surface.Surface
- Direction
- airframe.surface.reflect uses airframe.surface, so a change to airframe.surface can break airframe.surface.reflect, while a change to airframe.surface.reflect can't break airframe.surface.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→20 airframe.surface.reflect uses airframe.http.openapi.OpenAPI part of a loop✕
- Connections
- 2 pairs of types, where a type in airframe.surface.reflect uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.surface.reflect.RuntimeGenericSurface→wvlet.airframe.http.openapi.OpenAPI.Parameterwvlet.airframe.surface.reflect.StandardBuilder→wvlet.airframe.http.openapi.OpenAPI.Parameter
- Direction
- airframe.surface.reflect uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.surface.reflect, while a change to airframe.surface.reflect can't break airframe.http.openapi.OpenAPI.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→1 airframe.launcher uses airframe.surface.Primitive✕
- Connections
- 18 pairs of types, where a type in airframe.launcher uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.launcher.ClassOptionSchema→wvlet.airframe.surface.Primitive.Intwvlet.airframe.launcher.CommandLauncher→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.launcher.CommandLauncher→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.CommandLauncher→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.launcher.CommandLauncherBaseCompat→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.HelpMessagePrinter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.Launcher→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.LauncherBaseCompat→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.LauncherCompat→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.LauncherInfo→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.launcher.LauncherInfo→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.MethodOptionSchema→wvlet.airframe.surface.Primitive.Intwvlet.airframe.launcher.OptionParser→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.OptionSchema→wvlet.airframe.surface.Primitive.Intwvlet.airframe.launcher.OptionSchema→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.StringTree→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.launcher.StringTree→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.StringTreeCodec→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.launcher uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.launcher, while a change to airframe.launcher can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.launcher uses a module listed above it, which is the healthy direction.
11→4 airframe.launcher uses airframe.log✕
- Connections
- 5 pairs of types, where a type in airframe.launcher uses a type in airframe.log.
- The types involved
wvlet.airframe.launcher.ClassOptionSchema→wvlet.airframe.log.LogSupportwvlet.airframe.launcher.CommandLauncher→wvlet.airframe.log.LogSupportwvlet.airframe.launcher.Launcher→wvlet.airframe.log.LogSupportwvlet.airframe.launcher.OptionParser→wvlet.airframe.log.LogSupportwvlet.airframe.launcher.OptionSchema→wvlet.airframe.log.LogSupport
- Direction
- airframe.launcher uses airframe.log, so a change to airframe.log can break airframe.launcher, while a change to airframe.launcher can't break airframe.log.
- Position
- Below the diagonal: airframe.launcher uses a module listed above it, which is the healthy direction.
11→8 airframe.launcher uses airframe.msgpack.spi✕
- Connections
- 2 pairs of types, where a type in airframe.launcher uses a type in airframe.msgpack.spi.
- The types involved
wvlet.airframe.launcher.StringTreeCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.launcher.StringTreeCodec→wvlet.airframe.msgpack.spi.Unpacker
- Direction
- airframe.launcher uses airframe.msgpack.spi, so a change to airframe.msgpack.spi can break airframe.launcher, while a change to airframe.launcher can't break airframe.msgpack.spi.
- Position
- Below the diagonal: airframe.launcher uses a module listed above it, which is the healthy direction.
11→10 airframe.launcher uses airframe.surface.reflect✕
- Connections
- 3 pairs of types, where a type in airframe.launcher uses a type in airframe.surface.reflect.
- The types involved
wvlet.airframe.launcher.ClassOptionSchema→wvlet.airframe.surface.reflect.Pathwvlet.airframe.launcher.MethodOptionSchema→wvlet.airframe.surface.reflect.Pathwvlet.airframe.launcher.StringTree→wvlet.airframe.surface.reflect.Path
- Direction
- airframe.launcher uses airframe.surface.reflect, so a change to airframe.surface.reflect can break airframe.launcher, while a change to airframe.launcher can't break airframe.surface.reflect.
- Position
- Below the diagonal: airframe.launcher uses a module listed above it, which is the healthy direction.
11→19 airframe.launcher uses airframe.surface part of a loop✕
- Connections
- 5 pairs of types, where a type in airframe.launcher uses a type in airframe.surface.
- The types involved
wvlet.airframe.launcher.ClassOptionSchema→wvlet.airframe.surface.Surfacewvlet.airframe.launcher.Launcher→wvlet.airframe.surface.MethodSurfacewvlet.airframe.launcher.Launcher→wvlet.airframe.surface.Surfacewvlet.airframe.launcher.MethodOptionSchema→wvlet.airframe.surface.MethodSurfacewvlet.airframe.launcher.OptionParser→wvlet.airframe.surface.Surface
- Direction
- airframe.launcher uses airframe.surface, so a change to airframe.surface can break airframe.launcher, while a change to airframe.launcher can't break airframe.surface.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→26 airframe.launcher uses airframe.codec part of a loop✕
- Connections
- 3 pairs of types, where a type in airframe.launcher uses a type in airframe.codec.
- The types involved
wvlet.airframe.launcher.LauncherConfig→wvlet.airframe.codec.MessageCodecFactorywvlet.airframe.launcher.StringTreeCodec→wvlet.airframe.codec.MessageCodecwvlet.airframe.launcher.StringTreeCodec→wvlet.airframe.codec.MessageContext
- Direction
- airframe.launcher uses airframe.codec, so a change to airframe.codec can break airframe.launcher, while a change to airframe.launcher can't break airframe.codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 airframe.sql.model.Expression uses airframe.surface.Primitive✕
- Connections
- 109 pairs of types, where a type in airframe.sql.model.Expression uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.sql.model.Expression.Alias→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.All→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.Expression.AllColumns→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.And→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.ArithmeticBinaryExpr→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.ArithmeticUnaryExpr→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.ArrayConstructor→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.BackQuotedIdentifier→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.Between→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.BinaryExprType→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.BinaryLiteral→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.BooleanLiteral→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.Expression.Cast→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.Expression.Cast→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.CharLiteral→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.ColumnDefLike→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.Expression.ColumnType→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.CurrentDate→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.model.Expression.CurrentLocalTime→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.model.Expression.CurrentLocalTimeStamp→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.model.Expression.CurrentRow→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.CurrentTime→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.model.Expression.CurrentTimeBase→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.Expression.CurrentTimestamp→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.model.Expression.DayOfWeek→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.sql.model.Expression uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.sql.model.Expression, while a change to airframe.sql.model.Expression can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.sql.model.Expression uses a module listed above it, which is the healthy direction.
12→4 airframe.sql.model.Expression uses airframe.log✕
- Connections
- 1 pair of types, where a type in airframe.sql.model.Expression uses a type in airframe.log.
- The types involved
wvlet.airframe.sql.model.Expression.AllColumns→wvlet.airframe.log.LogSupport
- Direction
- airframe.sql.model.Expression uses airframe.log, so a change to airframe.log can break airframe.sql.model.Expression, while a change to airframe.sql.model.Expression can't break airframe.log.
- Position
- Below the diagonal: airframe.sql.model.Expression uses a module listed above it, which is the healthy direction.
12→9 airframe.sql.model.Expression uses airframe.sql.model✕
- Connections
- 217 pairs of types, where a type in airframe.sql.model.Expression uses a type in airframe.sql.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.sql.model.Expression.Alias→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.model.Expression.Alias→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.Expression.Alias→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.Alias→wvlet.airframe.sql.model.SourceColumnwvlet.airframe.sql.model.Expression.All→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.AllColumns→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.model.Expression.AllColumns→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.Expression.AllColumns→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.AllColumns→wvlet.airframe.sql.model.SourceColumnwvlet.airframe.sql.model.Expression.And→wvlet.airframe.sql.model.BinaryExpressionwvlet.airframe.sql.model.Expression.And→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.Expression.And→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.ArithmeticBinaryExpr→wvlet.airframe.sql.model.BinaryExpressionwvlet.airframe.sql.model.Expression.ArithmeticBinaryExpr→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.Expression.ArithmeticBinaryExpr→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.ArithmeticExpression→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.Expression.ArithmeticUnaryExpr→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.Expression.ArithmeticUnaryExpr→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.ArithmeticUnaryExpr→wvlet.airframe.sql.model.UnaryExpressionwvlet.airframe.sql.model.Expression.ArrayConstructor→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.Expression.ArrayConstructor→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.BackQuotedIdentifier→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.Between→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.Expression.Between→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.Expression.BinaryLiteral→wvlet.airframe.sql.model.LeafExpression
- Direction
- airframe.sql.model.Expression uses airframe.sql.model, so a change to airframe.sql.model can break airframe.sql.model.Expression, while a change to airframe.sql.model.Expression can't break airframe.sql.model.
- Position
- Below the diagonal: airframe.sql.model.Expression uses a module listed above it, which is the healthy direction.
12→18 airframe.sql.model.Expression uses airframe.sql.model.LogicalPlan part of a loop✕
- Connections
- 3 pairs of types, where a type in airframe.sql.model.Expression uses a type in airframe.sql.model.LogicalPlan.
- The types involved
wvlet.airframe.sql.model.Expression.InSubQuery→wvlet.airframe.sql.model.LogicalPlan.Relationwvlet.airframe.sql.model.Expression.NotInSubQuery→wvlet.airframe.sql.model.LogicalPlan.Relationwvlet.airframe.sql.model.Expression.SubQueryExpression→wvlet.airframe.sql.model.LogicalPlan.Relation
- Direction
- airframe.sql.model.Expression uses airframe.sql.model.LogicalPlan, so a change to airframe.sql.model.LogicalPlan can break airframe.sql.model.Expression, while a change to airframe.sql.model.Expression can't break airframe.sql.model.LogicalPlan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→26 airframe.sql.model.Expression uses airframe.codec part of a loop✕
- Connections
- 18 pairs of types, where a type in airframe.sql.model.Expression uses a type in airframe.codec.
- The types involved
wvlet.airframe.sql.model.Expression.Alias→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.AllColumns→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.ArithmeticBinaryExpr→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.ArrayConstructor→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.BooleanLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.CharLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.DecimalLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.DoubleLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.FunctionCall→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.LongLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.MultiSourceColumn→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.NullLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.RowConstructor→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.SingleColumn→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.StringLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.TimeLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.TimestampLiteral→wvlet.airframe.codec.DataTypewvlet.airframe.sql.model.Expression.TimestampWithTimeZoneLiteral→wvlet.airframe.codec.DataType
- Direction
- airframe.sql.model.Expression uses airframe.codec, so a change to airframe.codec can break airframe.sql.model.Expression, while a change to airframe.sql.model.Expression can't break airframe.codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 airframe.launcher.StringTree uses airframe.surface.Primitive✕
- Connections
- 2 pairs of types, where a type in airframe.launcher.StringTree uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.launcher.StringTree.Leaf→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.launcher.StringTree.Node→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.launcher.StringTree uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.launcher.StringTree, while a change to airframe.launcher.StringTree can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.launcher.StringTree uses a module listed above it, which is the healthy direction.
13→10 airframe.launcher.StringTree uses airframe.surface.reflect✕
- Connections
- 4 pairs of types, where a type in airframe.launcher.StringTree uses a type in airframe.surface.reflect.
- The types involved
wvlet.airframe.launcher.StringTree.EmptyNode→wvlet.airframe.surface.reflect.Pathwvlet.airframe.launcher.StringTree.Leaf→wvlet.airframe.surface.reflect.Pathwvlet.airframe.launcher.StringTree.Node→wvlet.airframe.surface.reflect.Pathwvlet.airframe.launcher.StringTree.SeqLeaf→wvlet.airframe.surface.reflect.Path
- Direction
- airframe.launcher.StringTree uses airframe.surface.reflect, so a change to airframe.surface.reflect can break airframe.launcher.StringTree, while a change to airframe.launcher.StringTree can't break airframe.surface.reflect.
- Position
- Below the diagonal: airframe.launcher.StringTree uses a module listed above it, which is the healthy direction.
13→11 airframe.launcher.StringTree uses airframe.launcher✕
- Connections
- 4 pairs of types, where a type in airframe.launcher.StringTree uses a type in airframe.launcher.
- The types involved
wvlet.airframe.launcher.StringTree.EmptyNode→wvlet.airframe.launcher.StringTreewvlet.airframe.launcher.StringTree.Leaf→wvlet.airframe.launcher.StringTreewvlet.airframe.launcher.StringTree.Node→wvlet.airframe.launcher.StringTreewvlet.airframe.launcher.StringTree.SeqLeaf→wvlet.airframe.launcher.StringTree
- Direction
- airframe.launcher.StringTree uses airframe.launcher, so a change to airframe.launcher can break airframe.launcher.StringTree, while a change to airframe.launcher.StringTree can't break airframe.launcher.
- Position
- Below the diagonal: airframe.launcher.StringTree uses a module listed above it, which is the healthy direction.
14→1 airframe.sql.catalog uses airframe.surface.Primitive✕
- Connections
- 13 pairs of types, where a type in airframe.sql.catalog uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.sql.catalog.BoundFunction→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.catalog.Catalog→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.catalog.Catalog→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.catalog.Catalog→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.sql.catalog.DataType→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.catalog.DataType→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.catalog.DataTypeParser→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.catalog.DataTypeParser→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.catalog.InMemoryCatalog→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.catalog.InMemoryCatalog→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.catalog.InMemoryCatalog→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.sql.catalog.SQLFunction→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.catalog.UnboundFunction→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.sql.catalog uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.sql.catalog, while a change to airframe.sql.catalog can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.sql.catalog uses a module listed above it, which is the healthy direction.
14→4 airframe.sql.catalog uses airframe.log✕
- Connections
- 2 pairs of types, where a type in airframe.sql.catalog uses a type in airframe.log.
- The types involved
wvlet.airframe.sql.catalog.Catalog→wvlet.airframe.log.LogSupportwvlet.airframe.sql.catalog.DataTypeParser→wvlet.airframe.log.LogSupport
- Direction
- airframe.sql.catalog uses airframe.log, so a change to airframe.log can break airframe.sql.catalog, while a change to airframe.sql.catalog can't break airframe.log.
- Position
- Below the diagonal: airframe.sql.catalog uses a module listed above it, which is the healthy direction.
14→12 airframe.sql.catalog uses airframe.sql.model.Expression✕
- Connections
- 1 pair of types, where a type in airframe.sql.catalog uses a type in airframe.sql.model.Expression.
- The types involved
wvlet.airframe.sql.catalog.Catalog→wvlet.airframe.sql.model.Expression.QName
- Direction
- airframe.sql.catalog uses airframe.sql.model.Expression, so a change to airframe.sql.model.Expression can break airframe.sql.catalog, while a change to airframe.sql.catalog can't break airframe.sql.model.Expression.
- Position
- Below the diagonal: airframe.sql.catalog uses a module listed above it, which is the healthy direction.
14→26 airframe.sql.catalog uses airframe.codec part of a loop✕
- Connections
- 6 pairs of types, where a type in airframe.sql.catalog uses a type in airframe.codec.
- The types involved
wvlet.airframe.sql.catalog.BoundFunction→wvlet.airframe.codec.DataTypewvlet.airframe.sql.catalog.DataType→wvlet.airframe.codec.DataTypewvlet.airframe.sql.catalog.DataTypeParser→wvlet.airframe.codec.DataTypewvlet.airframe.sql.catalog.SQLFunction→wvlet.airframe.codec.DataTypewvlet.airframe.sql.catalog.SQLFunctionType→wvlet.airframe.codec.DataTypewvlet.airframe.sql.catalog.UnboundFunction→wvlet.airframe.codec.DataType
- Direction
- airframe.sql.catalog uses airframe.codec, so a change to airframe.codec can break airframe.sql.catalog, while a change to airframe.sql.catalog can't break airframe.codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 airframe.rx.html uses airframe.surface.Primitive✕
- Connections
- 15 pairs of types, where a type in airframe.rx.html uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.rx.html.DOMRenderer→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.EntityRef→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.GlobalAttrs→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.HtmlAttribute→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.html.HtmlAttribute→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.HtmlElement→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.HtmlNodeBase→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.HtmlTags→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.Namespace→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.RawHtml→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.RxCode→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.RxDOM→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.html.RxDOM→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.html.RxDOMNode→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.html.RxElement→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.rx.html uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.rx.html, while a change to airframe.rx.html can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.rx.html uses a module listed above it, which is the healthy direction.
15→4 airframe.rx.html uses airframe.log✕
- Connections
- 5 pairs of types, where a type in airframe.rx.html uses a type in airframe.log.
- The types involved
wvlet.airframe.rx.html.DOMRenderer→wvlet.airframe.log.LogSupportwvlet.airframe.rx.html.Embedded→wvlet.airframe.log.LogSupportwvlet.airframe.rx.html.LazyRxElement→wvlet.airframe.log.LogSupportwvlet.airframe.rx.html.RxDOMNode→wvlet.airframe.log.LogSupportwvlet.airframe.rx.html.RxElement→wvlet.airframe.log.LogSupport
- Direction
- airframe.rx.html uses airframe.log, so a change to airframe.log can break airframe.rx.html, while a change to airframe.rx.html can't break airframe.log.
- Position
- Below the diagonal: airframe.rx.html uses a module listed above it, which is the healthy direction.
15→13 airframe.rx.html uses airframe.launcher.StringTree✕
- Connections
- 2 pairs of types, where a type in airframe.rx.html uses a type in airframe.launcher.StringTree.
- The types involved
wvlet.airframe.rx.html.DOMRenderer→wvlet.airframe.launcher.StringTree.Nodewvlet.airframe.rx.html.RxDOMNode→wvlet.airframe.launcher.StringTree.Node
- Direction
- airframe.rx.html uses airframe.launcher.StringTree, so a change to airframe.launcher.StringTree can break airframe.rx.html, while a change to airframe.rx.html can't break airframe.launcher.StringTree.
- Position
- Below the diagonal: airframe.rx.html uses a module listed above it, which is the healthy direction.
15→17 airframe.rx.html uses airframe.rx part of a loop✕
- Connections
- 3 pairs of types, where a type in airframe.rx.html uses a type in airframe.rx.
- The types involved
wvlet.airframe.rx.html.DOMRenderer→wvlet.airframe.rx.Cancelablewvlet.airframe.rx.html.RxDOMNode→wvlet.airframe.rx.Cancelablewvlet.airframe.rx.html.RxElement→wvlet.airframe.rx.Cancelable
- Direction
- airframe.rx.html uses airframe.rx, so a change to airframe.rx can break airframe.rx.html, while a change to airframe.rx.html can't break airframe.rx.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→25 airframe.rx.html uses airframe.http.Http part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.rx.html uses a type in airframe.http.Http.
- The types involved
wvlet.airframe.rx.html.RxHtmlMacros→wvlet.airframe.http.Http.Context
- Direction
- airframe.rx.html uses airframe.http.Http, so a change to airframe.http.Http can break airframe.rx.html, while a change to airframe.rx.html can't break airframe.http.Http.
- 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→1 airframe.sql.analyzer uses airframe.surface.Primitive✕
- Connections
- 13 pairs of types, where a type in airframe.sql.analyzer uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.sql.analyzer.AnalyzerContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.analyzer.EdgeOrdering→wvlet.airframe.surface.Primitive.Intwvlet.airframe.sql.analyzer.Graph→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.analyzer.InOutTableFinder→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.sql.analyzer.Node→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.analyzer.QuerySignature→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.analyzer.QuerySignatureConfig→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.analyzer.RewriteRule→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.analyzer.SQLAnalyzer→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.analyzer.SQLAnonymizer→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.analyzer.SQLAnonymizer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.sql.analyzer.TableGraph→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.analyzer.TypeResolver→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.sql.analyzer uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.sql.analyzer, while a change to airframe.sql.analyzer can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.sql.analyzer uses a module listed above it, which is the healthy direction.
16→4 airframe.sql.analyzer uses airframe.log✕
- Connections
- 6 pairs of types, where a type in airframe.sql.analyzer uses a type in airframe.log.
- The types involved
wvlet.airframe.sql.analyzer.CTEResolver→wvlet.airframe.log.LogSupportwvlet.airframe.sql.analyzer.Optimizer→wvlet.airframe.log.LogSupportwvlet.airframe.sql.analyzer.QuerySignature→wvlet.airframe.log.LogSupportwvlet.airframe.sql.analyzer.RewriteRule→wvlet.airframe.log.LogSupportwvlet.airframe.sql.analyzer.SQLAnalyzer→wvlet.airframe.log.LogSupportwvlet.airframe.sql.analyzer.TypeResolver→wvlet.airframe.log.LogSupport
- Direction
- airframe.sql.analyzer uses airframe.log, so a change to airframe.log can break airframe.sql.analyzer, while a change to airframe.sql.analyzer can't break airframe.log.
- Position
- Below the diagonal: airframe.sql.analyzer uses a module listed above it, which is the healthy direction.
16→9 airframe.sql.analyzer uses airframe.sql.model✕
- Connections
- 12 pairs of types, where a type in airframe.sql.analyzer uses a type in airframe.sql.model.
- The types involved
wvlet.airframe.sql.analyzer.AnalyzerContext→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.analyzer.AnalyzerContext→wvlet.airframe.sql.model.LogicalPlanwvlet.airframe.sql.analyzer.CTEResolver→wvlet.airframe.sql.model.LogicalPlanwvlet.airframe.sql.analyzer.InOutTableFinder→wvlet.airframe.sql.model.LogicalPlanwvlet.airframe.sql.analyzer.Optimizer→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.analyzer.Optimizer→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.analyzer.RewriteRule→wvlet.airframe.sql.model.LogicalPlanwvlet.airframe.sql.analyzer.SQLAnalyzer→wvlet.airframe.sql.model.LogicalPlanwvlet.airframe.sql.analyzer.TableGraph→wvlet.airframe.sql.model.LogicalPlanwvlet.airframe.sql.analyzer.TypeResolver→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.analyzer.TypeResolver→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.analyzer.TypeResolver→wvlet.airframe.sql.model.LogicalPlan
- Direction
- airframe.sql.analyzer uses airframe.sql.model, so a change to airframe.sql.model can break airframe.sql.analyzer, while a change to airframe.sql.analyzer can't break airframe.sql.model.
- Position
- Below the diagonal: airframe.sql.analyzer uses a module listed above it, which is the healthy direction.
16→13 airframe.sql.analyzer uses airframe.launcher.StringTree✕
- Connections
- 2 pairs of types, where a type in airframe.sql.analyzer uses a type in airframe.launcher.StringTree.
- The types involved
wvlet.airframe.sql.analyzer.Edge→wvlet.airframe.launcher.StringTree.Nodewvlet.airframe.sql.analyzer.Graph→wvlet.airframe.launcher.StringTree.Node
- Direction
- airframe.sql.analyzer uses airframe.launcher.StringTree, so a change to airframe.launcher.StringTree can break airframe.sql.analyzer, while a change to airframe.sql.analyzer can't break airframe.launcher.StringTree.
- Position
- Below the diagonal: airframe.sql.analyzer uses a module listed above it, which is the healthy direction.
16→14 airframe.sql.analyzer uses airframe.sql.catalog✕
- Connections
- 2 pairs of types, where a type in airframe.sql.analyzer uses a type in airframe.sql.catalog.
- The types involved
wvlet.airframe.sql.analyzer.AnalyzerContext→wvlet.airframe.sql.catalog.Catalogwvlet.airframe.sql.analyzer.SQLAnalyzer→wvlet.airframe.sql.catalog.Catalog
- Direction
- airframe.sql.analyzer uses airframe.sql.catalog, so a change to airframe.sql.catalog can break airframe.sql.analyzer, while a change to airframe.sql.analyzer can't break airframe.sql.catalog.
- Position
- Below the diagonal: airframe.sql.analyzer uses a module listed above it, which is the healthy direction.
16→18 airframe.sql.analyzer uses airframe.sql.model.LogicalPlan part of a loop✕
- Connections
- 2 pairs of types, where a type in airframe.sql.analyzer uses a type in airframe.sql.model.LogicalPlan.
- The types involved
wvlet.airframe.sql.analyzer.Optimizer→wvlet.airframe.sql.model.LogicalPlan.Relationwvlet.airframe.sql.analyzer.TypeResolver→wvlet.airframe.sql.model.LogicalPlan.Relation
- Direction
- airframe.sql.analyzer uses airframe.sql.model.LogicalPlan, so a change to airframe.sql.model.LogicalPlan can break airframe.sql.analyzer, while a change to airframe.sql.analyzer can't break airframe.sql.model.LogicalPlan.
- 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.
17→1 airframe.rx uses airframe.surface.Primitive✕
- Connections
- 25 pairs of types, where a type in airframe.rx uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.rx.Cancelable→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.ManualTicker→wvlet.airframe.surface.Primitive.Longwvlet.airframe.rx.Rx→wvlet.airframe.surface.Primitive.Longwvlet.airframe.rx.Rx→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.RxBlockingQueue→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.RxCache→wvlet.airframe.surface.Primitive.Longwvlet.airframe.rx.RxOps→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.RxOptionCache→wvlet.airframe.surface.Primitive.Longwvlet.airframe.rx.RxOptionCacheOp→wvlet.airframe.surface.Primitive.Longwvlet.airframe.rx.RxOptionVar→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.RxOptionVar→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.RxOptionVar→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.RxQueue→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.RxResult→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.RxSource→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.RxVar→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.RxVar→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.rx.RxVar→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.RxVarOps→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.rx.RxVarOps→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.Ticker→wvlet.airframe.surface.Primitive.Longwvlet.airframe.rx.Timer→wvlet.airframe.surface.Primitive.Longwvlet.airframe.rx.Timer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.rx.compat→wvlet.airframe.surface.Primitive.Longwvlet.airframe.rx.html→wvlet.airframe.surface.Primitive.Boolean
- Direction
- airframe.rx uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.rx, while a change to airframe.rx can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.rx uses a module listed above it, which is the healthy direction.
17→4 airframe.rx uses airframe.log✕
- Connections
- 2 pairs of types, where a type in airframe.rx uses a type in airframe.log.
- The types involved
wvlet.airframe.rx.RxQueue→wvlet.airframe.log.LogSupportwvlet.airframe.rx.RxRunner→wvlet.airframe.log.LogSupport
- Direction
- airframe.rx uses airframe.log, so a change to airframe.log can break airframe.rx, while a change to airframe.rx can't break airframe.log.
- Position
- Below the diagonal: airframe.rx uses a module listed above it, which is the healthy direction.
17→6 airframe.rx uses airframe.control✕
- Connections
- 5 pairs of types, where a type in airframe.rx uses a type in airframe.control.
- The types involved
wvlet.airframe.rx.ManualTicker→wvlet.airframe.control.ManualTickerwvlet.airframe.rx.ManualTicker→wvlet.airframe.control.Tickerwvlet.airframe.rx.RxCache→wvlet.airframe.control.Tickerwvlet.airframe.rx.RxOptionCache→wvlet.airframe.control.Tickerwvlet.airframe.rx.RxOptionCacheOp→wvlet.airframe.control.Ticker
- Direction
- airframe.rx uses airframe.control, so a change to airframe.control can break airframe.rx, while a change to airframe.rx can't break airframe.control.
- Position
- Below the diagonal: airframe.rx uses a module listed above it, which is the healthy direction.
17→15 airframe.rx uses airframe.rx.html✕
- Connections
- 2 pairs of types, where a type in airframe.rx uses a type in airframe.rx.html.
- The types involved
wvlet.airframe.rx.html→wvlet.airframe.rx.html.HtmlNodewvlet.airframe.rx.html→wvlet.airframe.rx.html.RxElement
- Direction
- airframe.rx uses airframe.rx.html, so a change to airframe.rx.html can break airframe.rx, while a change to airframe.rx can't break airframe.rx.html.
- Position
- Below the diagonal: airframe.rx uses a module listed above it, which is the healthy direction.
17→31 airframe.rx uses airframe part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.rx uses a type in airframe.
- The types involved
wvlet.airframe.rx.LazyF0→wvlet.airframe.LazyF0
- Direction
- airframe.rx uses airframe, so a change to airframe can break airframe.rx, while a change to airframe.rx can't break airframe.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 airframe.sql.model.LogicalPlan uses airframe.surface.Primitive✕
- Connections
- 38 pairs of types, where a type in airframe.sql.model.LogicalPlan uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.sql.model.LogicalPlan.Aggregate→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.AliasedRelation→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.CreateSchema→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.LogicalPlan.CreateTable→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.LogicalPlan.CreateTable→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.CreateTableAs→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.LogicalPlan.CreateView→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.LogicalPlan.Delete→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.Distinct→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.DropSchema→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.LogicalPlan.DropTable→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.LogicalPlan.DropTable→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.DropView→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.sql.model.LogicalPlan.EmptyRelation→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.Except→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.Filter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.InsertInto→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.Intersect→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.Join→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.JoinType→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.Lateral→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.LateralView→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.Limit→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.ParenthesizedRelation→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.sql.model.LogicalPlan.Project→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.sql.model.LogicalPlan uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.sql.model.LogicalPlan, while a change to airframe.sql.model.LogicalPlan can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.sql.model.LogicalPlan uses a module listed above it, which is the healthy direction.
18→4 airframe.sql.model.LogicalPlan uses airframe.log✕
- Connections
- 2 pairs of types, where a type in airframe.sql.model.LogicalPlan uses a type in airframe.log.
- The types involved
wvlet.airframe.sql.model.LogicalPlan.Join→wvlet.airframe.log.LogSupportwvlet.airframe.sql.model.LogicalPlan.SetOperation→wvlet.airframe.log.LogSupport
- Direction
- airframe.sql.model.LogicalPlan uses airframe.log, so a change to airframe.log can break airframe.sql.model.LogicalPlan, while a change to airframe.sql.model.LogicalPlan can't break airframe.log.
- Position
- Below the diagonal: airframe.sql.model.LogicalPlan uses a module listed above it, which is the healthy direction.
18→5 airframe.sql.model.LogicalPlan uses airframe.rx.html.widget.editor.monaco✕
- Connections
- 2 pairs of types, where a type in airframe.sql.model.LogicalPlan uses a type in airframe.rx.html.widget.editor.monaco.
- The types involved
wvlet.airframe.sql.model.LogicalPlan.Aggregate→wvlet.airframe.rx.html.widget.editor.monaco.Selectionwvlet.airframe.sql.model.LogicalPlan.Project→wvlet.airframe.rx.html.widget.editor.monaco.Selection
- Direction
- airframe.sql.model.LogicalPlan uses airframe.rx.html.widget.editor.monaco, so a change to airframe.rx.html.widget.editor.monaco can break airframe.sql.model.LogicalPlan, while a change to airframe.sql.model.LogicalPlan can't break airframe.rx.html.widget.editor.monaco.
- Position
- Below the diagonal: airframe.sql.model.LogicalPlan uses a module listed above it, which is the healthy direction.
18→9 airframe.sql.model.LogicalPlan uses airframe.sql.model✕
- Connections
- 89 pairs of types, where a type in airframe.sql.model.LogicalPlan uses a type in airframe.sql.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.sql.model.LogicalPlan.AddColumn→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.Aggregate→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.model.LogicalPlan.Aggregate→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.LogicalPlan.Aggregate→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.AliasedRelation→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.model.LogicalPlan.AliasedRelation→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.CreateSchema→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.CreateTable→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.CreateTableAs→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.model.LogicalPlan.CreateTableAs→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.CreateView→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.DDL→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.model.LogicalPlan.DDL→wvlet.airframe.sql.model.LeafPlanwvlet.airframe.sql.model.LogicalPlan.DDL→wvlet.airframe.sql.model.LogicalPlanwvlet.airframe.sql.model.LogicalPlan.DDL→wvlet.airframe.sql.model.SQLSigwvlet.airframe.sql.model.LogicalPlan.Delete→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.model.LogicalPlan.Delete→wvlet.airframe.sql.model.Expressionwvlet.airframe.sql.model.LogicalPlan.Delete→wvlet.airframe.sql.model.LeafPlanwvlet.airframe.sql.model.LogicalPlan.Delete→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.Distinct→wvlet.airframe.sql.model.Attributewvlet.airframe.sql.model.LogicalPlan.Distinct→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.DropColumn→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.DropSchema→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.DropTable→wvlet.airframe.sql.model.NodeLocationwvlet.airframe.sql.model.LogicalPlan.DropView→wvlet.airframe.sql.model.NodeLocation
- Direction
- airframe.sql.model.LogicalPlan uses airframe.sql.model, so a change to airframe.sql.model can break airframe.sql.model.LogicalPlan, while a change to airframe.sql.model.LogicalPlan can't break airframe.sql.model.
- Position
- Below the diagonal: airframe.sql.model.LogicalPlan uses a module listed above it, which is the healthy direction.
18→12 airframe.sql.model.LogicalPlan uses airframe.sql.model.Expression✕
- Connections
- 30 pairs of types, where a type in airframe.sql.model.LogicalPlan uses a type in airframe.sql.model.Expression. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.sql.model.LogicalPlan.AddColumn→wvlet.airframe.sql.model.Expression.ColumnDefwvlet.airframe.sql.model.LogicalPlan.AddColumn→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.Aggregate→wvlet.airframe.sql.model.Expression.GroupingKeywvlet.airframe.sql.model.LogicalPlan.AliasedRelation→wvlet.airframe.sql.model.Expression.Identifierwvlet.airframe.sql.model.LogicalPlan.CreateSchema→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.CreateSchema→wvlet.airframe.sql.model.Expression.SchemaPropertywvlet.airframe.sql.model.LogicalPlan.CreateTable→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.CreateTable→wvlet.airframe.sql.model.Expression.TableElementwvlet.airframe.sql.model.LogicalPlan.CreateTableAs→wvlet.airframe.sql.model.Expression.Identifierwvlet.airframe.sql.model.LogicalPlan.CreateTableAs→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.CreateView→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.Delete→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.DropColumn→wvlet.airframe.sql.model.Expression.Identifierwvlet.airframe.sql.model.LogicalPlan.DropColumn→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.DropSchema→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.DropTable→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.DropView→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.InsertInto→wvlet.airframe.sql.model.Expression.Identifierwvlet.airframe.sql.model.LogicalPlan.InsertInto→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.Join→wvlet.airframe.sql.model.Expression.JoinCriteriawvlet.airframe.sql.model.LogicalPlan.LateralView→wvlet.airframe.sql.model.Expression.Identifierwvlet.airframe.sql.model.LogicalPlan.Limit→wvlet.airframe.sql.model.Expression.LongLiteralwvlet.airframe.sql.model.LogicalPlan.RenameColumn→wvlet.airframe.sql.model.Expression.Identifierwvlet.airframe.sql.model.LogicalPlan.RenameColumn→wvlet.airframe.sql.model.Expression.QNamewvlet.airframe.sql.model.LogicalPlan.RenameSchema→wvlet.airframe.sql.model.Expression.Identifier
- Direction
- airframe.sql.model.LogicalPlan uses airframe.sql.model.Expression, so a change to airframe.sql.model.Expression can break airframe.sql.model.LogicalPlan, while a change to airframe.sql.model.LogicalPlan can't break airframe.sql.model.Expression.
- Position
- Below the diagonal: airframe.sql.model.LogicalPlan uses a module listed above it, which is the healthy direction.
18→16 airframe.sql.model.LogicalPlan uses airframe.sql.analyzer✕
- Connections
- 36 pairs of types, where a type in airframe.sql.model.LogicalPlan uses a type in airframe.sql.analyzer. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.sql.model.LogicalPlan.AddColumn→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Aggregate→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.AliasedRelation→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.CreateSchema→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.CreateTable→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.CreateTableAs→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.CreateView→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Delete→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Distinct→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.DropColumn→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.DropSchema→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.DropTable→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.DropView→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.EmptyRelation→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Except→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Filter→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.InsertInto→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Intersect→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Join→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Lateral→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.LateralView→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Limit→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.ParenthesizedRelation→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Project→wvlet.airframe.sql.analyzer.QuerySignatureConfigwvlet.airframe.sql.model.LogicalPlan.Query→wvlet.airframe.sql.analyzer.QuerySignatureConfig
- Direction
- airframe.sql.model.LogicalPlan uses airframe.sql.analyzer, so a change to airframe.sql.analyzer can break airframe.sql.model.LogicalPlan, while a change to airframe.sql.model.LogicalPlan can't break airframe.sql.analyzer.
- Position
- Below the diagonal: airframe.sql.model.LogicalPlan uses a module listed above it, which is the healthy direction.
19→1 airframe.surface uses airframe.surface.Primitive✕
- Connections
- 45 pairs of types, where a type in airframe.surface uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.surface.Alias→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.Alias→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.AnyRefSurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.ArraySurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.CName→wvlet.airframe.surface.Primitive.Charwvlet.airframe.surface.CName→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.CanonicalNameFormatter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.ClassMethodSurface→wvlet.airframe.surface.Primitive.Intwvlet.airframe.surface.ClassMethodSurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.ExistentialType→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.GenericSurface→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.GenericSurface→wvlet.airframe.surface.Primitive.Intwvlet.airframe.surface.GenericSurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.HigherKindedTypeSurface→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.HigherKindedTypeSurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.IntersectionSurface→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.IntersectionSurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.LazySurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.MethodRef→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.MethodRef→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.MethodSurface→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.MethodSurface→wvlet.airframe.surface.Primitive.Intwvlet.airframe.surface.MethodSurface→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.surface.OptionSurface→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.surface.Parameter→wvlet.airframe.surface.Primitive.Boolean
- Direction
- airframe.surface uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.surface, while a change to airframe.surface can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.surface uses a module listed above it, which is the healthy direction.
19→4 airframe.surface uses airframe.log✕
- Connections
- 1 pair of types, where a type in airframe.surface uses a type in airframe.log.
- The types involved
wvlet.airframe.surface.Zero→wvlet.airframe.log.LogSupport
- Direction
- airframe.surface uses airframe.log, so a change to airframe.log can break airframe.surface, while a change to airframe.surface can't break airframe.log.
- Position
- Below the diagonal: airframe.surface uses a module listed above it, which is the healthy direction.
19→18 airframe.surface uses airframe.sql.model.LogicalPlan✕
- Connections
- 2 pairs of types, where a type in airframe.surface uses a type in airframe.sql.model.LogicalPlan.
- The types involved
wvlet.airframe.surface.Union2→wvlet.airframe.sql.model.LogicalPlan.Unionwvlet.airframe.surface.Union3→wvlet.airframe.sql.model.LogicalPlan.Union
- Direction
- airframe.surface uses airframe.sql.model.LogicalPlan, so a change to airframe.sql.model.LogicalPlan can break airframe.surface, while a change to airframe.surface can't break airframe.sql.model.LogicalPlan.
- Position
- Below the diagonal: airframe.surface uses a module listed above it, which is the healthy direction.
19→20 airframe.surface uses airframe.http.openapi.OpenAPI part of a loop✕
- Connections
- 8 pairs of types, where a type in airframe.surface uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.surface.GenericSurface→wvlet.airframe.http.openapi.OpenAPI.Parameterwvlet.airframe.surface.IntersectionSurface→wvlet.airframe.http.openapi.OpenAPI.Parameterwvlet.airframe.surface.MethodParameter→wvlet.airframe.http.openapi.OpenAPI.Parameterwvlet.airframe.surface.RecordParameter→wvlet.airframe.http.openapi.OpenAPI.Parameterwvlet.airframe.surface.RecordSurface→wvlet.airframe.http.openapi.OpenAPI.Parameterwvlet.airframe.surface.Surface→wvlet.airframe.http.openapi.OpenAPI.Parameterwvlet.airframe.surface.TaggedSurface→wvlet.airframe.http.openapi.OpenAPI.Parameterwvlet.airframe.surface.UnionSurface→wvlet.airframe.http.openapi.OpenAPI.Parameter
- Direction
- airframe.surface uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.surface, while a change to airframe.surface can't break airframe.http.openapi.OpenAPI.
- 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→25 airframe.surface uses airframe.http.Http part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.surface uses a type in airframe.http.Http.
- The types involved
wvlet.airframe.surface.SurfaceMacros→wvlet.airframe.http.Http.Context
- Direction
- airframe.surface uses airframe.http.Http, so a change to airframe.http.Http can break airframe.surface, while a change to airframe.surface can't break airframe.http.Http.
- 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.
20→1 airframe.http.openapi.OpenAPI uses airframe.surface.Primitive✕
- Connections
- 15 pairs of types, where a type in airframe.http.openapi.OpenAPI uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.openapi.OpenAPI.Components→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.Info→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.License→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.MediaType→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.Parameter→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.openapi.OpenAPI.Parameter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.ParameterRef→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.PathItem→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.RequestBody→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.openapi.OpenAPI.RequestBody→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.Response→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.ResponseRef→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.Schema→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.openapi.OpenAPI.Schema→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.openapi.OpenAPI.SchemaRef→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.http.openapi.OpenAPI uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.openapi.OpenAPI, while a change to airframe.http.openapi.OpenAPI can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
20→19 airframe.http.openapi.OpenAPI uses airframe.surface✕
- Connections
- 8 pairs of types, where a type in airframe.http.openapi.OpenAPI uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.openapi.OpenAPI.OneOf→wvlet.airframe.surface.Union3wvlet.airframe.http.openapi.OpenAPI.Parameter→wvlet.airframe.surface.Union2wvlet.airframe.http.openapi.OpenAPI.ParameterRef→wvlet.airframe.surface.Union2wvlet.airframe.http.openapi.OpenAPI.PathItem→wvlet.airframe.surface.Union2wvlet.airframe.http.openapi.OpenAPI.Response→wvlet.airframe.surface.Union2wvlet.airframe.http.openapi.OpenAPI.ResponseRef→wvlet.airframe.surface.Union2wvlet.airframe.http.openapi.OpenAPI.Schema→wvlet.airframe.surface.Union3wvlet.airframe.http.openapi.OpenAPI.SchemaRef→wvlet.airframe.surface.Union3
- Direction
- airframe.http.openapi.OpenAPI uses airframe.surface, so a change to airframe.surface can break airframe.http.openapi.OpenAPI, while a change to airframe.http.openapi.OpenAPI can't break airframe.surface.
- Position
- Below the diagonal: airframe.http.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
21→1 airframe.lifecycle uses airframe.surface.Primitive✕
- Connections
- 17 pairs of types, where a type in airframe.lifecycle uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.lifecycle.AddShutdownHook→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.CloseHook→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.lifecycle.CloseHook→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.FILOLifeCycleHookExecutor→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.Injectee→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.lifecycle.Injectee→wvlet.airframe.surface.Primitive.Intwvlet.airframe.lifecycle.LifeCycleEventHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.LifeCycleEventHandlerChain→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.LifeCycleEventHandlerPair→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.LifeCycleHook→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.LifeCycleManager→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.lifecycle.LifeCycleManager→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.lifecycle.LifeCycleManager→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.MethodCallHook→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.lifecycle.MethodCallHook→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.ShowDebugLifeCycleLog→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.lifecycle.ShowLifeCycleLog→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.lifecycle uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.lifecycle, while a change to airframe.lifecycle can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.lifecycle uses a module listed above it, which is the healthy direction.
21→4 airframe.lifecycle uses airframe.log✕
- Connections
- 2 pairs of types, where a type in airframe.lifecycle uses a type in airframe.log.
- The types involved
wvlet.airframe.lifecycle.FILOLifeCycleHookExecutor→wvlet.airframe.log.LogSupportwvlet.airframe.lifecycle.LifeCycleManager→wvlet.airframe.log.LogSupport
- Direction
- airframe.lifecycle uses airframe.log, so a change to airframe.log can break airframe.lifecycle, while a change to airframe.lifecycle can't break airframe.log.
- Position
- Below the diagonal: airframe.lifecycle uses a module listed above it, which is the healthy direction.
21→19 airframe.lifecycle uses airframe.surface✕
- Connections
- 7 pairs of types, where a type in airframe.lifecycle uses a type in airframe.surface.
- The types involved
wvlet.airframe.lifecycle.EventHookHolder→wvlet.airframe.surface.Surfacewvlet.airframe.lifecycle.Injectee→wvlet.airframe.surface.Surfacewvlet.airframe.lifecycle.LifeCycleEventHandler→wvlet.airframe.surface.Surfacewvlet.airframe.lifecycle.LifeCycleEventHandlerChain→wvlet.airframe.surface.Surfacewvlet.airframe.lifecycle.LifeCycleEventHandlerPair→wvlet.airframe.surface.Surfacewvlet.airframe.lifecycle.LifeCycleHook→wvlet.airframe.surface.Surfacewvlet.airframe.lifecycle.LifeCycleManager→wvlet.airframe.surface.Surface
- Direction
- airframe.lifecycle uses airframe.surface, so a change to airframe.surface can break airframe.lifecycle, while a change to airframe.lifecycle can't break airframe.surface.
- Position
- Below the diagonal: airframe.lifecycle uses a module listed above it, which is the healthy direction.
21→24 airframe.lifecycle uses airframe.tracing part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.lifecycle uses a type in airframe.tracing.
- The types involved
wvlet.airframe.lifecycle.LifeCycleManager→wvlet.airframe.tracing.Tracer
- Direction
- airframe.lifecycle uses airframe.tracing, so a change to airframe.tracing can break airframe.lifecycle, while a change to airframe.lifecycle can't break airframe.tracing.
- 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.
21→31 airframe.lifecycle uses airframe part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.lifecycle uses a type in airframe.
- The types involved
wvlet.airframe.lifecycle.LifeCycleManager→wvlet.airframe.AirframeSession
- Direction
- airframe.lifecycle uses airframe, so a change to airframe can break airframe.lifecycle, while a change to airframe.lifecycle can't break airframe.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→1 airframe.http.HttpMessage uses airframe.surface.Primitive✕
- Connections
- 25 pairs of types, where a type in airframe.http.HttpMessage uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.HttpMessage.ByteArrayMessage→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.HttpMessage.ByteArrayMessage→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.HttpMessage.ByteArrayMessage→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpMessage.EmptyMessage→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.HttpMessage.EmptyMessage→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.HttpMessage.EmptyMessage→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.HttpMessage.EmptyMessage→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpMessage.HttpMessageRequestAdapter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpMessage.HttpMessageResponseAdapter→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.HttpMessage.HttpMessageResponseAdapter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpMessage.LazyByteArrayMessage→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.HttpMessage.LazyByteArrayMessage→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.HttpMessage.LazyByteArrayMessage→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpMessage.Message→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.HttpMessage.Message→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.HttpMessage.Message→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.HttpMessage.Message→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpMessage.Request→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.HttpMessage.Request→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpMessage.Request→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.HttpMessage.Response→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.HttpMessage.Response→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpMessage.StringMessage→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.HttpMessage.StringMessage→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.HttpMessage.StringMessage→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.http.HttpMessage uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.HttpMessage, while a change to airframe.http.HttpMessage can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.HttpMessage uses a module listed above it, which is the healthy direction.
22→17 airframe.http.HttpMessage uses airframe.rx✕
- Connections
- 1 pair of types, where a type in airframe.http.HttpMessage uses a type in airframe.rx.
- The types involved
wvlet.airframe.http.HttpMessage.Response→wvlet.airframe.rx.Rx
- Direction
- airframe.http.HttpMessage uses airframe.rx, so a change to airframe.rx can break airframe.http.HttpMessage, while a change to airframe.http.HttpMessage can't break airframe.rx.
- Position
- Below the diagonal: airframe.http.HttpMessage uses a module listed above it, which is the healthy direction.
22→20 airframe.http.HttpMessage uses airframe.http.openapi.OpenAPI✕
- Connections
- 3 pairs of types, where a type in airframe.http.HttpMessage uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.HttpMessage.HttpMessageResponseAdapter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.HttpMessage.HttpMessageResponseWrapper→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.HttpMessage.Response→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http.HttpMessage uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http.HttpMessage, while a change to airframe.http.HttpMessage can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http.HttpMessage uses a module listed above it, which is the healthy direction.
22→30 airframe.http.HttpMessage uses airframe.http part of a loop✕
- Connections
- 19 pairs of types, where a type in airframe.http.HttpMessage uses a type in airframe.http.
- The types involved
wvlet.airframe.http.HttpMessage.HttpMessageRequestAdapter→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.HttpMessage.HttpMessageRequestAdapter→wvlet.airframe.http.HttpRequestwvlet.airframe.http.HttpMessage.HttpMessageRequestAdapter→wvlet.airframe.http.HttpRequestAdapterwvlet.airframe.http.HttpMessage.HttpMessageRequestAdapter→wvlet.airframe.http.ServerAddresswvlet.airframe.http.HttpMessage.HttpMessageRequestWrapper→wvlet.airframe.http.HttpRequestwvlet.airframe.http.HttpMessage.HttpMessageRequestWrapper→wvlet.airframe.http.HttpRequestAdapterwvlet.airframe.http.HttpMessage.HttpMessageResponseAdapter→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.HttpMessage.HttpMessageResponseAdapter→wvlet.airframe.http.HttpResponsewvlet.airframe.http.HttpMessage.HttpMessageResponseAdapter→wvlet.airframe.http.HttpResponseAdapterwvlet.airframe.http.HttpMessage.HttpMessageResponseWrapper→wvlet.airframe.http.HttpResponsewvlet.airframe.http.HttpMessage.HttpMessageResponseWrapper→wvlet.airframe.http.HttpResponseAdapterwvlet.airframe.http.HttpMessage.Request→wvlet.airframe.http.HttpMessagewvlet.airframe.http.HttpMessage.Request→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.HttpMessage.Request→wvlet.airframe.http.ServerAddresswvlet.airframe.http.HttpMessage.Request→wvlet.airframe.http.ServerSentEventHandlerwvlet.airframe.http.HttpMessage.Response→wvlet.airframe.http.HttpMessagewvlet.airframe.http.HttpMessage.Response→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.HttpMessage.Response→wvlet.airframe.http.HttpStatuswvlet.airframe.http.HttpMessage.Response→wvlet.airframe.http.ServerSentEvent
- Direction
- airframe.http.HttpMessage uses airframe.http, so a change to airframe.http can break airframe.http.HttpMessage, while a change to airframe.http.HttpMessage can't break airframe.http.
- 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.
23→1 airframe.parquet uses airframe.surface.Primitive✕
- Connections
- 34 pairs of types, where a type in airframe.parquet uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.parquet.ColumnStatistics→wvlet.airframe.surface.Primitive.Longwvlet.airframe.parquet.NioInputFile→wvlet.airframe.surface.Primitive.Longwvlet.airframe.parquet.Parquet→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetCompat→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetFieldWriter→wvlet.airframe.surface.Primitive.Intwvlet.airframe.parquet.ParquetFieldWriter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetFieldWriter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.parquet.ParquetObjectWriter→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.parquet.ParquetObjectWriter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetObjectWriter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.parquet.ParquetOptionWriter→wvlet.airframe.surface.Primitive.Intwvlet.airframe.parquet.ParquetOptionWriter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetOptionWriter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.parquet.ParquetParameterWriter→wvlet.airframe.surface.Primitive.Intwvlet.airframe.parquet.ParquetParameterWriter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetParameterWriter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.parquet.ParquetQueryPlan→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetQueryPlanner→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetReadSupportAdapter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetReaderAdapter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetRecordWriter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.parquet.ParquetRecordWriterSupportAdapter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.parquet.ParquetSchema→wvlet.airframe.surface.Primitive.PrimitiveSurfacewvlet.airframe.parquet.ParquetSchema→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.parquet.ParquetSeqWriter→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.parquet uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.parquet, while a change to airframe.parquet can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.parquet uses a module listed above it, which is the healthy direction.
23→3 airframe.parquet uses airframe.http.RPCEncoding✕
- Connections
- 7 pairs of types, where a type in airframe.parquet uses a type in airframe.http.RPCEncoding.
- The types involved
wvlet.airframe.parquet.ParquetFieldWriter→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.parquet.ParquetObjectWriter→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.parquet.ParquetOptionWriter→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.parquet.ParquetParameterWriter→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.parquet.ParquetSeqWriter→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.parquet.ParquetWriteCodec→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.parquet.PrimitiveParquetCodec→wvlet.airframe.http.RPCEncoding.MsgPack
- Direction
- airframe.parquet uses airframe.http.RPCEncoding, so a change to airframe.http.RPCEncoding can break airframe.parquet, while a change to airframe.parquet can't break airframe.http.RPCEncoding.
- Position
- Below the diagonal: airframe.parquet uses a module listed above it, which is the healthy direction.
23→4 airframe.parquet uses airframe.log✕
- Connections
- 14 pairs of types, where a type in airframe.parquet uses a type in airframe.log.
- The types involved
wvlet.airframe.parquet.Parquet→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetFieldWriter→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetObjectWriter→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetQueryPlanner→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetRecordReader→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetRecordWriter→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetRecordWriterSupportAdapter→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetSchema→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetSeqWriter→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetStatsReader→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetWriteSupportAdapter→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.ParquetWriterAdapter→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.PrimitiveParquetCodec→wvlet.airframe.log.LogSupportwvlet.airframe.parquet.RecordBuilderImpl→wvlet.airframe.log.LogSupport
- Direction
- airframe.parquet uses airframe.log, so a change to airframe.log can break airframe.parquet, while a change to airframe.parquet can't break airframe.log.
- Position
- Below the diagonal: airframe.parquet uses a module listed above it, which is the healthy direction.
23→8 airframe.parquet uses airframe.msgpack.spi✕
- Connections
- 1 pair of types, where a type in airframe.parquet uses a type in airframe.msgpack.spi.
- The types involved
wvlet.airframe.parquet.ParquetObjectWriter→wvlet.airframe.msgpack.spi.Value
- Direction
- airframe.parquet uses airframe.msgpack.spi, so a change to airframe.msgpack.spi can break airframe.parquet, while a change to airframe.parquet can't break airframe.msgpack.spi.
- Position
- Below the diagonal: airframe.parquet uses a module listed above it, which is the healthy direction.
23→19 airframe.parquet uses airframe.surface✕
- Connections
- 4 pairs of types, where a type in airframe.parquet uses a type in airframe.surface.
- The types involved
wvlet.airframe.parquet.Parquet→wvlet.airframe.surface.Surfacewvlet.airframe.parquet.ParquetReaderAdapter→wvlet.airframe.surface.Surfacewvlet.airframe.parquet.ParquetSchema→wvlet.airframe.surface.Surfacewvlet.airframe.parquet.ParquetWriterAdapter→wvlet.airframe.surface.Surface
- Direction
- airframe.parquet uses airframe.surface, so a change to airframe.surface can break airframe.parquet, while a change to airframe.parquet can't break airframe.surface.
- Position
- Below the diagonal: airframe.parquet uses a module listed above it, which is the healthy direction.
23→20 airframe.parquet uses airframe.http.openapi.OpenAPI✕
- Connections
- 1 pair of types, where a type in airframe.parquet uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.parquet.ParquetObjectWriter→wvlet.airframe.http.openapi.OpenAPI.Parameter
- Direction
- airframe.parquet uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.parquet, while a change to airframe.parquet can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.parquet uses a module listed above it, which is the healthy direction.
24→1 airframe.tracing uses airframe.surface.Primitive✕
- Connections
- 8 pairs of types, where a type in airframe.tracing uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.tracing.ChromeTracer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.tracing.DIStats→wvlet.airframe.surface.Primitive.Longwvlet.airframe.tracing.DIStats→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.tracing.DIStatsReport→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.tracing.DIStatsReport→wvlet.airframe.surface.Primitive.Longwvlet.airframe.tracing.DIStatsReport→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.tracing.DefaultTracer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.tracing.Tracer→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.tracing uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.tracing, while a change to airframe.tracing can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.tracing uses a module listed above it, which is the healthy direction.
24→4 airframe.tracing uses airframe.log✕
- Connections
- 3 pairs of types, where a type in airframe.tracing uses a type in airframe.log.
- The types involved
wvlet.airframe.tracing.DIStats→wvlet.airframe.log.LogSupportwvlet.airframe.tracing.DefaultTracer→wvlet.airframe.log.LogSupportwvlet.airframe.tracing.Tracer→wvlet.airframe.log.LogSupport
- Direction
- airframe.tracing uses airframe.log, so a change to airframe.log can break airframe.tracing, while a change to airframe.tracing can't break airframe.log.
- Position
- Below the diagonal: airframe.tracing uses a module listed above it, which is the healthy direction.
24→19 airframe.tracing uses airframe.surface✕
- Connections
- 3 pairs of types, where a type in airframe.tracing uses a type in airframe.surface.
- The types involved
wvlet.airframe.tracing.DIStats→wvlet.airframe.surface.Surfacewvlet.airframe.tracing.DIStatsReport→wvlet.airframe.surface.Surfacewvlet.airframe.tracing.Tracer→wvlet.airframe.surface.Surface
- Direction
- airframe.tracing uses airframe.surface, so a change to airframe.surface can break airframe.tracing, while a change to airframe.tracing can't break airframe.surface.
- Position
- Below the diagonal: airframe.tracing uses a module listed above it, which is the healthy direction.
24→21 airframe.tracing uses airframe.lifecycle✕
- Connections
- 1 pair of types, where a type in airframe.tracing uses a type in airframe.lifecycle.
- The types involved
wvlet.airframe.tracing.Tracer→wvlet.airframe.lifecycle.Injectee
- Direction
- airframe.tracing uses airframe.lifecycle, so a change to airframe.lifecycle can break airframe.tracing, while a change to airframe.tracing can't break airframe.lifecycle.
- Position
- Below the diagonal: airframe.tracing uses a module listed above it, which is the healthy direction.
24→31 airframe.tracing uses airframe part of a loop✕
- Connections
- 3 pairs of types, where a type in airframe.tracing uses a type in airframe.
- The types involved
wvlet.airframe.tracing.DIStats→wvlet.airframe.Designwvlet.airframe.tracing.DIStats→wvlet.airframe.Sessionwvlet.airframe.tracing.Tracer→wvlet.airframe.Session
- Direction
- airframe.tracing uses airframe, so a change to airframe can break airframe.tracing, while a change to airframe.tracing can't break airframe.
- 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.
25→20 airframe.http.Http uses airframe.http.openapi.OpenAPI✕
- Connections
- 2 pairs of types, where a type in airframe.http.Http uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.Http.Context→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.Http.Filter→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http.Http uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http.Http, while a change to airframe.http.Http can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http.Http uses a module listed above it, which is the healthy direction.
25→22 airframe.http.Http uses airframe.http.HttpMessage✕
- Connections
- 2 pairs of types, where a type in airframe.http.Http uses a type in airframe.http.HttpMessage.
- The types involved
wvlet.airframe.http.Http.Context→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.Http.Filter→wvlet.airframe.http.HttpMessage.Request
- Direction
- airframe.http.Http uses airframe.http.HttpMessage, so a change to airframe.http.HttpMessage can break airframe.http.Http, while a change to airframe.http.Http can't break airframe.http.HttpMessage.
- Position
- Below the diagonal: airframe.http.Http uses a module listed above it, which is the healthy direction.
25→30 airframe.http.Http uses airframe.http part of a loop✕
- Connections
- 4 pairs of types, where a type in airframe.http.Http uses a type in airframe.http.
- The types involved
wvlet.airframe.http.Http.Context→wvlet.airframe.http.HttpBackendwvlet.airframe.http.Http.Context→wvlet.airframe.http.HttpContextwvlet.airframe.http.Http.Filter→wvlet.airframe.http.HttpBackendwvlet.airframe.http.Http.Filter→wvlet.airframe.http.HttpFilter
- Direction
- airframe.http.Http uses airframe.http, so a change to airframe.http can break airframe.http.Http, while a change to airframe.http.Http can't break airframe.http.
- 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.
26→1 airframe.codec uses airframe.surface.Primitive✕
- Connections
- 46 pairs of types, where a type in airframe.codec uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.codec.AnyCodecCompat→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.codec.Compat→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.codec.Compat→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.codec.DataType→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.codec.EnumCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.codec.GenericException→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.codec.GenericStackTraceElement→wvlet.airframe.surface.Primitive.Intwvlet.airframe.codec.GenericStackTraceElement→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.codec.JDBCCodec→wvlet.airframe.surface.Primitive.Intwvlet.airframe.codec.JDBCCodec→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.codec.JSONCodec→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.codec.JSONCodec→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.codec.JSONCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.codec.JSONValueCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.codec.JavaInstantTimeCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.codec.JavaUtilDateCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.codec.LazyCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.codec.MessageCodec→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.codec.MessageCodec→wvlet.airframe.surface.Primitive.Intwvlet.airframe.codec.MessageCodec→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.codec.MessageCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.codec.MessageCodecException→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.codec.MessageCodecFactory→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.codec.MessageContext→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.codec.MessageContext→wvlet.airframe.surface.Primitive.Byte
- Direction
- airframe.codec uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.codec, while a change to airframe.codec can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.codec uses a module listed above it, which is the healthy direction.
26→3 airframe.codec uses airframe.http.RPCEncoding✕
- Connections
- 1 pair of types, where a type in airframe.codec uses a type in airframe.http.RPCEncoding.
- The types involved
wvlet.airframe.codec.MessageCodec→wvlet.airframe.http.RPCEncoding.MsgPack
- Direction
- airframe.codec uses airframe.http.RPCEncoding, so a change to airframe.http.RPCEncoding can break airframe.codec, while a change to airframe.codec can't break airframe.http.RPCEncoding.
- Position
- Below the diagonal: airframe.codec uses a module listed above it, which is the healthy direction.
26→4 airframe.codec uses airframe.log✕
- Connections
- 8 pairs of types, where a type in airframe.codec uses a type in airframe.log.
- The types involved
wvlet.airframe.codec.JDBCCodec→wvlet.airframe.log.LogSupportwvlet.airframe.codec.JavaUtilDateCodec→wvlet.airframe.log.LogSupportwvlet.airframe.codec.MessageCodec→wvlet.airframe.log.LogSupportwvlet.airframe.codec.MessageCodecFactory→wvlet.airframe.log.LogSupportwvlet.airframe.codec.ObjectCodec→wvlet.airframe.log.LogSupportwvlet.airframe.codec.ObjectMapCodec→wvlet.airframe.log.LogSupportwvlet.airframe.codec.ParamListCodec→wvlet.airframe.log.LogSupportwvlet.airframe.codec.StringUnapplyCodec→wvlet.airframe.log.LogSupport
- Direction
- airframe.codec uses airframe.log, so a change to airframe.log can break airframe.codec, while a change to airframe.codec can't break airframe.log.
- Position
- Below the diagonal: airframe.codec uses a module listed above it, which is the healthy direction.
26→8 airframe.codec uses airframe.msgpack.spi✕
- Connections
- 39 pairs of types, where a type in airframe.codec uses a type in airframe.msgpack.spi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.codec.EnumCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.EnumCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.JSONCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.JSONCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.JSONValueCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.JSONValueCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.JavaInstantTimeCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.JavaInstantTimeCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.JavaUtilDateCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.JavaUtilDateCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.LazyCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.LazyCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.MessageCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.MessageCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.MessageValueCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.MessageValueCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.MessageValueCodec→wvlet.airframe.msgpack.spi.Valuewvlet.airframe.codec.ObjectCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.ObjectCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.ObjectMapCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.ObjectMapCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.codec.PackAsMapSupport→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.PackSupport→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.ParamListCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.codec.ParamListCodec→wvlet.airframe.msgpack.spi.Unpacker
- Direction
- airframe.codec uses airframe.msgpack.spi, so a change to airframe.msgpack.spi can break airframe.codec, while a change to airframe.codec can't break airframe.msgpack.spi.
- Position
- Below the diagonal: airframe.codec uses a module listed above it, which is the healthy direction.
26→18 airframe.codec uses airframe.sql.model.LogicalPlan✕
- Connections
- 1 pair of types, where a type in airframe.codec uses a type in airframe.sql.model.LogicalPlan.
- The types involved
wvlet.airframe.codec.UnionCodec→wvlet.airframe.sql.model.LogicalPlan.Union
- Direction
- airframe.codec uses airframe.sql.model.LogicalPlan, so a change to airframe.sql.model.LogicalPlan can break airframe.codec, while a change to airframe.codec can't break airframe.sql.model.LogicalPlan.
- Position
- Below the diagonal: airframe.codec uses a module listed above it, which is the healthy direction.
26→19 airframe.codec uses airframe.surface✕
- Connections
- 11 pairs of types, where a type in airframe.codec uses a type in airframe.surface.
- The types involved
wvlet.airframe.codec.Compat→wvlet.airframe.surface.Surfacewvlet.airframe.codec.CompatBase→wvlet.airframe.surface.Surfacewvlet.airframe.codec.JavaStandardCodec→wvlet.airframe.surface.Surfacewvlet.airframe.codec.LazyCodec→wvlet.airframe.surface.Surfacewvlet.airframe.codec.MessageCodecFactory→wvlet.airframe.surface.Surfacewvlet.airframe.codec.MessageCodecFinder→wvlet.airframe.surface.Surfacewvlet.airframe.codec.ObjectCodec→wvlet.airframe.surface.Surfacewvlet.airframe.codec.ObjectMapCodec→wvlet.airframe.surface.Surfacewvlet.airframe.codec.PrimitiveCodec→wvlet.airframe.surface.Surfacewvlet.airframe.codec.StandardCodec→wvlet.airframe.surface.Surfacewvlet.airframe.codec.UnionCodec→wvlet.airframe.surface.Surface
- Direction
- airframe.codec uses airframe.surface, so a change to airframe.surface can break airframe.codec, while a change to airframe.codec can't break airframe.surface.
- Position
- Below the diagonal: airframe.codec uses a module listed above it, which is the healthy direction.
26→20 airframe.codec uses airframe.http.openapi.OpenAPI✕
- Connections
- 1 pair of types, where a type in airframe.codec uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.codec.ParamListCodec→wvlet.airframe.http.openapi.OpenAPI.Parameter
- Direction
- airframe.codec uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.codec, while a change to airframe.codec can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.codec uses a module listed above it, which is the healthy direction.
26→25 airframe.codec uses airframe.http.Http✕
- Connections
- 1 pair of types, where a type in airframe.codec uses a type in airframe.http.Http.
- The types involved
wvlet.airframe.codec.CodecMacros→wvlet.airframe.http.Http.Context
- Direction
- airframe.codec uses airframe.http.Http, so a change to airframe.http.Http can break airframe.codec, while a change to airframe.codec can't break airframe.http.Http.
- Position
- Below the diagonal: airframe.codec uses a module listed above it, which is the healthy direction.
27→1 airframe.http.client uses airframe.surface.Primitive✕
- Connections
- 27 pairs of types, where a type in airframe.http.client uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.http.client.AsyncClient→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.AsyncClientImpl→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.CurlBindings→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.client.CurlBindings→wvlet.airframe.surface.Primitive.Longwvlet.airframe.http.client.CurlBindings→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.CurlCallbacks→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.client.CurlCallbacks→wvlet.airframe.surface.Primitive.Longwvlet.airframe.http.client.CurlCallbacks→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.client.CurlCallbacks→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.CurlChannel→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.client.CurlChannel→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.client.CurlChannel→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.client.HttpClientContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.client.HttpClientLoggingFilter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.HttpClients→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.client.HttpClients→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.client.JSFetchChannel→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.JSHttpClientChannel→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.JavaHttpClientBackend→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.client.JavaHttpClientChannel→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.client.NativeHttpClientBackend→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.client.NativeHttpClientBackend→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.client.SyncClient→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.http.client uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.client, while a change to airframe.http.client can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→2 airframe.http.client uses airframe.control.Retry✕
- Connections
- 5 pairs of types, where a type in airframe.http.client uses a type in airframe.control.Retry.
- The types involved
wvlet.airframe.http.client.HttpClientBackend→wvlet.airframe.control.Retry.RetryContextwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.control.Retry.RetryContextwvlet.airframe.http.client.HttpClientFactory→wvlet.airframe.control.Retry.RetryContextwvlet.airframe.http.client.HttpClients→wvlet.airframe.control.Retry.RetryContextwvlet.airframe.http.client.JSHttpClientBackend→wvlet.airframe.control.Retry.RetryContext
- Direction
- airframe.http.client uses airframe.control.Retry, so a change to airframe.control.Retry can break airframe.http.client, while a change to airframe.http.client can't break airframe.control.Retry.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→4 airframe.http.client uses airframe.log✕
- Connections
- 7 pairs of types, where a type in airframe.http.client uses a type in airframe.log.
- The types involved
wvlet.airframe.http.client.AsyncClient→wvlet.airframe.log.LogSupportwvlet.airframe.http.client.CurlChannel→wvlet.airframe.log.LogSupportwvlet.airframe.http.client.HttpClientLoggingFilter→wvlet.airframe.log.LogSupportwvlet.airframe.http.client.HttpClients→wvlet.airframe.log.LogSupportwvlet.airframe.http.client.JSFetchChannel→wvlet.airframe.log.LogSupportwvlet.airframe.http.client.JSHttpClientChannel→wvlet.airframe.log.LogSupportwvlet.airframe.http.client.JavaHttpClientChannel→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.client uses airframe.log, so a change to airframe.log can break airframe.http.client, while a change to airframe.http.client can't break airframe.log.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→6 airframe.http.client uses airframe.control✕
- Connections
- 5 pairs of types, where a type in airframe.http.client uses a type in airframe.control.
- The types involved
wvlet.airframe.http.client.AsyncClient→wvlet.airframe.control.CircuitBreakerwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.control.CircuitBreakerwvlet.airframe.http.client.HttpClientFactory→wvlet.airframe.control.CircuitBreakerwvlet.airframe.http.client.HttpClients→wvlet.airframe.control.Resourcewvlet.airframe.http.client.SyncClient→wvlet.airframe.control.CircuitBreaker
- Direction
- airframe.http.client uses airframe.control, so a change to airframe.control can break airframe.http.client, while a change to airframe.http.client can't break airframe.control.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→17 airframe.http.client uses airframe.rx✕
- Connections
- 7 pairs of types, where a type in airframe.http.client uses a type in airframe.rx.
- The types involved
wvlet.airframe.http.client.AsyncClient→wvlet.airframe.rx.Rxwvlet.airframe.http.client.CurlChannel→wvlet.airframe.rx.Rxwvlet.airframe.http.client.HttpChannel→wvlet.airframe.rx.Rxwvlet.airframe.http.client.JSFetchChannel→wvlet.airframe.rx.Rxwvlet.airframe.http.client.JSHttpClientChannel→wvlet.airframe.rx.Rxwvlet.airframe.http.client.JavaHttpClientChannel→wvlet.airframe.rx.Rxwvlet.airframe.http.client.URLConnectionChannel→wvlet.airframe.rx.Rx
- Direction
- airframe.http.client uses airframe.rx, so a change to airframe.rx can break airframe.http.client, while a change to airframe.http.client can't break airframe.rx.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→19 airframe.http.client uses airframe.surface✕
- Connections
- 3 pairs of types, where a type in airframe.http.client uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.client.AsyncClient→wvlet.airframe.surface.Surfacewvlet.airframe.http.client.HttpClients→wvlet.airframe.surface.Surfacewvlet.airframe.http.client.SyncClient→wvlet.airframe.surface.Surface
- Direction
- airframe.http.client uses airframe.surface, so a change to airframe.surface can break airframe.http.client, while a change to airframe.http.client can't break airframe.surface.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→20 airframe.http.client uses airframe.http.openapi.OpenAPI✕
- Connections
- 11 pairs of types, where a type in airframe.http.client uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.client.AsyncClient→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.CurlChannel→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.HttpChannel→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.HttpClientFactory→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.HttpClients→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.JSFetchChannel→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.JSHttpClientChannel→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.JavaHttpClientChannel→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.SyncClient→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.client.URLConnectionChannel→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http.client uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http.client, while a change to airframe.http.client can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→22 airframe.http.client uses airframe.http.HttpMessage✕
- Connections
- 11 pairs of types, where a type in airframe.http.client uses a type in airframe.http.HttpMessage.
- The types involved
wvlet.airframe.http.client.AsyncClient→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.CurlChannel→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.HttpChannel→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.HttpClientFactory→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.HttpClients→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.JSFetchChannel→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.JSHttpClientChannel→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.JavaHttpClientChannel→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.SyncClient→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.client.URLConnectionChannel→wvlet.airframe.http.HttpMessage.Request
- Direction
- airframe.http.client uses airframe.http.HttpMessage, so a change to airframe.http.HttpMessage can break airframe.http.client, while a change to airframe.http.client can't break airframe.http.HttpMessage.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→26 airframe.http.client uses airframe.codec✕
- Connections
- 1 pair of types, where a type in airframe.http.client uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.codec.MessageCodecFactory
- Direction
- airframe.http.client uses airframe.codec, so a change to airframe.codec can break airframe.http.client, while a change to airframe.http.client can't break airframe.codec.
- Position
- Below the diagonal: airframe.http.client uses a module listed above it, which is the healthy direction.
27→30 airframe.http.client uses airframe.http part of a loop✕
- Connections
- 33 pairs of types, where a type in airframe.http.client uses a type in airframe.http. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.http.client.AsyncClient→wvlet.airframe.http.HttpLoggerwvlet.airframe.http.client.AsyncClient→wvlet.airframe.http.RPCMethodwvlet.airframe.http.client.CurlChannel→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.client.CurlChannel→wvlet.airframe.http.ServerAddresswvlet.airframe.http.client.HttpChannel→wvlet.airframe.http.ServerAddresswvlet.airframe.http.client.HttpClientBackend→wvlet.airframe.http.ServerAddresswvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.http.HttpLoggerwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.http.HttpLoggerConfigwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.http.RPCEncodingwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.http.RxHttpFilterwvlet.airframe.http.client.HttpClientConfig→wvlet.airframe.http.ServerAddresswvlet.airframe.http.client.HttpClientContext→wvlet.airframe.http.RPCMethodwvlet.airframe.http.client.HttpClientFactory→wvlet.airframe.http.RPCEncodingwvlet.airframe.http.client.HttpClientFactory→wvlet.airframe.http.RxHttpFilterwvlet.airframe.http.client.HttpClientFilter→wvlet.airframe.http.RxHttpFilterwvlet.airframe.http.client.HttpClientLoggingFilter→wvlet.airframe.http.RxHttpFilterwvlet.airframe.http.client.HttpClients→wvlet.airframe.http.HttpClientExceptionwvlet.airframe.http.client.HttpClients→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.client.JSFetchChannel→wvlet.airframe.http.ServerAddresswvlet.airframe.http.client.JSFetchChannel→wvlet.airframe.http.ServerSentEventHandlerwvlet.airframe.http.client.JSHttpClientBackend→wvlet.airframe.http.ServerAddresswvlet.airframe.http.client.JSHttpClientChannel→wvlet.airframe.http.ServerAddresswvlet.airframe.http.client.JavaHttpClientBackend→wvlet.airframe.http.ServerAddresswvlet.airframe.http.client.JavaHttpClientChannel→wvlet.airframe.http.HttpClientwvlet.airframe.http.client.JavaHttpClientChannel→wvlet.airframe.http.HttpRequest
- Direction
- airframe.http.client uses airframe.http, so a change to airframe.http can break airframe.http.client, while a change to airframe.http.client can't break airframe.http.
- 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.
28→1 airframe.http.router uses airframe.surface.Primitive✕
- Connections
- 8 pairs of types, where a type in airframe.http.router uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.router.ControllerRoute→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.router.ControllerRoute→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.router.Route→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.router.Route→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.router.RouteMatch→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.router.RxRoute→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.http.router uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.router, while a change to airframe.http.router can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→4 airframe.http.router uses airframe.log✕
- Connections
- 5 pairs of types, where a type in airframe.http.router uses a type in airframe.log.
- The types involved
wvlet.airframe.http.router.ControllerRoute→wvlet.airframe.log.LogSupportwvlet.airframe.http.router.HttpEndpointExecutionContext→wvlet.airframe.log.LogSupportwvlet.airframe.http.router.HttpRequestDispatcher→wvlet.airframe.log.LogSupportwvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.log.LogSupportwvlet.airframe.http.router.RedirectToRxEndpoint→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.router uses airframe.log, so a change to airframe.log can break airframe.http.router, while a change to airframe.http.router can't break airframe.log.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→5 airframe.http.router uses airframe.rx.html.widget.editor.monaco✕
- Connections
- 1 pair of types, where a type in airframe.http.router uses a type in airframe.rx.html.widget.editor.monaco.
- The types involved
wvlet.airframe.http.router.Automaton→wvlet.airframe.rx.html.widget.editor.monaco.Token
- Direction
- airframe.http.router uses airframe.rx.html.widget.editor.monaco, so a change to airframe.rx.html.widget.editor.monaco can break airframe.http.router, while a change to airframe.http.router can't break airframe.rx.html.widget.editor.monaco.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→8 airframe.http.router uses airframe.msgpack.spi✕
- Connections
- 1 pair of types, where a type in airframe.http.router uses a type in airframe.msgpack.spi.
- The types involved
wvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.msgpack.spi.Value
- Direction
- airframe.http.router uses airframe.msgpack.spi, so a change to airframe.msgpack.spi can break airframe.http.router, while a change to airframe.http.router can't break airframe.msgpack.spi.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→13 airframe.http.router uses airframe.launcher.StringTree✕
- Connections
- 1 pair of types, where a type in airframe.http.router uses a type in airframe.launcher.StringTree.
- The types involved
wvlet.airframe.http.router.Automaton→wvlet.airframe.launcher.StringTree.Node
- Direction
- airframe.http.router uses airframe.launcher.StringTree, so a change to airframe.launcher.StringTree can break airframe.http.router, while a change to airframe.http.router can't break airframe.launcher.StringTree.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→17 airframe.http.router uses airframe.rx✕
- Connections
- 1 pair of types, where a type in airframe.http.router uses a type in airframe.rx.
- The types involved
wvlet.airframe.http.router.RedirectToRxEndpoint→wvlet.airframe.rx.Rx
- Direction
- airframe.http.router uses airframe.rx, so a change to airframe.rx can break airframe.http.router, while a change to airframe.http.router can't break airframe.rx.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→19 airframe.http.router uses airframe.surface✕
- Connections
- 9 pairs of types, where a type in airframe.http.router uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.router.ControllerProvider→wvlet.airframe.surface.Surfacewvlet.airframe.http.router.ControllerRoute→wvlet.airframe.surface.MethodSurfacewvlet.airframe.http.router.ControllerRoute→wvlet.airframe.surface.Surfacewvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.surface.MethodSurfacewvlet.airframe.http.router.ResponseHandler→wvlet.airframe.surface.Surfacewvlet.airframe.http.router.Route→wvlet.airframe.surface.MethodSurfacewvlet.airframe.http.router.Route→wvlet.airframe.surface.Surfacewvlet.airframe.http.router.RxRoute→wvlet.airframe.surface.MethodSurfacewvlet.airframe.http.router.RxRoute→wvlet.airframe.surface.Surface
- Direction
- airframe.http.router uses airframe.surface, so a change to airframe.surface can break airframe.http.router, while a change to airframe.http.router can't break airframe.surface.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→20 airframe.http.router uses airframe.http.openapi.OpenAPI✕
- Connections
- 1 pair of types, where a type in airframe.http.router uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.router.RedirectToRxEndpoint→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http.router uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http.router, while a change to airframe.http.router can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→25 airframe.http.router uses airframe.http.Http✕
- Connections
- 1 pair of types, where a type in airframe.http.router uses a type in airframe.http.Http.
- The types involved
wvlet.airframe.http.router.RouterMacros→wvlet.airframe.http.Http.Context
- Direction
- airframe.http.router uses airframe.http.Http, so a change to airframe.http.Http can break airframe.http.router, while a change to airframe.http.router can't break airframe.http.Http.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→26 airframe.http.router uses airframe.codec✕
- Connections
- 5 pairs of types, where a type in airframe.http.router uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.router.ControllerRoute→wvlet.airframe.codec.MessageCodecFactorywvlet.airframe.http.router.HttpRequestDispatcher→wvlet.airframe.codec.MessageCodecFactorywvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.codec.MessageCodecFactorywvlet.airframe.http.router.Route→wvlet.airframe.codec.MessageCodecFactorywvlet.airframe.http.router.RouteMatch→wvlet.airframe.codec.MessageCodecFactory
- Direction
- airframe.http.router uses airframe.codec, so a change to airframe.codec can break airframe.http.router, while a change to airframe.http.router can't break airframe.codec.
- Position
- Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
28→30 airframe.http.router uses airframe.http part of a loop✕
- Connections
- 13 pairs of types, where a type in airframe.http.router uses a type in airframe.http.
- The types involved
wvlet.airframe.http.router.ControllerRoute→wvlet.airframe.http.HttpContextwvlet.airframe.http.router.ControllerRoute→wvlet.airframe.http.RPCMethodwvlet.airframe.http.router.HttpEndpointExecutionContext→wvlet.airframe.http.HttpBackendwvlet.airframe.http.router.HttpEndpointExecutionContext→wvlet.airframe.http.HttpContextwvlet.airframe.http.router.HttpRequestDispatcher→wvlet.airframe.http.HttpBackendwvlet.airframe.http.router.HttpRequestDispatcher→wvlet.airframe.http.HttpFilterwvlet.airframe.http.router.HttpRequestDispatcher→wvlet.airframe.http.Routerwvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.http.HttpContextwvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.http.HttpRequestAdapterwvlet.airframe.http.router.HttpRequestMapper→wvlet.airframe.http.RPCExceptionwvlet.airframe.http.router.Route→wvlet.airframe.http.HttpContextwvlet.airframe.http.router.RouteMatch→wvlet.airframe.http.HttpContextwvlet.airframe.http.router.RouterObjectMacros→wvlet.airframe.http.Router
- Direction
- airframe.http.router uses airframe.http, so a change to airframe.http can break airframe.http.router, while a change to airframe.http.router can't break airframe.http.
- 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.
28→31 airframe.http.router uses airframe part of a loop✕
- Connections
- 5 pairs of types, where a type in airframe.http.router uses a type in airframe.
- The types involved
wvlet.airframe.http.router.ControllerProvider→wvlet.airframe.Sessionwvlet.airframe.http.router.ControllerRoute→wvlet.airframe.Sessionwvlet.airframe.http.router.HttpRequestDispatcher→wvlet.airframe.Sessionwvlet.airframe.http.router.Route→wvlet.airframe.Sessionwvlet.airframe.http.router.RouteMatch→wvlet.airframe.Session
- Direction
- airframe.http.router uses airframe, so a change to airframe can break airframe.http.router, while a change to airframe.http.router can't break airframe.
- 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.
29→1 airframe.http.finagle uses airframe.surface.Primitive✕
- Connections
- 25 pairs of types, where a type in airframe.http.finagle uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.finagle.Finagle→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.finagle.FinagleClient→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleClient→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.finagle.FinagleClientConfig→wvlet.airframe.surface.Primitive.Doublewvlet.airframe.http.finagle.FinagleClientConfig→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.finagle.FinagleClientConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleContextAdapter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleContextAdapter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.finagle.FinagleHttpRequestAdapter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleHttpResponseAdapter→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.finagle.FinagleHttpResponseAdapter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleRPCContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleRPCContext→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.finagle.FinagleResponseHandler→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.finagle.FinagleServer→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.finagle.FinagleServer→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleServer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleServerFactory→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.finagle.FinagleServerFactory→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.finagle.FinagleServerFactory→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.http.finagle uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→2 airframe.http.finagle uses airframe.control.Retry✕
- Connections
- 2 pairs of types, where a type in airframe.http.finagle uses a type in airframe.control.Retry.
- The types involved
wvlet.airframe.http.finagle.FinagleClientConfig→wvlet.airframe.control.Retry.RetryContextwvlet.airframe.http.finagle.FinagleRetryFilter→wvlet.airframe.control.Retry.RetryContext
- Direction
- airframe.http.finagle uses airframe.control.Retry, so a change to airframe.control.Retry can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.control.Retry.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→4 airframe.http.finagle uses airframe.log✕
- Connections
- 6 pairs of types, where a type in airframe.http.finagle uses a type in airframe.log.
- The types involved
wvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.log.LogSupportwvlet.airframe.http.finagle.FinagleClient→wvlet.airframe.log.LogSupportwvlet.airframe.http.finagle.FinagleResponseHandler→wvlet.airframe.log.LogSupportwvlet.airframe.http.finagle.FinagleRetryFilter→wvlet.airframe.log.LogSupportwvlet.airframe.http.finagle.FinagleServer→wvlet.airframe.log.LogSupportwvlet.airframe.http.finagle.FinagleServerFactory→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.finagle uses airframe.log, so a change to airframe.log can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.log.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→6 airframe.http.finagle uses airframe.control✕
- Connections
- 1 pair of types, where a type in airframe.http.finagle uses a type in airframe.control.
- The types involved
wvlet.airframe.http.finagle.FinagleClient→wvlet.airframe.control.Resource
- Direction
- airframe.http.finagle uses airframe.control, so a change to airframe.control can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.control.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→19 airframe.http.finagle uses airframe.surface✕
- Connections
- 2 pairs of types, where a type in airframe.http.finagle uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.finagle.FinagleResponseHandler→wvlet.airframe.surface.Surfacewvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.surface.Surface
- Direction
- airframe.http.finagle uses airframe.surface, so a change to airframe.surface can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.surface.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→20 airframe.http.finagle uses airframe.http.openapi.OpenAPI✕
- Connections
- 11 pairs of types, where a type in airframe.http.finagle uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleClient→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleContextAdapter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleFilter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleFilterAdapter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleHttpResponseAdapter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleHttpResponseWrapper→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleResponseHandler→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleRetryFilter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleRouter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http.finagle uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→22 airframe.http.finagle uses airframe.http.HttpMessage✕
- Connections
- 14 pairs of types, where a type in airframe.http.finagle uses a type in airframe.http.HttpMessage.
- The types involved
wvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleClient→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleContextAdapter→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleFilter→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleFilterAdapter→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleHttpRequestAdapter→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.finagle.FinagleHttpRequestAdapter→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleHttpRequestWrapper→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleHttpResponseAdapter→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.finagle.FinagleRPCContext→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleResponseHandler→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleRetryFilter→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleRouter→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.http.HttpMessage.Request
- Direction
- airframe.http.finagle uses airframe.http.HttpMessage, so a change to airframe.http.HttpMessage can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.http.HttpMessage.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→24 airframe.http.finagle uses airframe.tracing✕
- Connections
- 1 pair of types, where a type in airframe.http.finagle uses a type in airframe.tracing.
- The types involved
wvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.tracing.Tracer
- Direction
- airframe.http.finagle uses airframe.tracing, so a change to airframe.tracing can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.tracing.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→25 airframe.http.finagle uses airframe.http.Http✕
- Connections
- 4 pairs of types, where a type in airframe.http.finagle uses a type in airframe.http.Http.
- The types involved
wvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.http.Http.Filterwvlet.airframe.http.finagle.FinagleContextAdapter→wvlet.airframe.http.Http.Contextwvlet.airframe.http.finagle.FinagleFilterAdapter→wvlet.airframe.http.Http.Contextwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.http.Http.Filter
- Direction
- airframe.http.finagle uses airframe.http.Http, so a change to airframe.http.Http can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.http.Http.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→26 airframe.http.finagle uses airframe.codec✕
- Connections
- 2 pairs of types, where a type in airframe.http.finagle uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.finagle.FinagleClientConfig→wvlet.airframe.codec.MessageCodecFactorywvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.codec.MessageCodec
- Direction
- airframe.http.finagle uses airframe.codec, so a change to airframe.codec can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.codec.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→28 airframe.http.finagle uses airframe.http.router✕
- Connections
- 4 pairs of types, where a type in airframe.http.finagle uses a type in airframe.http.router.
- The types involved
wvlet.airframe.http.finagle.FinagleResponseHandler→wvlet.airframe.http.router.ResponseHandlerwvlet.airframe.http.finagle.FinagleResponseHandler→wvlet.airframe.http.router.Routewvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.http.router.ControllerProviderwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.http.router.ResponseHandler
- Direction
- airframe.http.finagle uses airframe.http.router, so a change to airframe.http.router can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.http.router.
- Position
- Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy direction.
29→30 airframe.http.finagle uses airframe.http part of a loop✕
- Connections
- 25 pairs of types, where a type in airframe.http.finagle uses a type in airframe.http.
- The types involved
wvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.http.HttpBackendwvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.http.HttpFilterwvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.http.HttpRequestAdapterwvlet.airframe.http.finagle.FinagleBackend→wvlet.airframe.http.HttpStatuswvlet.airframe.http.finagle.FinagleClient→wvlet.airframe.http.HttpClientwvlet.airframe.http.finagle.FinagleClient→wvlet.airframe.http.HttpResponsewvlet.airframe.http.finagle.FinagleClientConfig→wvlet.airframe.http.Httpwvlet.airframe.http.finagle.FinagleFilter→wvlet.airframe.http.HttpBackendwvlet.airframe.http.finagle.FinagleFilter→wvlet.airframe.http.HttpFilterwvlet.airframe.http.finagle.FinagleHttpRequestAdapter→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.finagle.FinagleHttpRequestAdapter→wvlet.airframe.http.HttpRequestwvlet.airframe.http.finagle.FinagleHttpRequestAdapter→wvlet.airframe.http.HttpRequestAdapterwvlet.airframe.http.finagle.FinagleHttpRequestAdapter→wvlet.airframe.http.ServerAddresswvlet.airframe.http.finagle.FinagleHttpRequestWrapper→wvlet.airframe.http.HttpRequestwvlet.airframe.http.finagle.FinagleHttpRequestWrapper→wvlet.airframe.http.HttpRequestAdapterwvlet.airframe.http.finagle.FinagleHttpResponseAdapter→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.finagle.FinagleHttpResponseAdapter→wvlet.airframe.http.HttpResponsewvlet.airframe.http.finagle.FinagleHttpResponseAdapter→wvlet.airframe.http.HttpResponseAdapterwvlet.airframe.http.finagle.FinagleHttpResponseWrapper→wvlet.airframe.http.HttpResponsewvlet.airframe.http.finagle.FinagleHttpResponseWrapper→wvlet.airframe.http.HttpResponseAdapterwvlet.airframe.http.finagle.FinagleRPCContext→wvlet.airframe.http.RPCContextwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.http.Httpwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.http.Routerwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.http.RxRouterwvlet.airframe.http.finagle.FinagleServerFactory→wvlet.airframe.http.Router
- Direction
- airframe.http.finagle uses airframe.http, so a change to airframe.http can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.http.
- 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.
29→31 airframe.http.finagle uses airframe part of a loop✕
- Connections
- 4 pairs of types, where a type in airframe.http.finagle uses a type in airframe.
- The types involved
wvlet.airframe.http.finagle.FinagleClientConfig→wvlet.airframe.Designwvlet.airframe.http.finagle.FinagleClientConfig→wvlet.airframe.httpwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.Designwvlet.airframe.http.finagle.FinagleServerConfig→wvlet.airframe.Session
- Direction
- airframe.http.finagle uses airframe, so a change to airframe can break airframe.http.finagle, while a change to airframe.http.finagle can't break airframe.
- 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.
30→1 airframe.http uses airframe.surface.Primitive✕
- Connections
- 98 pairs of types, where a type in airframe.http uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.http.Compat→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.Compat→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.CompatApi→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.CompatApi→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.EmptyRPCContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.EmptyRPCContext→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.GrpcStatus→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.GrpcStatus→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.GrpcStatus→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.Http→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpAccessLogConfig→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.HttpAccessLogConfig→wvlet.airframe.surface.Primitive.Longwvlet.airframe.http.HttpAccessLogConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpAccessLogWriter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpAccessLogWriter→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.HttpBackend→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.HttpBackend→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpBackend→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.HttpClientBase→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpClientException→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.HttpClientException→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpContext→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.HttpFilter→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.HttpLogger→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.http uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http, while a change to airframe.http can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→2 airframe.http uses airframe.control.Retry✕
- Connections
- 1 pair of types, where a type in airframe.http uses a type in airframe.control.Retry.
- The types involved
wvlet.airframe.http.HttpClientMaxRetryException→wvlet.airframe.control.Retry.RetryContext
- Direction
- airframe.http uses airframe.control.Retry, so a change to airframe.control.Retry can break airframe.http, while a change to airframe.http can't break airframe.control.Retry.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→3 airframe.http uses airframe.http.RPCEncoding✕
- Connections
- 3 pairs of types, where a type in airframe.http uses a type in airframe.http.RPCEncoding.
- The types involved
wvlet.airframe.http.HttpMessage→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.http.HttpServerException→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.http.RPCException→wvlet.airframe.http.RPCEncoding.MsgPack
- Direction
- airframe.http uses airframe.http.RPCEncoding, so a change to airframe.http.RPCEncoding can break airframe.http, while a change to airframe.http can't break airframe.http.RPCEncoding.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→4 airframe.http uses airframe.log✕
- Connections
- 3 pairs of types, where a type in airframe.http uses a type in airframe.log.
- The types involved
wvlet.airframe.http.RPCException→wvlet.airframe.log.LogSupportwvlet.airframe.http.Router→wvlet.airframe.log.LogSupportwvlet.airframe.http.StaticContent→wvlet.airframe.log.LogSupport
- Direction
- airframe.http uses airframe.log, so a change to airframe.log can break airframe.http, while a change to airframe.http can't break airframe.log.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→6 airframe.http uses airframe.control✕
- Connections
- 3 pairs of types, where a type in airframe.http uses a type in airframe.control.
- The types involved
wvlet.airframe.http.HttpClientBase→wvlet.airframe.control.Resourcewvlet.airframe.http.HttpSyncClientAdapterBase→wvlet.airframe.control.Resourcewvlet.airframe.http.HttpSyncClientBase→wvlet.airframe.control.Resource
- Direction
- airframe.http uses airframe.control, so a change to airframe.control can break airframe.http, while a change to airframe.http can't break airframe.control.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→8 airframe.http uses airframe.msgpack.spi✕
- Connections
- 5 pairs of types, where a type in airframe.http uses a type in airframe.msgpack.spi.
- The types involved
wvlet.airframe.http.GrpcStatus→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.http.HttpStatus→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.http.RPCEncoding→wvlet.airframe.msgpack.spi.Valuewvlet.airframe.http.RPCStatus→wvlet.airframe.msgpack.spi.Valuewvlet.airframe.http.RPCStatusType→wvlet.airframe.msgpack.spi.Packer
- Direction
- airframe.http uses airframe.msgpack.spi, so a change to airframe.msgpack.spi can break airframe.http, while a change to airframe.http can't break airframe.msgpack.spi.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→17 airframe.http uses airframe.rx✕
- Connections
- 3 pairs of types, where a type in airframe.http uses a type in airframe.rx.
- The types involved
wvlet.airframe.http.RxHttpEndpoint→wvlet.airframe.rx.Rxwvlet.airframe.http.RxHttpFilter→wvlet.airframe.rx.Rxwvlet.airframe.http.finagle→wvlet.airframe.rx.Rx
- Direction
- airframe.http uses airframe.rx, so a change to airframe.rx can break airframe.http, while a change to airframe.http can't break airframe.rx.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→19 airframe.http uses airframe.surface✕
- Connections
- 5 pairs of types, where a type in airframe.http uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.HttpLoggerConfig→wvlet.airframe.surface.Surfacewvlet.airframe.http.HttpSyncClient→wvlet.airframe.surface.Surfacewvlet.airframe.http.RPCMethod→wvlet.airframe.surface.Surfacewvlet.airframe.http.Router→wvlet.airframe.surface.MethodSurfacewvlet.airframe.http.Router→wvlet.airframe.surface.Surface
- Direction
- airframe.http uses airframe.surface, so a change to airframe.surface can break airframe.http, while a change to airframe.http can't break airframe.surface.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→20 airframe.http uses airframe.http.openapi.OpenAPI✕
- Connections
- 10 pairs of types, where a type in airframe.http uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.Http→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.HttpResponse→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.HttpResponseAdapter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.HttpServerException→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.HttpSyncClient→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.RPCException→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.RxHttpEndpoint→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.RxHttpFilter→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.StaticContent→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.finagle→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http, while a change to airframe.http can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→22 airframe.http uses airframe.http.HttpMessage✕
- Connections
- 16 pairs of types, where a type in airframe.http uses a type in airframe.http.HttpMessage.
- The types involved
wvlet.airframe.http.EmptyRPCContext→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.Http→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.HttpMessage→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.HttpRequest→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.HttpRequest→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.HttpRequestAdapter→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.HttpRequestAdapter→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.HttpResponse→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.HttpResponseAdapter→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.HttpServerException→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.HttpSyncClient→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.RxHttpEndpoint→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.RxHttpFilter→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.WebSocketContext→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.finagle→wvlet.airframe.http.HttpMessage.Messagewvlet.airframe.http.finagle→wvlet.airframe.http.HttpMessage.Request
- Direction
- airframe.http uses airframe.http.HttpMessage, so a change to airframe.http.HttpMessage can break airframe.http, while a change to airframe.http can't break airframe.http.HttpMessage.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→25 airframe.http uses airframe.http.Http✕
- Connections
- 5 pairs of types, where a type in airframe.http uses a type in airframe.http.Http.
- The types involved
wvlet.airframe.http.HttpBackend→wvlet.airframe.http.Http.Contextwvlet.airframe.http.HttpBackend→wvlet.airframe.http.Http.Filterwvlet.airframe.http.HttpFilter→wvlet.airframe.http.Http.Contextwvlet.airframe.http.HttpFilter→wvlet.airframe.http.Http.Filterwvlet.airframe.http.RxRouterMacros→wvlet.airframe.http.Http.Context
- Direction
- airframe.http uses airframe.http.Http, so a change to airframe.http.Http can break airframe.http, while a change to airframe.http can't break airframe.http.Http.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→26 airframe.http uses airframe.codec✕
- Connections
- 7 pairs of types, where a type in airframe.http uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.GrpcStatus→wvlet.airframe.codec.PackSupportwvlet.airframe.http.HttpLoggerConfig→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.HttpLoggerConfig→wvlet.airframe.codec.MessageCodecFactorywvlet.airframe.http.HttpStatus→wvlet.airframe.codec.PackSupportwvlet.airframe.http.RPCEncoding→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.RPCErrorMessage→wvlet.airframe.codec.GenericStackTraceElementwvlet.airframe.http.RPCStatusType→wvlet.airframe.codec.PackSupport
- Direction
- airframe.http uses airframe.codec, so a change to airframe.codec can break airframe.http, while a change to airframe.http can't break airframe.codec.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→27 airframe.http uses airframe.http.client✕
- Connections
- 3 pairs of types, where a type in airframe.http uses a type in airframe.http.client.
- The types involved
wvlet.airframe.http.Compat→wvlet.airframe.http.client.HttpClientBackendwvlet.airframe.http.CompatApi→wvlet.airframe.http.client.HttpClientBackendwvlet.airframe.http.Http→wvlet.airframe.http.client.HttpClientConfig
- Direction
- airframe.http uses airframe.http.client, so a change to airframe.http.client can break airframe.http, while a change to airframe.http can't break airframe.http.client.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→28 airframe.http uses airframe.http.router✕
- Connections
- 4 pairs of types, where a type in airframe.http uses a type in airframe.http.router.
- The types involved
wvlet.airframe.http.Router→wvlet.airframe.http.router.Routewvlet.airframe.http.Router→wvlet.airframe.http.router.RouteMatchwvlet.airframe.http.Router→wvlet.airframe.http.router.RouterBasewvlet.airframe.http.RxRouter→wvlet.airframe.http.router.RxRoute
- Direction
- airframe.http uses airframe.http.router, so a change to airframe.http.router can break airframe.http, while a change to airframe.http can't break airframe.http.router.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→29 airframe.http uses airframe.http.finagle✕
- Connections
- 1 pair of types, where a type in airframe.http uses a type in airframe.http.finagle.
- The types involved
wvlet.airframe.http.finagle→wvlet.airframe.http.finagle.FinagleServerConfig
- Direction
- airframe.http uses airframe.http.finagle, so a change to airframe.http.finagle can break airframe.http, while a change to airframe.http can't break airframe.http.finagle.
- Position
- Below the diagonal: airframe.http uses a module listed above it, which is the healthy direction.
30→31 airframe.http uses airframe part of a loop✕
- Connections
- 1 pair of types, where a type in airframe.http uses a type in airframe.
- The types involved
wvlet.airframe.http.finagle→wvlet.airframe.Design
- Direction
- airframe.http uses airframe, so a change to airframe can break airframe.http, while a change to airframe.http can't break airframe.
- 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.
31→1 airframe uses airframe.surface.Primitive✕
- Connections
- 28 pairs of types, where a type in airframe uses a type in airframe.surface.Primitive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wvlet.airframe.AirframeException→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.AirframeSession→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.AirframeSession→wvlet.airframe.surface.Primitive.Longwvlet.airframe.AirframeSession→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.AirframeSession→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.AirframeSessionImpl→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.AirframeSpec→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.AirframeSpec→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.Design→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.Design→wvlet.airframe.surface.Primitive.Intwvlet.airframe.Design→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.DesignOptions→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.DesignOptions→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.LifeCycleHookDesign→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.Session→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.Session→wvlet.airframe.surface.Primitive.Longwvlet.airframe.Session→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.Session→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.SessionBuilder→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.SessionImpl→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.SourceCode→wvlet.airframe.surface.Primitive.Intwvlet.airframe.SourceCode→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.fluentd→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.fluentd→wvlet.airframe.surface.Primitive.Intwvlet.airframe.fluentd→wvlet.airframe.surface.Primitive.Long
- Direction
- airframe uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe, while a change to airframe can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe uses a module listed above it, which is the healthy direction.
31→4 airframe uses airframe.log✕
- Connections
- 7 pairs of types, where a type in airframe uses a type in airframe.log.
- The types involved
wvlet.airframe.AirframeSession→wvlet.airframe.log.LogSupportwvlet.airframe.AirframeSpec→wvlet.airframe.log.LogSupportwvlet.airframe.BinderImpl→wvlet.airframe.log.LogSupportwvlet.airframe.Design→wvlet.airframe.log.LogSupportwvlet.airframe.DesignImpl→wvlet.airframe.log.LogSupportwvlet.airframe.LifeCycleSupport→wvlet.airframe.log.LogSupportwvlet.airframe.SessionBuilder→wvlet.airframe.log.LogSupport
- Direction
- airframe uses airframe.log, so a change to airframe.log can break airframe, while a change to airframe can't break airframe.log.
- Position
- Below the diagonal: airframe uses a module listed above it, which is the healthy direction.
31→19 airframe uses airframe.surface✕
- Connections
- 5 pairs of types, where a type in airframe uses a type in airframe.surface.
- The types involved
wvlet.airframe.AirframeSession→wvlet.airframe.surface.Surfacewvlet.airframe.Design→wvlet.airframe.surface.Surfacewvlet.airframe.LifeCycleHookDesign→wvlet.airframe.surface.Surfacewvlet.airframe.Session→wvlet.airframe.surface.Surfacewvlet.airframe.surface→wvlet.airframe.surface.Surface
- Direction
- airframe uses airframe.surface, so a change to airframe.surface can break airframe, while a change to airframe can't break airframe.surface.
- Position
- Below the diagonal: airframe uses a module listed above it, which is the healthy direction.
31→21 airframe uses airframe.lifecycle✕
- Connections
- 4 pairs of types, where a type in airframe uses a type in airframe.lifecycle.
- The types involved
wvlet.airframe.AirframeSession→wvlet.airframe.lifecycle.LifeCycleManagerwvlet.airframe.LifeCycleHookDesign→wvlet.airframe.lifecycle.LifeCycleHookTypewvlet.airframe.Session→wvlet.airframe.lifecycle.LifeCycleManagerwvlet.airframe.SessionBuilder→wvlet.airframe.lifecycle.LifeCycleEventHandler
- Direction
- airframe uses airframe.lifecycle, so a change to airframe.lifecycle can break airframe, while a change to airframe can't break airframe.lifecycle.
- Position
- Below the diagonal: airframe uses a module listed above it, which is the healthy direction.
31→24 airframe uses airframe.tracing✕
- Connections
- 4 pairs of types, where a type in airframe uses a type in airframe.tracing.
- The types involved
wvlet.airframe.AirframeSession→wvlet.airframe.tracing.DIStatswvlet.airframe.AirframeSession→wvlet.airframe.tracing.Tracerwvlet.airframe.Design→wvlet.airframe.tracing.DIStatswvlet.airframe.Design→wvlet.airframe.tracing.Tracer
- Direction
- airframe uses airframe.tracing, so a change to airframe.tracing can break airframe, while a change to airframe can't break airframe.tracing.
- Position
- Below the diagonal: airframe uses a module listed above it, which is the healthy direction.
31→25 airframe uses airframe.http.Http✕
- Connections
- 1 pair of types, where a type in airframe uses a type in airframe.http.Http.
- The types involved
wvlet.airframe.AirframeMacros→wvlet.airframe.http.Http.Context
- Direction
- airframe uses airframe.http.Http, so a change to airframe.http.Http can break airframe, while a change to airframe can't break airframe.http.Http.
- Position
- Below the diagonal: airframe uses a module listed above it, which is the healthy direction.
31→30 airframe uses airframe.http✕
- Connections
- 1 pair of types, where a type in airframe uses a type in airframe.http.
- The types involved
wvlet.airframe.http→wvlet.airframe.http.CompatApi
- Direction
- airframe uses airframe.http, so a change to airframe.http can break airframe, while a change to airframe can't break airframe.http.
- Position
- Below the diagonal: airframe uses a module listed above it, which is the healthy direction.
32→1 airframe.http.codegen uses airframe.surface.Primitive✕
- Connections
- 8 pairs of types, where a type in airframe.http.codegen uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.codegen.ClassScanner→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.codegen.HttpClientGeneratorConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.codegen.HttpCodeGenerator→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.codegen.HttpCodeGenerator→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.codegen.HttpCodeGeneratorOption→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.codegen.OpenAPIGeneratorOption→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.codegen.RouteAnalyzer→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.codegen.RouteScanner→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.http.codegen uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.codegen, while a change to airframe.http.codegen can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.codegen uses a module listed above it, which is the healthy direction.
32→4 airframe.http.codegen uses airframe.log✕
- Connections
- 4 pairs of types, where a type in airframe.http.codegen uses a type in airframe.log.
- The types involved
wvlet.airframe.http.codegen.ClassScanner→wvlet.airframe.log.LogSupportwvlet.airframe.http.codegen.HttpClientIR→wvlet.airframe.log.LogSupportwvlet.airframe.http.codegen.HttpCodeGenerator→wvlet.airframe.log.LogSupportwvlet.airframe.http.codegen.RouteScanner→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.codegen uses airframe.log, so a change to airframe.log can break airframe.http.codegen, while a change to airframe.http.codegen can't break airframe.log.
- Position
- Below the diagonal: airframe.http.codegen uses a module listed above it, which is the healthy direction.
32→19 airframe.http.codegen uses airframe.surface✕
- Connections
- 2 pairs of types, where a type in airframe.http.codegen uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.codegen.HttpClientIR→wvlet.airframe.surface.MethodParameterwvlet.airframe.http.codegen.RouteAnalyzer→wvlet.airframe.surface.MethodParameter
- Direction
- airframe.http.codegen uses airframe.surface, so a change to airframe.surface can break airframe.http.codegen, while a change to airframe.http.codegen can't break airframe.surface.
- Position
- Below the diagonal: airframe.http.codegen uses a module listed above it, which is the healthy direction.
32→28 airframe.http.codegen uses airframe.http.router✕
- Connections
- 1 pair of types, where a type in airframe.http.codegen uses a type in airframe.http.router.
- The types involved
wvlet.airframe.http.codegen.RouteAnalyzer→wvlet.airframe.http.router.Route
- Direction
- airframe.http.codegen uses airframe.http.router, so a change to airframe.http.router can break airframe.http.codegen, while a change to airframe.http.codegen can't break airframe.http.router.
- Position
- Below the diagonal: airframe.http.codegen uses a module listed above it, which is the healthy direction.
32→30 airframe.http.codegen uses airframe.http✕
- Connections
- 6 pairs of types, where a type in airframe.http.codegen uses a type in airframe.http.
- The types involved
wvlet.airframe.http.codegen.HttpClientIR→wvlet.airframe.http.Routerwvlet.airframe.http.codegen.HttpClientIR→wvlet.airframe.http.RxRouterwvlet.airframe.http.codegen.HttpCodeGenerator→wvlet.airframe.http.Routerwvlet.airframe.http.codegen.HttpCodeGenerator→wvlet.airframe.http.RxRouterwvlet.airframe.http.codegen.RouteScanner→wvlet.airframe.http.Routerwvlet.airframe.http.codegen.RouteScanner→wvlet.airframe.http.RxRouter
- Direction
- airframe.http.codegen uses airframe.http, so a change to airframe.http can break airframe.http.codegen, while a change to airframe.http.codegen can't break airframe.http.
- Position
- Below the diagonal: airframe.http.codegen uses a module listed above it, which is the healthy direction.
33→1 airframe.http.internal uses airframe.surface.Primitive✕
- Connections
- 10 pairs of types, where a type in airframe.http.internal uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.internal.HttpLogs→wvlet.airframe.surface.Primitive.Longwvlet.airframe.http.internal.HttpLogs→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.internal.HttpMultiMapCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.internal.HttpResponseBodyCodec→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.internal.LocalRPCContext→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.internal.LogRotationHttpLogger→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.internal.LogRotationHttpLogger→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.internal.RPCCallContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.internal.TLSSupport→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.internal.TLSSupport→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.http.internal uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
33→4 airframe.http.internal uses airframe.log✕
- Connections
- 2 pairs of types, where a type in airframe.http.internal uses a type in airframe.log.
- The types involved
wvlet.airframe.http.internal.HttpLogs→wvlet.airframe.log.LogSupportwvlet.airframe.http.internal.RPCResponseFilter→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.internal uses airframe.log, so a change to airframe.log can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.log.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
33→8 airframe.http.internal uses airframe.msgpack.spi✕
- Connections
- 4 pairs of types, where a type in airframe.http.internal uses a type in airframe.msgpack.spi.
- The types involved
wvlet.airframe.http.internal.HttpMultiMapCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.http.internal.HttpMultiMapCodec→wvlet.airframe.msgpack.spi.Unpackerwvlet.airframe.http.internal.HttpResponseBodyCodec→wvlet.airframe.msgpack.spi.Packerwvlet.airframe.http.internal.HttpResponseBodyCodec→wvlet.airframe.msgpack.spi.Unpacker
- Direction
- airframe.http.internal uses airframe.msgpack.spi, so a change to airframe.msgpack.spi can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.msgpack.spi.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
33→17 airframe.http.internal uses airframe.rx✕
- Connections
- 1 pair of types, where a type in airframe.http.internal uses a type in airframe.rx.
- The types involved
wvlet.airframe.http.internal.RPCResponseFilter→wvlet.airframe.rx.Rx
- Direction
- airframe.http.internal uses airframe.rx, so a change to airframe.rx can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.rx.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
33→19 airframe.http.internal uses airframe.surface✕
- Connections
- 1 pair of types, where a type in airframe.http.internal uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.internal.RPCCallContext→wvlet.airframe.surface.MethodSurface
- Direction
- airframe.http.internal uses airframe.surface, so a change to airframe.surface can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.surface.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
33→20 airframe.http.internal uses airframe.http.openapi.OpenAPI✕
- Connections
- 2 pairs of types, where a type in airframe.http.internal uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.internal.HttpLogs→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.internal.RPCResponseFilter→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http.internal uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
33→22 airframe.http.internal uses airframe.http.HttpMessage✕
- Connections
- 2 pairs of types, where a type in airframe.http.internal uses a type in airframe.http.HttpMessage.
- The types involved
wvlet.airframe.http.internal.HttpLogs→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.internal.RPCResponseFilter→wvlet.airframe.http.HttpMessage.Request
- Direction
- airframe.http.internal uses airframe.http.HttpMessage, so a change to airframe.http.HttpMessage can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.http.HttpMessage.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
33→26 airframe.http.internal uses airframe.codec✕
- Connections
- 4 pairs of types, where a type in airframe.http.internal uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.internal.HttpMultiMapCodec→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.internal.HttpMultiMapCodec→wvlet.airframe.codec.MessageContextwvlet.airframe.http.internal.HttpResponseBodyCodec→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.internal.HttpResponseBodyCodec→wvlet.airframe.codec.MessageContext
- Direction
- airframe.http.internal uses airframe.codec, so a change to airframe.codec can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.codec.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
33→30 airframe.http.internal uses airframe.http✕
- Connections
- 11 pairs of types, where a type in airframe.http.internal uses a type in airframe.http.
- The types involved
wvlet.airframe.http.internal.HttpLogs→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.internal.HttpLogs→wvlet.airframe.http.RPCMethodwvlet.airframe.http.internal.HttpLogs→wvlet.airframe.http.RPCStatuswvlet.airframe.http.internal.HttpMultiMapCodec→wvlet.airframe.http.HttpMultiMapwvlet.airframe.http.internal.HttpResponseBodyCodec→wvlet.airframe.http.HttpResponsewvlet.airframe.http.internal.LocalRPCContext→wvlet.airframe.http.RPCContextwvlet.airframe.http.internal.LogRotationHttpLogger→wvlet.airframe.http.HttpLoggerwvlet.airframe.http.internal.LogRotationHttpLogger→wvlet.airframe.http.HttpLoggerConfigwvlet.airframe.http.internal.RPCCallContext→wvlet.airframe.http.RPCMethodwvlet.airframe.http.internal.RPCResponseFilter→wvlet.airframe.http.RxHttpEndpointwvlet.airframe.http.internal.RPCResponseFilter→wvlet.airframe.http.RxHttpFilter
- Direction
- airframe.http.internal uses airframe.http, so a change to airframe.http can break airframe.http.internal, while a change to airframe.http.internal can't break airframe.http.
- Position
- Below the diagonal: airframe.http.internal uses a module listed above it, which is the healthy direction.
34→1 airframe.http.grpc.internal uses airframe.surface.Primitive✕
- Connections
- 8 pairs of types, where a type in airframe.http.grpc.internal uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.grpc.internal.DefaultGrpcRequestLogger→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.grpc.internal.DefaultGrpcRequestLogger→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.grpc.internal.GrpcRequestHandler→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.grpc.internal.GrpcRequestHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.grpc.internal.GrpcRequestLogger→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.grpc.internal.RPCServerStreamingMethodHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.grpc.internal.RPCUnaryMethodHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.grpc.internal.WrappedServerCallListener→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.http.grpc.internal uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy direction.
34→3 airframe.http.grpc.internal uses airframe.http.RPCEncoding✕
- Connections
- 6 pairs of types, where a type in airframe.http.grpc.internal uses a type in airframe.http.RPCEncoding.
- The types involved
wvlet.airframe.http.grpc.internal.GrpcRequestHandler→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.http.grpc.internal.GrpcServiceBuilder→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.http.grpc.internal.RPCBidiStreamingMethodHandler→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.http.grpc.internal.RPCClientStreamingMethodHandler→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.http.grpc.internal.RPCServerStreamingMethodHandler→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.http.grpc.internal.RPCUnaryMethodHandler→wvlet.airframe.http.RPCEncoding.MsgPack
- Direction
- airframe.http.grpc.internal uses airframe.http.RPCEncoding, so a change to airframe.http.RPCEncoding can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.http.RPCEncoding.
- Position
- Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy direction.
34→4 airframe.http.grpc.internal uses airframe.log✕
- Connections
- 6 pairs of types, where a type in airframe.http.grpc.internal uses a type in airframe.log.
- The types involved
wvlet.airframe.http.grpc.internal.DefaultGrpcRequestLogger→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.internal.GrpcContextTrackInterceptor→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.internal.GrpcException→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.internal.GrpcRequestHandler→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.internal.RPCServerStreamingMethodHandler→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.internal.RPCUnaryMethodHandler→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.grpc.internal uses airframe.log, so a change to airframe.log can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.log.
- Position
- Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy direction.
34→19 airframe.http.grpc.internal uses airframe.surface✕
- Connections
- 2 pairs of types, where a type in airframe.http.grpc.internal uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.grpc.internal.GrpcRequestHandler→wvlet.airframe.surface.Surfacewvlet.airframe.http.grpc.internal.GrpcServiceBuilder→wvlet.airframe.surface.Surface
- Direction
- airframe.http.grpc.internal uses airframe.surface, so a change to airframe.surface can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.surface.
- Position
- Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy direction.
34→26 airframe.http.grpc.internal uses airframe.codec✕
- Connections
- 2 pairs of types, where a type in airframe.http.grpc.internal uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.grpc.internal.GrpcRequestHandler→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.grpc.internal.GrpcServiceBuilder→wvlet.airframe.codec.MessageCodecFactory
- Direction
- airframe.http.grpc.internal uses airframe.codec, so a change to airframe.codec can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.codec.
- Position
- Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy direction.
34→28 airframe.http.grpc.internal uses airframe.http.router✕
- Connections
- 1 pair of types, where a type in airframe.http.grpc.internal uses a type in airframe.http.router.
- The types involved
wvlet.airframe.http.grpc.internal.GrpcServiceBuilder→wvlet.airframe.http.router.Route
- Direction
- airframe.http.grpc.internal uses airframe.http.router, so a change to airframe.http.router can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.http.router.
- Position
- Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy direction.
34→31 airframe.http.grpc.internal uses airframe✕
- Connections
- 1 pair of types, where a type in airframe.http.grpc.internal uses a type in airframe.
- The types involved
wvlet.airframe.http.grpc.internal.GrpcServiceBuilder→wvlet.airframe.Session
- Direction
- airframe.http.grpc.internal uses airframe, so a change to airframe can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.
- Position
- Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy direction.
34→33 airframe.http.grpc.internal uses airframe.http.internal✕
- Connections
- 2 pairs of types, where a type in airframe.http.grpc.internal uses a type in airframe.http.internal.
- The types involved
wvlet.airframe.http.grpc.internal.DefaultGrpcRequestLogger→wvlet.airframe.http.internal.RPCCallContextwvlet.airframe.http.grpc.internal.GrpcRequestLogger→wvlet.airframe.http.internal.RPCCallContext
- Direction
- airframe.http.grpc.internal uses airframe.http.internal, so a change to airframe.http.internal can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.http.internal.
- Position
- Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy direction.
34→37 airframe.http.grpc.internal uses airframe.http.grpc part of a loop✕
- Connections
- 6 pairs of types, where a type in airframe.http.grpc.internal uses a type in airframe.http.grpc.
- The types involved
wvlet.airframe.http.grpc.internal.DefaultGrpcRequestLogger→wvlet.airframe.http.grpc.GrpcContextwvlet.airframe.http.grpc.internal.GrpcRequestHandler→wvlet.airframe.http.grpc.GrpcContextwvlet.airframe.http.grpc.internal.GrpcRequestLogger→wvlet.airframe.http.grpc.GrpcContextwvlet.airframe.http.grpc.internal.GrpcServiceBuilder→wvlet.airframe.http.grpc.GrpcMethodwvlet.airframe.http.grpc.internal.GrpcServiceBuilder→wvlet.airframe.http.grpc.GrpcServerConfigwvlet.airframe.http.grpc.internal.GrpcServiceBuilder→wvlet.airframe.http.grpc.GrpcService
- Direction
- airframe.http.grpc.internal uses airframe.http.grpc, so a change to airframe.http.grpc can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break airframe.http.grpc.
- 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.
35→1 airframe.http.netty uses airframe.surface.Primitive✕
- Connections
- 21 pairs of types, where a type in airframe.http.netty uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.netty.NettyBackend→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.netty.NettyBackend→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.netty.NettyBackend→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.netty.NettyRPCContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.netty.NettyRPCContext→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.netty.NettyRequestDecompression→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.netty.NettyRequestHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.netty.NettyServer→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.netty.NettyServer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.surface.Primitive.Longwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.netty.NettyWebSocketContext→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.netty.NettyWebSocketContext→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.netty.NettyWebSocketContext→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.netty.NettyWebSocketContext→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.netty.NettyWebSocketHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.netty.RxNettyBackend→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.netty.RxNettyBackend→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.netty.WebSocketRoute→wvlet.airframe.surface.Primitive.String
- Direction
- airframe.http.netty uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→4 airframe.http.netty uses airframe.log✕
- Connections
- 5 pairs of types, where a type in airframe.http.netty uses a type in airframe.log.
- The types involved
wvlet.airframe.http.netty.NettyBackend→wvlet.airframe.log.LogSupportwvlet.airframe.http.netty.NettyRequestHandler→wvlet.airframe.log.LogSupportwvlet.airframe.http.netty.NettyResponseHandler→wvlet.airframe.log.LogSupportwvlet.airframe.http.netty.NettyServer→wvlet.airframe.log.LogSupportwvlet.airframe.http.netty.NettyWebSocketHandler→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.netty uses airframe.log, so a change to airframe.log can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.log.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→17 airframe.http.netty uses airframe.rx✕
- Connections
- 1 pair of types, where a type in airframe.http.netty uses a type in airframe.rx.
- The types involved
wvlet.airframe.http.netty.NettyBackend→wvlet.airframe.rx.Rx
- Direction
- airframe.http.netty uses airframe.rx, so a change to airframe.rx can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.rx.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→19 airframe.http.netty uses airframe.surface✕
- Connections
- 2 pairs of types, where a type in airframe.http.netty uses a type in airframe.surface.
- The types involved
wvlet.airframe.http.netty.NettyResponseHandler→wvlet.airframe.surface.Surfacewvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.surface.Surface
- Direction
- airframe.http.netty uses airframe.surface, so a change to airframe.surface can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.surface.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→20 airframe.http.netty uses airframe.http.openapi.OpenAPI✕
- Connections
- 2 pairs of types, where a type in airframe.http.netty uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.netty.NettyResponseHandler→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http.netty uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→22 airframe.http.netty uses airframe.http.HttpMessage✕
- Connections
- 6 pairs of types, where a type in airframe.http.netty uses a type in airframe.http.HttpMessage.
- The types involved
wvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.netty.NettyRPCContext→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.netty.NettyRequestHandler→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.netty.NettyResponseHandler→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.netty.NettyWebSocketContext→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.netty.WebSocketRoute→wvlet.airframe.http.HttpMessage.Request
- Direction
- airframe.http.netty uses airframe.http.HttpMessage, so a change to airframe.http.HttpMessage can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.http.HttpMessage.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→25 airframe.http.netty uses airframe.http.Http✕
- Connections
- 1 pair of types, where a type in airframe.http.netty uses a type in airframe.http.Http.
- The types involved
wvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.Http.Filter
- Direction
- airframe.http.netty uses airframe.http.Http, so a change to airframe.http.Http can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.http.Http.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→26 airframe.http.netty uses airframe.codec✕
- Connections
- 2 pairs of types, where a type in airframe.http.netty uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.codec.MessageCodecFactory
- Direction
- airframe.http.netty uses airframe.codec, so a change to airframe.codec can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.codec.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→28 airframe.http.netty uses airframe.http.router✕
- Connections
- 3 pairs of types, where a type in airframe.http.netty uses a type in airframe.http.router.
- The types involved
wvlet.airframe.http.netty.NettyResponseHandler→wvlet.airframe.http.router.ResponseHandlerwvlet.airframe.http.netty.NettyResponseHandler→wvlet.airframe.http.router.Routewvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.http.router.ControllerProvider
- Direction
- airframe.http.netty uses airframe.http.router, so a change to airframe.http.router can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.http.router.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→30 airframe.http.netty uses airframe.http✕
- Connections
- 19 pairs of types, where a type in airframe.http.netty uses a type in airframe.http.
- The types involved
wvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.HttpBackendwvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.HttpFilterwvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.HttpRequestAdapterwvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.HttpStatuswvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.RxHttpFilterwvlet.airframe.http.netty.NettyRPCContext→wvlet.airframe.http.RPCContextwvlet.airframe.http.netty.NettyRequestHandler→wvlet.airframe.http.HttpRequestwvlet.airframe.http.netty.NettyServer→wvlet.airframe.http.HttpLoggerwvlet.airframe.http.netty.NettyServer→wvlet.airframe.http.HttpServerwvlet.airframe.http.netty.NettyServer→wvlet.airframe.http.RxHttpFilterwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.http.HttpLoggerwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.http.HttpLoggerConfigwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.http.HttpMessagewvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.http.Routerwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.http.RxHttpFilterwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.http.RxRouterwvlet.airframe.http.netty.NettyWebSocketContext→wvlet.airframe.http.WebSocketContextwvlet.airframe.http.netty.RxNettyBackend→wvlet.airframe.http.RxHttpBackendwvlet.airframe.http.netty.WebSocketRoute→wvlet.airframe.http.RxHttpFilter
- Direction
- airframe.http.netty uses airframe.http, so a change to airframe.http can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.http.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→31 airframe.http.netty uses airframe✕
- Connections
- 2 pairs of types, where a type in airframe.http.netty uses a type in airframe.
- The types involved
wvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.Designwvlet.airframe.http.netty.NettyServerConfig→wvlet.airframe.Session
- Direction
- airframe.http.netty uses airframe, so a change to airframe can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
35→33 airframe.http.netty uses airframe.http.internal✕
- Connections
- 1 pair of types, where a type in airframe.http.netty uses a type in airframe.http.internal.
- The types involved
wvlet.airframe.http.netty.NettyBackend→wvlet.airframe.http.internal.TLSSupport
- Direction
- airframe.http.netty uses airframe.http.internal, so a change to airframe.http.internal can break airframe.http.netty, while a change to airframe.http.netty can't break airframe.http.internal.
- Position
- Below the diagonal: airframe.http.netty uses a module listed above it, which is the healthy direction.
36→1 airspec.spi uses airframe.surface.Primitive✕
- Connections
- 17 pairs of types, where a type in airspec.spi uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airspec.spi.AirSpecContext→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.spi.AirSpecContext→wvlet.airframe.surface.Primitive.Intwvlet.airspec.spi.AirSpecContext→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.AirSpecContext→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.spi.AirSpecException→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.AirSpecFailureBase→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.AssertionFailure→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.Asserts→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.spi.Cancelled→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.Ignored→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.InterceptException→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.JsObjectMatcher→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.spi.MissingTestDependency→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.Pending→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.PropertyCheck→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.spi.RichAsserts→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.spi.Skipped→wvlet.airframe.surface.Primitive.String
- Direction
- airspec.spi uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airspec.spi, while a change to airspec.spi can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airspec.spi uses a module listed above it, which is the healthy direction.
36→4 airspec.spi uses airframe.log✕
- Connections
- 1 pair of types, where a type in airspec.spi uses a type in airframe.log.
- The types involved
wvlet.airspec.spi.RichAsserts→wvlet.airframe.log.LogSupport
- Direction
- airspec.spi uses airframe.log, so a change to airframe.log can break airspec.spi, while a change to airspec.spi can't break airframe.log.
- Position
- Below the diagonal: airspec.spi uses a module listed above it, which is the healthy direction.
36→31 airspec.spi uses airframe✕
- Connections
- 8 pairs of types, where a type in airspec.spi uses a type in airframe.
- The types involved
wvlet.airspec.spi.AirSpecContext→wvlet.airframe.Sessionwvlet.airspec.spi.AirSpecFailureBase→wvlet.airframe.SourceCodewvlet.airspec.spi.AssertionFailure→wvlet.airframe.SourceCodewvlet.airspec.spi.Cancelled→wvlet.airframe.SourceCodewvlet.airspec.spi.Ignored→wvlet.airframe.SourceCodewvlet.airspec.spi.InterceptException→wvlet.airframe.SourceCodewvlet.airspec.spi.Pending→wvlet.airframe.SourceCodewvlet.airspec.spi.Skipped→wvlet.airframe.SourceCode
- Direction
- airspec.spi uses airframe, so a change to airframe can break airspec.spi, while a change to airspec.spi can't break airframe.
- Position
- Below the diagonal: airspec.spi uses a module listed above it, which is the healthy direction.
36→39 airspec.spi uses airspec part of a loop✕
- Connections
- 2 pairs of types, where a type in airspec.spi uses a type in airspec.
- The types involved
wvlet.airspec.spi.AirSpecContext→wvlet.airspec.AirSpecDefwvlet.airspec.spi.AirSpecContext→wvlet.airspec.AirSpecSpi
- Direction
- airspec.spi uses airspec, so a change to airspec can break airspec.spi, while a change to airspec.spi can't break airspec.
- 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.
37→1 airframe.http.grpc uses airframe.surface.Primitive✕
- Connections
- 10 pairs of types, where a type in airframe.http.grpc uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.grpc.GrpcClient→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.grpc.GrpcClient→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.grpc.GrpcMethod→wvlet.airframe.surface.Primitive.Bytewvlet.airframe.http.grpc.GrpcServer→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.grpc.GrpcServer→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.grpc.GrpcServer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.grpc.GrpcServerConfig→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.grpc.GrpcServerConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.grpc.GrpcServerFactory→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.grpc.GrpcService→wvlet.airframe.surface.Primitive.Unit
- Direction
- airframe.http.grpc uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.grpc, while a change to airframe.http.grpc can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.grpc uses a module listed above it, which is the healthy direction.
37→3 airframe.http.grpc uses airframe.http.RPCEncoding✕
- Connections
- 2 pairs of types, where a type in airframe.http.grpc uses a type in airframe.http.RPCEncoding.
- The types involved
wvlet.airframe.http.grpc.GrpcClientCalls→wvlet.airframe.http.RPCEncoding.MsgPackwvlet.airframe.http.grpc.GrpcRequestMarshaller→wvlet.airframe.http.RPCEncoding.MsgPack
- Direction
- airframe.http.grpc uses airframe.http.RPCEncoding, so a change to airframe.http.RPCEncoding can break airframe.http.grpc, while a change to airframe.http.grpc can't break airframe.http.RPCEncoding.
- Position
- Below the diagonal: airframe.http.grpc uses a module listed above it, which is the healthy direction.
37→4 airframe.http.grpc uses airframe.log✕
- Connections
- 7 pairs of types, where a type in airframe.http.grpc uses a type in airframe.log.
- The types involved
wvlet.airframe.http.grpc.GrpcClientCalls→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.GrpcRequestMarshaller→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.GrpcResponseMarshaller→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.GrpcServer→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.GrpcServerConfig→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.GrpcServerFactory→wvlet.airframe.log.LogSupportwvlet.airframe.http.grpc.GrpcService→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.grpc uses airframe.log, so a change to airframe.log can break airframe.http.grpc, while a change to airframe.http.grpc can't break airframe.log.
- Position
- Below the diagonal: airframe.http.grpc uses a module listed above it, which is the healthy direction.
37→17 airframe.http.grpc uses airframe.rx✕
- Connections
- 3 pairs of types, where a type in airframe.http.grpc uses a type in airframe.rx.
- The types involved
wvlet.airframe.http.grpc.GrpcClient→wvlet.airframe.rx.Rxwvlet.airframe.http.grpc.GrpcClientCalls→wvlet.airframe.rx.Cancelablewvlet.airframe.http.grpc.GrpcClientCalls→wvlet.airframe.rx.Rx
- Direction
- airframe.http.grpc uses airframe.rx, so a change to airframe.rx can break airframe.http.grpc, while a change to airframe.http.grpc can't break airframe.rx.
- Position
- Below the diagonal: airframe.http.grpc uses a module listed above it, which is the healthy direction.
37→26 airframe.http.grpc uses airframe.codec✕
- Connections
- 3 pairs of types, where a type in airframe.http.grpc uses a type in airframe.codec.
- The types involved
wvlet.airframe.http.grpc.GrpcClientCalls→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.grpc.GrpcMethod→wvlet.airframe.codec.MessageCodecwvlet.airframe.http.grpc.GrpcServerConfig→wvlet.airframe.codec.MessageCodecFactory
- Direction
- airframe.http.grpc uses airframe.codec, so a change to airframe.codec can break airframe.http.grpc, while a change to airframe.http.grpc can't break airframe.codec.
- Position
- Below the diagonal: airframe.http.grpc uses a module listed above it, which is the healthy direction.
37→30 airframe.http.grpc uses airframe.http✕
- Connections
- 6 pairs of types, where a type in airframe.http.grpc uses a type in airframe.http.
- The types involved
wvlet.airframe.http.grpc.GrpcClientCalls→wvlet.airframe.http.RPCEncodingwvlet.airframe.http.grpc.GrpcClientConfig→wvlet.airframe.http.RPCEncodingwvlet.airframe.http.grpc.GrpcClientInterceptor→wvlet.airframe.http.RPCEncodingwvlet.airframe.http.grpc.GrpcResponse→wvlet.airframe.http.RPCEncodingwvlet.airframe.http.grpc.GrpcServerConfig→wvlet.airframe.http.Routerwvlet.airframe.http.grpc.GrpcServerConfig→wvlet.airframe.http.RxRouter
- Direction
- airframe.http.grpc uses airframe.http, so a change to airframe.http can break airframe.http.grpc, while a change to airframe.http.grpc can't break airframe.http.
- Position
- Below the diagonal: airframe.http.grpc uses a module listed above it, which is the healthy direction.
37→31 airframe.http.grpc uses airframe✕
- Connections
- 2 pairs of types, where a type in airframe.http.grpc uses a type in airframe.
- The types involved
wvlet.airframe.http.grpc.GrpcServerConfig→wvlet.airframe.Designwvlet.airframe.http.grpc.GrpcServerConfig→wvlet.airframe.Session
- Direction
- airframe.http.grpc uses airframe, so a change to airframe can break airframe.http.grpc, while a change to airframe.http.grpc can't break airframe.
- Position
- Below the diagonal: airframe.http.grpc uses a module listed above it, which is the healthy direction.
37→34 airframe.http.grpc uses airframe.http.grpc.internal✕
- Connections
- 1 pair of types, where a type in airframe.http.grpc uses a type in airframe.http.grpc.internal.
- The types involved
wvlet.airframe.http.grpc.GrpcService→wvlet.airframe.http.grpc.internal.GrpcRequestLogger
- Direction
- airframe.http.grpc uses airframe.http.grpc.internal, so a change to airframe.http.grpc.internal can break airframe.http.grpc, while a change to airframe.http.grpc can't break airframe.http.grpc.internal.
- Position
- Below the diagonal: airframe.http.grpc uses a module listed above it, which is the healthy direction.
38→1 airframe.http.recorder uses airframe.surface.Primitive✕
- Connections
- 13 pairs of types, where a type in airframe.http.recorder uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airframe.http.recorder.HttpRecord→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.recorder.HttpRecord→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.recorder.HttpRecord→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.recorder.HttpRecordStore→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.recorder.HttpRecordStore→wvlet.airframe.surface.Primitive.Longwvlet.airframe.http.recorder.HttpRecordStore→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.recorder.HttpRecordStore→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.recorder.HttpRecorder→wvlet.airframe.surface.Primitive.Booleanwvlet.airframe.http.recorder.HttpRecorderConfig→wvlet.airframe.surface.Primitive.Intwvlet.airframe.http.recorder.HttpRecorderConfig→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.recorder.HttpRecorderServer→wvlet.airframe.surface.Primitive.Stringwvlet.airframe.http.recorder.HttpRecorderServer→wvlet.airframe.surface.Primitive.Unitwvlet.airframe.http.recorder.HttpRequestMatcher→wvlet.airframe.surface.Primitive.Int
- Direction
- airframe.http.recorder uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airframe.http.recorder, while a change to airframe.http.recorder can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airframe.http.recorder uses a module listed above it, which is the healthy direction.
38→4 airframe.http.recorder uses airframe.log✕
- Connections
- 2 pairs of types, where a type in airframe.http.recorder uses a type in airframe.log.
- The types involved
wvlet.airframe.http.recorder.HttpRecordStore→wvlet.airframe.log.LogSupportwvlet.airframe.http.recorder.HttpRecorder→wvlet.airframe.log.LogSupport
- Direction
- airframe.http.recorder uses airframe.log, so a change to airframe.log can break airframe.http.recorder, while a change to airframe.http.recorder can't break airframe.log.
- Position
- Below the diagonal: airframe.http.recorder uses a module listed above it, which is the healthy direction.
38→20 airframe.http.recorder uses airframe.http.openapi.OpenAPI✕
- Connections
- 3 pairs of types, where a type in airframe.http.recorder uses a type in airframe.http.openapi.OpenAPI.
- The types involved
wvlet.airframe.http.recorder.HttpRecord→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.recorder.HttpRecordStore→wvlet.airframe.http.openapi.OpenAPI.Responsewvlet.airframe.http.recorder.HttpRecorderServer→wvlet.airframe.http.openapi.OpenAPI.Response
- Direction
- airframe.http.recorder uses airframe.http.openapi.OpenAPI, so a change to airframe.http.openapi.OpenAPI can break airframe.http.recorder, while a change to airframe.http.recorder can't break airframe.http.openapi.OpenAPI.
- Position
- Below the diagonal: airframe.http.recorder uses a module listed above it, which is the healthy direction.
38→22 airframe.http.recorder uses airframe.http.HttpMessage✕
- Connections
- 3 pairs of types, where a type in airframe.http.recorder uses a type in airframe.http.HttpMessage.
- The types involved
wvlet.airframe.http.recorder.HttpRecordStore→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.recorder.HttpRecorderServer→wvlet.airframe.http.HttpMessage.Requestwvlet.airframe.http.recorder.HttpRequestMatcher→wvlet.airframe.http.HttpMessage.Request
- Direction
- airframe.http.recorder uses airframe.http.HttpMessage, so a change to airframe.http.HttpMessage can break airframe.http.recorder, while a change to airframe.http.recorder can't break airframe.http.HttpMessage.
- Position
- Below the diagonal: airframe.http.recorder uses a module listed above it, which is the healthy direction.
38→30 airframe.http.recorder uses airframe.http✕
- Connections
- 2 pairs of types, where a type in airframe.http.recorder uses a type in airframe.http.
- The types involved
wvlet.airframe.http.recorder.HttpRecorder→wvlet.airframe.http.RxHttpEndpointwvlet.airframe.http.recorder.HttpRecorderConfig→wvlet.airframe.http.RxHttpEndpoint
- Direction
- airframe.http.recorder uses airframe.http, so a change to airframe.http can break airframe.http.recorder, while a change to airframe.http.recorder can't break airframe.http.
- Position
- Below the diagonal: airframe.http.recorder uses a module listed above it, which is the healthy direction.
38→31 airframe.http.recorder uses airframe✕
- Connections
- 1 pair of types, where a type in airframe.http.recorder uses a type in airframe.
- The types involved
wvlet.airframe.http.recorder.HttpRecorderServer→wvlet.airframe.Session
- Direction
- airframe.http.recorder uses airframe, so a change to airframe can break airframe.http.recorder, while a change to airframe.http.recorder can't break airframe.
- Position
- Below the diagonal: airframe.http.recorder uses a module listed above it, which is the healthy direction.
38→35 airframe.http.recorder uses airframe.http.netty✕
- Connections
- 2 pairs of types, where a type in airframe.http.recorder uses a type in airframe.http.netty.
- The types involved
wvlet.airframe.http.recorder.HttpRecorderServer→wvlet.airframe.http.netty.NettyServerwvlet.airframe.http.recorder.HttpRecorderServer→wvlet.airframe.http.netty.NettyServerConfig
- Direction
- airframe.http.recorder uses airframe.http.netty, so a change to airframe.http.netty can break airframe.http.recorder, while a change to airframe.http.recorder can't break airframe.http.netty.
- Position
- Below the diagonal: airframe.http.recorder uses a module listed above it, which is the healthy direction.
39→1 airspec uses airframe.surface.Primitive✕
- Connections
- 22 pairs of types, where a type in airspec uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airspec.AirSpecDef→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecDefF0→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecDefF1→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecDefF2→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecDefF3→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecDefF4→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecDefF5→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecLauncher→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecLauncher→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.AirSpecSpi→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.AirSpecSpi→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.AirSpecSpi→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.AirSpecSpiCompat→wvlet.airframe.surface.Primitive.Intwvlet.airspec.AirSpecSpiCompat→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.AirSpecTestBuilder→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.Compat→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.Compat→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.CompatApi→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.CompatApi→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.CompatApi→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.Framework→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.MethodAirSpecDef→wvlet.airframe.surface.Primitive.String
- Direction
- airspec uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airspec, while a change to airspec can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airspec uses a module listed above it, which is the healthy direction.
39→4 airspec uses airframe.log✕
- Connections
- 2 pairs of types, where a type in airspec uses a type in airframe.log.
- The types involved
wvlet.airspec.AirSpecLauncher→wvlet.airframe.log.LogSupportwvlet.airspec.Compat→wvlet.airframe.log.LogSupport
- Direction
- airspec uses airframe.log, so a change to airframe.log can break airspec, while a change to airspec can't break airframe.log.
- Position
- Below the diagonal: airspec uses a module listed above it, which is the healthy direction.
39→19 airspec uses airframe.surface✕
- Connections
- 7 pairs of types, where a type in airspec uses a type in airframe.surface.
- The types involved
wvlet.airspec.AirSpecDef→wvlet.airframe.surface.Surfacewvlet.airspec.AirSpecDefF1→wvlet.airframe.surface.Surfacewvlet.airspec.AirSpecDefF2→wvlet.airframe.surface.Surfacewvlet.airspec.AirSpecDefF3→wvlet.airframe.surface.Surfacewvlet.airspec.AirSpecDefF4→wvlet.airframe.surface.Surfacewvlet.airspec.AirSpecDefF5→wvlet.airframe.surface.Surfacewvlet.airspec.MethodAirSpecDef→wvlet.airframe.surface.MethodSurface
- Direction
- airspec uses airframe.surface, so a change to airframe.surface can break airspec, while a change to airspec can't break airframe.surface.
- Position
- Below the diagonal: airspec uses a module listed above it, which is the healthy direction.
39→25 airspec uses airframe.http.Http✕
- Connections
- 1 pair of types, where a type in airspec uses a type in airframe.http.Http.
- The types involved
wvlet.airspec.AirSpecMacros→wvlet.airframe.http.Http.Context
- Direction
- airspec uses airframe.http.Http, so a change to airframe.http.Http can break airspec, while a change to airspec can't break airframe.http.Http.
- Position
- Below the diagonal: airspec uses a module listed above it, which is the healthy direction.
39→30 airspec uses airframe.http✕
- Connections
- 1 pair of types, where a type in airspec uses a type in airframe.http.
- The types involved
wvlet.airspec.Compat→wvlet.airframe.http.CompatApi
- Direction
- airspec uses airframe.http, so a change to airframe.http can break airspec, while a change to airspec can't break airframe.http.
- Position
- Below the diagonal: airspec uses a module listed above it, which is the healthy direction.
39→31 airspec uses airframe✕
- Connections
- 19 pairs of types, where a type in airspec uses a type in airframe.
- The types involved
wvlet.airspec.AirSpecDef→wvlet.airframe.Designwvlet.airspec.AirSpecDef→wvlet.airframe.Sessionwvlet.airspec.AirSpecDefF0→wvlet.airframe.Designwvlet.airspec.AirSpecDefF0→wvlet.airframe.LazyF0wvlet.airspec.AirSpecDefF0→wvlet.airframe.Sessionwvlet.airspec.AirSpecDefF1→wvlet.airframe.Designwvlet.airspec.AirSpecDefF1→wvlet.airframe.Sessionwvlet.airspec.AirSpecDefF2→wvlet.airframe.Designwvlet.airspec.AirSpecDefF2→wvlet.airframe.Sessionwvlet.airspec.AirSpecDefF3→wvlet.airframe.Designwvlet.airspec.AirSpecDefF3→wvlet.airframe.Sessionwvlet.airspec.AirSpecDefF4→wvlet.airframe.Designwvlet.airspec.AirSpecDefF4→wvlet.airframe.Sessionwvlet.airspec.AirSpecDefF5→wvlet.airframe.Designwvlet.airspec.AirSpecDefF5→wvlet.airframe.Sessionwvlet.airspec.AirSpecSpi→wvlet.airframe.Designwvlet.airspec.AirSpecTestBuilder→wvlet.airframe.Designwvlet.airspec.MethodAirSpecDef→wvlet.airframe.Designwvlet.airspec.MethodAirSpecDef→wvlet.airframe.Session
- Direction
- airspec uses airframe, so a change to airframe can break airspec, while a change to airspec can't break airframe.
- Position
- Below the diagonal: airspec uses a module listed above it, which is the healthy direction.
39→36 airspec uses airspec.spi✕
- Connections
- 11 pairs of types, where a type in airspec uses a type in airspec.spi.
- The types involved
wvlet.airspec.AirSpec→wvlet.airspec.spi.Assertswvlet.airspec.AirSpec→wvlet.airspec.spi.RichAssertswvlet.airspec.AirSpecDef→wvlet.airspec.spi.AirSpecContextwvlet.airspec.AirSpecDefF0→wvlet.airspec.spi.AirSpecContextwvlet.airspec.AirSpecDefF1→wvlet.airspec.spi.AirSpecContextwvlet.airspec.AirSpecDefF2→wvlet.airspec.spi.AirSpecContextwvlet.airspec.AirSpecDefF3→wvlet.airspec.spi.AirSpecContextwvlet.airspec.AirSpecDefF4→wvlet.airspec.spi.AirSpecContextwvlet.airspec.AirSpecDefF5→wvlet.airspec.spi.AirSpecContextwvlet.airspec.AirSpecSpi→wvlet.airspec.spi.AirSpecContextwvlet.airspec.MethodAirSpecDef→wvlet.airspec.spi.AirSpecContext
- Direction
- airspec uses airspec.spi, so a change to airspec.spi can break airspec, while a change to airspec can't break airspec.spi.
- Position
- Below the diagonal: airspec uses a module listed above it, which is the healthy direction.
40→1 airspec.runner uses airframe.surface.Primitive✕
- Connections
- 19 pairs of types, where a type in airspec.runner uses a type in airframe.surface.Primitive.
- The types involved
wvlet.airspec.runner.AirSpecContextImpl→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.runner.AirSpecContextImpl→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.runner.AirSpecContextImpl→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.runner.AirSpecEvent→wvlet.airframe.surface.Primitive.Longwvlet.airspec.runner.AirSpecEvent→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.runner.AirSpecEventHandler→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.runner.AirSpecLogger→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.runner.AirSpecLogger→wvlet.airframe.surface.Primitive.Intwvlet.airspec.runner.AirSpecLogger→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.runner.AirSpecLogger→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.runner.AirSpecMatcher→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.runner.AirSpecMatcher→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.runner.AirSpecSbtRunner→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.runner.AirSpecTask→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.runner.AirSpecTask→wvlet.airframe.surface.Primitive.Unitwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airframe.surface.Primitive.Booleanwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airframe.surface.Primitive.Longwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airframe.surface.Primitive.Stringwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airframe.surface.Primitive.Unit
- Direction
- airspec.runner uses airframe.surface.Primitive, so a change to airframe.surface.Primitive can break airspec.runner, while a change to airspec.runner can't break airframe.surface.Primitive.
- Position
- Below the diagonal: airspec.runner uses a module listed above it, which is the healthy direction.
40→4 airspec.runner uses airframe.log✕
- Connections
- 7 pairs of types, where a type in airspec.runner uses a type in airframe.log.
- The types involved
wvlet.airspec.runner.AirSpecContextImpl→wvlet.airframe.log.LogSupportwvlet.airspec.runner.AirSpecEventHandler→wvlet.airframe.log.LogSupportwvlet.airspec.runner.AirSpecLogger→wvlet.airframe.log.AnsiColorPalettewvlet.airspec.runner.AirSpecMatcher→wvlet.airframe.log.LogSupportwvlet.airspec.runner.AirSpecTask→wvlet.airframe.log.LogSupportwvlet.airspec.runner.AirSpecTask→wvlet.airframe.log.Loggerwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airframe.log.LogSupport
- Direction
- airspec.runner uses airframe.log, so a change to airframe.log can break airspec.runner, while a change to airspec.runner can't break airframe.log.
- Position
- Below the diagonal: airspec.runner uses a module listed above it, which is the healthy direction.
40→31 airspec.runner uses airframe✕
- Connections
- 3 pairs of types, where a type in airspec.runner uses a type in airframe.
- The types involved
wvlet.airspec.runner.AirSpecContextImpl→wvlet.airframe.Sessionwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airframe.Designwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airframe.Session
- Direction
- airspec.runner uses airframe, so a change to airframe can break airspec.runner, while a change to airspec.runner can't break airframe.
- Position
- Below the diagonal: airspec.runner uses a module listed above it, which is the healthy direction.
40→36 airspec.runner uses airspec.spi✕
- Connections
- 2 pairs of types, where a type in airspec.runner uses a type in airspec.spi.
- The types involved
wvlet.airspec.runner.AirSpecContextImpl→wvlet.airspec.spi.AirSpecContextwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airspec.spi.AirSpecContext
- Direction
- airspec.runner uses airspec.spi, so a change to airspec.spi can break airspec.runner, while a change to airspec.runner can't break airspec.spi.
- Position
- Below the diagonal: airspec.runner uses a module listed above it, which is the healthy direction.
40→39 airspec.runner uses airspec✕
- Connections
- 4 pairs of types, where a type in airspec.runner uses a type in airspec.
- The types involved
wvlet.airspec.runner.AirSpecContextImpl→wvlet.airspec.AirSpecDefwvlet.airspec.runner.AirSpecContextImpl→wvlet.airspec.AirSpecSpiwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airspec.AirSpecDefwvlet.airspec.runner.AirSpecTaskRunner→wvlet.airspec.AirSpecSpi
- Direction
- airspec.runner uses airspec, so a change to airspec can break airspec.runner, while a change to airspec.runner can't break airspec.
- Position
- Below the diagonal: airspec.runner 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 | 89 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
First, establish architectural clarity by documenting significant design decisions in the docs/adr folder and reconcile README inaccuracies to ensure documentation reflects reality. Next, resolve the three banned license findings to maintain compliance, and integrate a SAST step into the CI pipeline to prevent security regressions from reaching production. Finally, enforce strict null safety by enabling explicit null checks or null-wart tools in the build, and refactor code to eliminate null assertions at API boundaries.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Banned license finding(s) in License Compliance. | +2.8 pts | Low | License Compliance |
| 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.8 pts | Medium | Architecture documentation |
| Reconcile the README with reality: airframe-jmx/README.md links to `treasuredata.com`, but `airframe-jmx/treasuredata.com` does not exist; airframe-log/README.md links to `../img/airframe-log/jmx.png`, but `img/airframe-log/jmx.png` does not exist. | +1.9 pts | Medium | Documentation accuracy |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +1.6 pts | Medium | Security & performance tooling |
| 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.5 pts | Medium | Nullable reference types |
| 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 Watchdog 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.3 pts | Medium | Deployment & Rollback |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.1 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala | 5.7 | Mixed | Cyclomatic Complexity: SQLGenerator.printRelation (cyclomatic 37) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleResponseHandler.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 65 of 65 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 65 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, 371 of 394 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (.codecov.yml, target 80%) 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 325 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.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala`, `airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala`, … (+1 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.
- D34 Knowledge Freshness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 98 commits in the last 90 days, yet 216 of 236 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Airframe DI, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.zaxxer.hikari' is imported (airframe-jdbc/src/main/scala/wvlet/airframe/jdbc/DbConfig.scala:16), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.zaxxer.hikari' is imported (airframe-jdbc/src/main/scala/wvlet/airframe/jdbc/DbConfig.scala:16), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.zaxxer.hikari' is imported (airframe-jdbc/src/main/scala/wvlet/airframe/jdbc/DbConfig.scala:16), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RxRunner.run at 133. A further 4 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 OffsetUnpacker.skipValue at 26 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: airframe-codec/.jvm/src/main/scala/wvlet/airframe/codec/JDBCCodec.scala (JDBCCodec.toJDBCColumnCodec at 22), airframe-metrics/.jvm/src/main/scala/wvlet/airframe/metrics/TimeVector.scala (TimeVector.apply at 20). 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 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with RxRunner.run (cyclomatic 133), RxRunner.run (cyclomatic 133), PlanBuilder.buildCondition (cyclomatic 66). — 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 3 together lifts Cyclomatic Complexity from 5.7 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
38 method(s) exceeded the cognitive complexity threshold of 15; the worst was RxRunner.run at 147.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with RxRunner.run (cognitive 147), RxRunner.run (cognitive 147). — 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 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
25 god class(es) detected.
What to do
- Resolve the 13 TooManyMethods finding(s) in God Classes — start with Monaco.scala (3), Rx.scala (2), AirframeMacros.scala. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 10 FileTooLong finding(s) in God Classes — start with Monaco.scala, Expression.scala, AirframeMacros.scala. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with RxRunner.scala, DOMRenderer.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
60 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 9 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ReflectSurfaceFactory.scala (2), JSConsoleLogHandler.scala, AirframeMacros.scala. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 7 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ByteArrayBuffer.scala (2), package.scala, Expression.scala. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 4 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with MessageCodec.scala, NestedMessagePackBuilder.scala, compat.scala. — One of this dimension's main actionable groups (4 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
45 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; 4 module(s) off the main sequence, with abstractness counted on 32 of the 45 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
5 of 102 classes have LCOM4 above 3.
What to do
- Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with Logger.scala (2), RPCRequestBenchmark.scala, FluentdLogger.scala. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1640 test methods: 1640 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 1640 test case(s) across 300 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.
D12 · Dependency Hygiene
3 outdated direct sbt declarations. 48 of 55 direct declarations were graded against Maven Central (6 not published there, which is what a private Nexus or Artifactory artifact looks like, 1 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
3 of 47 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 3 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 4 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 8 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 3 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (3 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
15 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is airframe-http-netty/src/main/scala/wvlet/airframe/http/netty/NettyServer.scala. Counted over 219 of the 429 production source files in this repository: 193 are under the ~2,400-byte size floor this dimension measures over, and the remaining 17 have no attributable history left to measure.
D17 · Explicit Debt
79 deducted task-comment markers across 58805 LoC (0.1/KLoC) → score 9.7. 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 76 TodoComment finding(s) in Explicit Debt — start with SQLInterpreter.scala (10), Expression.scala (5), PrimitiveCodec.scala (5). — One of this dimension's main actionable groups (76 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with CompileTimeSurfaceFactory.scala (2), MethodSurfaceTest.scala. — One of this dimension's main actionable groups (3 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. 54 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 4 build units (npm, 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)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
89 finding(s): 0 critical, 88 high, 1 medium, 0 low. 80 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 10 file(s) — `.codecov.yml`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala`, … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 80 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 (80 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D35 · Change Coupling
Strongest change-coupling: SQLGenerator.scala↔SQLInterpreter.scala 65%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with SQLGenerator.scala. — One of this dimension's main actionable groups (1 warning-level).
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. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
- `Packer` declares 21 abstract members: `packNil`, `packBoolean`, `packByte`, `packShort`, `packInt`, `packLong`, `packBigInteger`, `packFloat`, `packDouble`, `packString`, `packTimestamp`, `packArrayHeader`, `packMapHeader`, `packExtensionTypeHeader`, `packBinaryHeader`, `packRawStringHeader`, `packValue`, `writePayload`, `writePayload`, `addPayload`, `addPayload`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 21 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/Packer.scala:22
- `Unpacker` declares 28 abstract members: `hasNext`, `getNextFormat`, `getNextValueType`, `skipValue`, `skipValue`, `unpackNil`, `tryUnpackNil`, `unpackBoolean`, `unpackByte`, `unpackShort`, `unpackInt`, `unpackLong`, `unpackBigInteger`, `unpackFloat`, `unpackDouble`, `unpackString`, `unpackTimestamp`, `unpackTimestamp`, `unpackArrayHeader`, `unpackMapHeader`, `unpackExtTypeHeader`, `unpackExtValue`, `unpackRawStringHeader`, `unpackBinaryHeader`, `unpackValue`, `readPayload`, `readPayload`, `readPayload`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 28 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/Unpacker.scala:22
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- `withThreadLocalStore` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — airframe-http/src/main/scala/wvlet/airframe/http/HttpBackend.scala:122
- `unpack` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpResponseBodyCodec.scala:45, airframe-launcher/src/main/scala/wvlet/airframe/launcher/StringTreeCodec.scala:43
- `writeMsgPack` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:122
- `inputAttributes` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:679
- `outputAttributes` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:680
- `get` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — airframe-surface/src/main/scala/wvlet/airframe/surface/RecordSurface.scala:79
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `withThreadLocalStore` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — airframe-http/src/main/scala/wvlet/airframe/http/HttpBackend.scala:122
- `unpack` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpResponseBodyCodec.scala:45, airframe-launcher/src/main/scala/wvlet/airframe/launcher/StringTreeCodec.scala:43
- `writeMsgPack` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:122
- `inputAttributes` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:679
- `outputAttributes` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:680
- `get` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — airframe-surface/src/main/scala/wvlet/airframe/surface/RecordSurface.scala:79
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- airframe-jmx/README.md links to `treasuredata.com`, but `airframe-jmx/treasuredata.com` 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. — airframe-jmx/README.md:11
- airframe-log/README.md links to `../img/airframe-log/jmx.png`, but `img/airframe-log/jmx.png` 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. — airframe-log/README.md:293
What to do
- Reconcile the README with reality: airframe-jmx/README.md links to `treasuredata.com`, but `airframe-jmx/treasuredata.com` does not exist; airframe-log/README.md links to `../img/airframe-log/jmx.png`, but `img/airframe-log/jmx.png` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
- 10/10 types (100%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 30101 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- 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 Watchdog 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
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/ulid/ULIDBenchmark.scala
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 27 use(s) across 63,101 production line(s) (~0.4/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcService.scala:17 — `NettyServerBuilder`.
- This repository's Scala server sets cookies (airframe-http/src/main/scala/wvlet/airframe/http/HttpHeader.scala:69 — `Set-Cookie` header) and no `httpOnly`, `secure` or `sameSite` flag is switched on anywhere, nor are its cookies Play's, which are HttpOnly by default. (−1.5 on this card.)
What to do
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Flag the cookies the server sets: `HttpCookie(…, secure = true, httpOnly = true)` with `.withSameSite(…)` in akka/pekko-http, `ResponseCookie(…, secure = true, httpOnly = true, sameSite = Some(SameSite.Lax))` in http4s, or Play's `play.http.session.secure = true` — on every session and auth cookie.
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
- `JSONTraverser.traverse` is public and takes `json: JSONValue` from its caller, and it calls itself at line 44 with a piece of `json` (and at line 50), not as a tail call the compiler turns into a loop — and nowhere in `JSONTraverser.traverse` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `JSONTraverser.traverse` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — airframe-json/src/main/scala/wvlet/airframe/json/JSONTraverser.scala:44
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 408 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 | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Strong | Strongest area. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate | Acceptable, with room to improve. |
| Security | 68% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 79% | Strong | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 20 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'com.zaxxer.hikari' (airframe-jdbc/src/main/scala/wvlet/airframe/jdbc/DbConfig.scala:16) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'com.zaxxer.hikari' (airframe-jdbc/src/main/scala/wvlet/airframe/jdbc/DbConfig.scala:16) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'com.zaxxer.hikari' (airframe-jdbc/src/main/scala/wvlet/airframe/jdbc/DbConfig.scala:16) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 49 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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 did not expose a crawlable HTTP endpoint in time — no runtime evidence 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.
- D10 Test Quality — ~29880 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
- 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# only; Java, JavaScript, Scala not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Scala surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .rb, .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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not 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): 593 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 6 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Ruby 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
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby, Scala and Java were read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter; 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; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- 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 Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-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.
Appendix A — Findings (grouped)
Critical — 93 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: org.openjdk.jmh:jmh-core
- Banned license: org.openjdk.jmh:jmh-generator-bytecode
- Banned license: org.openjdk.jmh:jmh-generator-reflection
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 259 finding(s)
- TodoComment airframe-ulid/src/main/scala/wvlet/airframe/ulid/CrockfordBase32.scala:95
- TodoComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:219
- TodoComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:277
- TodoComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:675
- TodoComment airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:377
- TodoComment airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:448
- TodoComment airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:550
- TodoComment airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:560
- TodoComment airframe-sql/src/test/scala/wvlet/airframe/sql/SQLBenchmark.scala:72
- TodoComment airframe-sql/src/test/scala/wvlet/airframe/sql/analyzer/TypeResolverTest.scala:356
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:149
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:590
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:876
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:894
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:151
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:300
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:303
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:405
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:464
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:471
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:561
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:581
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:264
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:355
- TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:394
- TooManyMethods: ICodeEditor airframe-rx-widget/src/main/scala/wvlet/airframe/rx/html/widget/editor/Monaco.scala:2408
- TooManyMethods: AirframeMacros airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:20
- TooManyMethods: HttpServerException airframe-http/src/main/scala/wvlet/airframe/http/HttpServerException.scala:25
- TooManyMethods: ITextModel airframe-rx-widget/src/main/scala/wvlet/airframe/rx/html/widget/editor/Monaco.scala:1043
- TooManyMethods: HttpMessage airframe-http/src/main/scala/wvlet/airframe/http/HttpMessage.scala:27
- TooManyMethods: CompileTimeSurfaceFactory airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:38
- TooManyMethods: Rx airframe-rx/src/main/scala/wvlet/airframe/rx/Rx.scala:136
- TooManyMethods: Rx airframe-rx/src/main/scala/wvlet/airframe/rx/Rx.scala:614
- TooManyMethods: OffsetPacker airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetPacker.scala:25
- TooManyMethods: IEditor airframe-rx-widget/src/main/scala/wvlet/airframe/rx/html/widget/editor/Monaco.scala:1373
- TooManyMethods: OffsetUnpacker airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:32
- TooManyMethods: SurfaceGenerator airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:64
- TooManyMethods: SurfaceFinder airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:212
- FileTooLong: editor/Monaco.scala airframe-rx-widget/src/main/scala/wvlet/airframe/rx/html/widget/editor/Monaco.scala
- FileTooLong: model/Expression.scala airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala
- FileTooLong: airframe/AirframeMacros.scala airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
- FileTooLong: codec/PrimitiveCodec.scala airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala
- FileTooLong: parser/SQLInterpreter.scala airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala
- FileTooLong: surface/CompileTimeSurfaceFactory.scala airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala
- FileTooLong: model/LogicalPlan.scala airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala
- FileTooLong: rx/RxRunner.scala airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala
- FileTooLong: spi/OffsetUnpacker.scala airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala
- FileTooLong: rx/Rx.scala airframe-rx/src/main/scala/wvlet/airframe/rx/Rx.scala
- Duplicated block (8 lines × 2) airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala:13
- Duplicated block (8 lines × 2) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:980
- Duplicated block (8 lines × 2) airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:86
- Duplicated block (8 lines × 2) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:278
- Duplicated block (8 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:166
- Duplicated block (8 lines × 2) airframe-di/.jvm/src/main/scala/wvlet/airframe/lifecycle/JSR250LifeCycleExecutor.scala:37
- Duplicated block (8 lines × 2) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/filter/HttpAccessLogFilter.scala:215
- Duplicated block (8 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:64
- Duplicated block (8 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:498
- Duplicated block (5 lines × 2) airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala:32
- Duplicated block (5 lines × 2) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:182
- Duplicated block (5 lines × 2) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:186
- Duplicated block (5 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:53
- Duplicated block (5 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:254
- Duplicated block (5 lines × 2) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:187
- Duplicated block (5 lines × 2) airframe-metrics/.jvm/src/main/scala/wvlet/airframe/metrics/TimeVector.scala:62
- Unfinished stub — body is `???` airframe-http/src/main/scala/wvlet/airframe/http/HttpBackend.scala:122
- Unfinished stub — body is `???` airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpResponseBodyCodec.scala:45
- Unfinished stub — body is `???` airframe-launcher/src/main/scala/wvlet/airframe/launcher/StringTreeCodec.scala:43
- Unfinished stub — body is `???` airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:122
- Unfinished stub — body is `???` airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:679
- Unfinished stub — body is `???` airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:680
- Unfinished stub — body is `???` airframe-surface/src/main/scala/wvlet/airframe/surface/RecordSurface.scala:79
- Unfinished stub — body is ??? / NotImplementedError airframe-http/src/main/scala/wvlet/airframe/http/HttpBackend.scala:122
- Unfinished stub — body is ??? / NotImplementedError airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpResponseBodyCodec.scala:45
- Unfinished stub — body is ??? / NotImplementedError airframe-launcher/src/main/scala/wvlet/airframe/launcher/StringTreeCodec.scala:43
- Unfinished stub — body is ??? / NotImplementedError airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:122
- Unfinished stub — body is ??? / NotImplementedError airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:679
- Unfinished stub — body is ??? / NotImplementedError airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:680
- Unfinished stub — body is ??? / NotImplementedError airframe-surface/src/main/scala/wvlet/airframe/surface/RecordSurface.scala:79
- Low cohesion: Logger (LCOM4 5) airframe-log/src/main/scala/wvlet/log/Logger.scala:30
- Low cohesion: RPCRequestBenchmark (LCOM4 4) airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/rpc_request/RPCRequestBenchmark.scala:30
- Low cohesion: Logger (LCOM4 4) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:30
- Low cohesion: FluentdLogger (LCOM4 4) airframe-fluentd/src/main/scala/wvlet/airframe/fluentd/FluentdLogger.scala:20
- Low cohesion: SurfaceGenerator (LCOM4 4) airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:64
- Duplicated block (12 lines × 2) airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodec.scala:132
- Duplicated block (12 lines × 2) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/NestedMessagePackBuilder.scala:70
- Duplicated block (12 lines × 2) airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:74
- Duplicated block (12 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:188
- Duplicated block (11 lines × 2) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:82
- Duplicated block (11 lines × 2) airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala:75
- Duplicated block (11 lines × 2) airframe-log/.jvm/src/main/scala/wvlet/log/LogEnv.scala:54
- Duplicated block (11 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:220
- Duplicated block (10 lines × 2) airframe-codec/src/main/scala/wvlet/airframe/codec/CollectionCodec.scala:200
- Duplicated block (10 lines × 2) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:249
- Duplicated block (10 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLParser.scala:51
- Duplicated block (10 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:73
- Off the main sequence: base
- Off the main sequence: ulid
- Off the main sequence: log
- Off the main sequence: surface
- FixmeComment airframe-surface/src/test/scala/wvlet/airframe/surface/MethodSurfaceTest.scala:129
- FixmeComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:239
- FixmeComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:914
- Duplicated block (15 lines × 2) airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:227
- Duplicated block (15 lines × 2) airframe-control/src/main/scala/wvlet/airframe/control/RateLimiter.scala:148
- Duplicated block (15 lines × 2) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:286
- RxRunner.run (cyclomatic 133) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:44
- RxRunner.run (cyclomatic 133) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:105
- RxRunner.run (cognitive 147) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:44
- RxRunner.run (cognitive 147) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:105
- MethodTooLong: RxRunner.run airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:105
- MethodTooLong: DOMRenderer.renderToInternal airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:140
- Duplicated block (21 lines × 2) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleServer.scala:385
- Duplicated block (21 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:300
- Duplicated block (14 lines × 2) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:55
- Duplicated block (14 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:188
- Duplicated block (9 lines × 2) airframe-http/.js/src/main/scala/wvlet/airframe/http/client/JSFetchChannel.scala:164
- Duplicated block (9 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:202
- PlanBuilder.buildCondition (cyclomatic 66) airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetQueryPlanner.scala:84
- AnyCodec.pack (cyclomatic 43) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:931
- MessageFormat.toMessageFormat (cyclomatic 37) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/MessageFormat.scala:93
- SQLGenerator.printRelation (cyclomatic 37) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:158
- SQLGenerator.printExpression (cyclomatic 37) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:370
- HttpRequestMapper.buildControllerMethodArgs (cyclomatic 35) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/router/HttpRequestMapper.scala:37
- OpenAPIGenerator.getOpenAPISchemaOfSurface (cyclomatic 33) airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPIGenerator.scala:448
- DOMRenderer.renderToInternal (cyclomatic 33) airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:140
- JSONScanner.rscan (cyclomatic 31) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:233
- TupleCodec.unpack (cyclomatic 25) airframe-codec/src/main/scala/wvlet/airframe/codec/ScalaStandardCodec.scala:59
- DOMRenderer.addAttribute (cyclomatic 22) airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:344
- CurlChannel.send (cyclomatic 21) airframe-http/.native/src/main/scala/wvlet/airframe/http/client/CurlChannel.scala:46
- CombinedStream.run (cyclomatic 21) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:615
- SQLGenerator.printDDL (cyclomatic 21) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:272
- JSONScanner.scanNumber (cyclomatic 20) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:334
- OptionParser.parse (cyclomatic 20) airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionParser.scala:187
- OffsetUnpacker.unpackByte (cyclomatic 20) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:198
- OpenAPIGenerator.buildFromRouter (cyclomatic 19) airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPIGenerator.scala:205
- HttpLogs.extractRpcArgLog (cyclomatic 18) airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:190
- defaultMessageCodecFinder.findCodec (cyclomatic 17) airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodecFinder.scala:74
- YamlReader.pack (cyclomatic 17) airframe-config/src/main/scala/wvlet/airframe/config/YamlReader.scala:110
- OffsetUnpacker.unpackShort (cyclomatic 17) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:240
- ParquetObjectWriter.packValue (cyclomatic 17) airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:185
- Attribute.matched (cyclomatic 17) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:367
- AirSpecTaskRunner.runSingle (cyclomatic 17) airspec/src/main/scala/wvlet/airspec/runner/AirSpecTaskRunner.scala:212
- FinagleResponseHandler.toHttpResponse (cyclomatic 16) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleResponseHandler.scala:86
- HttpRequestMapper.buildControllerMethodArgs (cognitive 57) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/router/HttpRequestMapper.scala:37
- JSONScanner.rscan (cognitive 49) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:233
- DOMRenderer.addAttribute (cognitive 46) airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:344
- StandardBuilder.set (cognitive 40) airframe-surface/.jvm/src/main/scala/wvlet/airframe/surface/reflect/ObjectBuilder.scala:126
- DOMRenderer.renderToInternal (cognitive 37) airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:140
- OpenAPIGenerator.buildFromRouter (cognitive 33) airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPIGenerator.scala:205
- OptionParser.parse (cognitive 31) airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionParser.scala:187
- JSONScanner.scanNumber (cognitive 30) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:334
- Attribute.matched (cognitive 29) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:367
- SQLInterpreter.visitPredicated (cognitive 29) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:558
- TypeConverter.convert (cognitive 27) airframe-surface/.jvm/src/main/scala/wvlet/airframe/surface/reflect/TypeConverter.scala:34
- CName.toNaturalName (cognitive 27) airframe-surface/src/main/scala/wvlet/airframe/surface/CName.scala:64
- ParamListCodec.unpack (cognitive 26) airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:120
- PlanBuilder.buildCondition (cognitive 26) airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetQueryPlanner.scala:84
- CompileTimeSurfaceFactory.surfaceOf (cognitive 25) airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:75
- AirSpecTaskRunner.runSingle (cognitive 25) airspec/src/main/scala/wvlet/airspec/runner/AirSpecTaskRunner.scala:212
- RouteMatcher.buildPathDFA (cognitive 23) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/router/RouteMatcher.scala:195
- ParquetObjectWriter.packValue (cognitive 23) airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:185
- CombinedStream.run (cognitive 23) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:615
- CommandLauncher.execute (cognitive 22) airframe-launcher/src/main/scala/wvlet/airframe/launcher/Launcher.scala:256
- TimeWindowBuilder.parseOffset (cognitive 22) airframe-metrics/.jvm/src/main/scala/wvlet/airframe/metrics/TimeWindow.scala:194
- CompileTimeSurfaceFactory.methodParametersOf (cognitive 21) airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:575
- SQLGenerator.printDDL (cognitive 20) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:272
- SQLInterpreter.visitQuerySpecification (cognitive 20) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:205
- CurlChannel.send (cognitive 19) airframe-http/.native/src/main/scala/wvlet/airframe/http/client/CurlChannel.scala:46
- OffsetUnpacker.unpackByte (cognitive 19) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:198
- AnyCodec.pack (cognitive 18) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:931
- ServerAddress.apply (cognitive 18) airframe-http/src/main/scala/wvlet/airframe/http/ServerAddress.scala:62
- LogicalPlanPrinter.print (cognitive 18) airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlanPrinter.scala:34
- EitherCodec.unpack (cognitive 17) airframe-codec/src/main/scala/wvlet/airframe/codec/ScalaStandardCodec.scala:231
- CommandLineTokenizer.parse (cognitive 17) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/CommandLineTokenizer.scala:31
- Shell.findJavaCommand (cognitive 17) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:298
- FinagleResponseHandler.toHttpResponse (cognitive 17) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleResponseHandler.scala:86
- JSFetchChannel.readStream (cognitive 17) airframe-http/.js/src/main/scala/wvlet/airframe/http/client/JSFetchChannel.scala:126
- HttpClientIR.buildIR (cognitive 16) airframe-http-codegen/src/main/scala/wvlet/airframe/http/codegen/HttpClientIR.scala:283
- OffsetPacker.packLong (cognitive 16) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetPacker.scala:146
- REDACTED
- REDACTED
- Change coupling: SQLGenerator.scala ↔ SQLInterpreter.scala airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:1
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:97
- Duplicated block (16–27 lines × 2) airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:373
- Duplicated block (25–26 lines × 2) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:167
- Duplicated block (16–20 lines × 2) airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala:64
- Duplicated block (18 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:75
- Duplicated block (16–17 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:125
- Duplicated block (17 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:597
- Duplicated block (15–16 lines × 2) airframe-http/src/main/scala-2/wvlet/airframe/http/RxRouterMacros.scala:33
- Duplicated block (14–15 lines × 7) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:101
- Duplicated block (6–15 lines × 2) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:644
- Duplicated block (12–13 lines × 2) airframe-control/src/main/scala/wvlet/airframe/control/IO.scala:42
- Duplicated block (13 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:175
- Duplicated block (11–12 lines × 2) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/ThreadUtil.scala:27
- Duplicated block (11 lines × 3) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcException.scala:42
- Duplicated block (8–9 lines × 2) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:94
- Duplicated block (6–7 lines × 3) airframe-core-base/src/main/scala-3/wvlet/airframe/log/LoggerMacros.scala:22
- Duplicated block (4–6 lines × 3) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:329
- Duplicated block (5–6 lines × 2) airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:92
- Duplicated block (6 lines × 2) airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:407
- Duplicated block (4–5 lines × 6) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:311
- Duplicated block (51 lines × 2) airframe-di/src/main/scala/wvlet/airframe/LazyF0.scala:17
- Duplicated block (20 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/internal/LocalRPCContext.scala:22
- Duplicated block (7 lines × 3) airframe-core/.js/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:15
- Duplicated block (10 lines × 3) airframe-log/.js/src/main/scala/wvlet/log/LogEnv.scala:14
- Recursive walk over a caller-supplied document has no depth cap airframe-json/src/main/scala/wvlet/airframe/json/JSONTraverser.scala:44
Minor — 39 finding(s)
- Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:354
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:579
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:233
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:247
- Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:224
- Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:58
- Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:113
- Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:189
- Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:264
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:500
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:255
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:220
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:601
- Duplicated predicate airframe-http-codegen/src/main/scala/wvlet/airframe/http/codegen/HttpClientIR.scala:319
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:119
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:116
- Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:200
- Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:229
- Duplicated predicate airframe-http/src/main/scala/wvlet/airframe/http/HttpMessage.scala:135
- Duplicated predicate airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:32
- Fat interface: Packer (21 abstract members) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/Packer.scala:22
- Fat interface: Unpacker (28 abstract members) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/Unpacker.scala:22
- README/code drift airframe-jmx/README.md:11
- README/code drift airframe-log/README.md:293
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Large public API surface
- No SAST
- Benchmarks don't track allocations airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/ulid/ULIDBenchmark.scala
- No security response headers detected
- Secure cookie flags not detected
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch airframe-surface/.jvm/src/main/scala/wvlet/airframe/surface/reflect/package.scala:82
- Subsumed condition operand airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionParser.scala:48
Minor — 3 finding(s)
- Outdated: ch.qos.logback:logback-core
- Outdated: commons-collections:commons-collections
- Outdated: org.scala-lang.modules:scala-parallel-collections_2.13
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-99761af3aa5c417ab356a2a98a7628af/history.json --exit-code 0 --source . | 4 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-99761af3aa5c417ab356a2a98a7628af/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 89 | 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 | 1 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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 6 file(s) — `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala`, `airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala`, `airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala`, … (+1 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 |