Public report of wvlet/airframe, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 15:01 UTC · Survey ID cd_0ea3bfcf5fc74ce1b41f7296aaadd93f
wvlet/airframe
Measured 14 November 2026, 15:01 UTC, at code version 79fcb13
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 58,805 lines of product code in 45 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Maturity, 60
Findings by how serious they are
91 critical360 serious51 minor
14 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 15:01 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
55of 55 dimensions measured by tools.
477of 502 findings point to an exact file and line, so you can open each one in the code. The other 25 concern the repository as a whole, such as missing documentation.
55dimensions across 6 lenses, read from 58,805 lines of product code in 45 projects.
wvlet/airframe falls short of our standard for production, held back most by its Maturity lens, the way the project is documented and understood. It scores 63 out of 100 and is rated Adequate, and 88 of its 91 critical findings are security problems.
Maturity, at 60, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is replacing the three packages under a banned licence, worth about 2 points. Making the naming consistent would lift Maturity itself, also worth about 2.
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 three packages carry licence risk. Pinning each tool to an exact version, limiting each secret to its own step and replacing or clearing the banned-licence packages 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 product code is 58,805 lines, about €120,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 66%Tests 34%
New since the last survey: 103 findings
These 103 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Edited copy of a member (61 corresponding lines) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala
Code Duplication · Edited copy of a member (45 corresponding lines) airframe-core/.native/src/main/scala-3/wvlet/airframe/log/LogTimestampFormatter.scala
Code Duplication · Edited copy of a member (48 corresponding lines) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Parallel.scala
Code Duplication · Edited copy of a member (33 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala
Code Duplication · Edited copy of a member (40 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala
Code Duplication · Edited copy of a member (39 corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala
Code Duplication · Edited copy of a member (22 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala
Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala
Code Duplication · Edited copy of a member (29 corresponding lines) airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala
Code Duplication · Edited copy of a member (35 corresponding lines) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala
Code Duplication · Edited copy of a member (36 corresponding lines) airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala
Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala
Code Duplication · Edited copy of a member (20 corresponding lines) airspec/src/main/scala/wvlet/airspec/spi/RichAsserts.scala
Code Duplication · Edited copy of a member (26 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala
Code Duplication · Edited copy of a member (18 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala
Code Duplication · Edited copy of a member (13 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala
Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
Code Duplication · Edited copies of one member (4 members, 26+ corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala
Code Duplication · Edited copy of a member (16 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala
Code Duplication · Edited copy of a member (21 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala
Code Duplication · Edited copy of a member (18 corresponding lines) airspec/src/main/scala/wvlet/airspec/spi/RichAsserts.scala
Code Duplication · Edited copy of a member (20 corresponding lines) airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala
Code Duplication · Edited copy of a member (21 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLParser.scala
Code Duplication · Edited copy of a member (22 corresponding lines) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala
Code Duplication · Edited copy of a member (10 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala
Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) airframe-core-base/src/main/scala-3/wvlet/airframe/log/LoggerMacros.scala
Code Duplication · Edited copy of a member (16 corresponding lines) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/filter/HttpAccessLogFilter.scala
Code Duplication · Edited copy of a member (16 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
Code Duplication · Edited copy of a member (16 corresponding lines) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala
Code Duplication · Edited copy of a member (20 corresponding lines) airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala
Code Duplication · Edited copy of a member (14 corresponding lines) airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala
Code Duplication · Edited copy of a member (13 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala
Code Duplication · Edited copy of a member (15 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala
Code Duplication · Edited copy of a member (11 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala
Code Duplication · Edited copy of a member (14 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala
Code Duplication · Edited copy of a member (17 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala
Code Duplication · Edited copy of a member (7 corresponding lines) airspec/src/main/scala/wvlet/airspec/AirSpecDef.scala
Code Duplication · Edited copy of a member (10 corresponding lines) airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala
Code Duplication · Edited copy of a member (23 corresponding lines) airframe-http/src/main/scala/wvlet/airframe/http/client/HttpClients.scala
Code Duplication · Edited copy of a member (13 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala
Code Duplication · Edited copy of a member (10 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala
Code Duplication · Edited copy of a member (8 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala
Code Duplication · Edited copy of a member (12 corresponding lines) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala
Code Duplication · Edited copy of a member (9 corresponding lines) airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala
Code Duplication · Edited copies of one member (6 members, 17+ corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala
Code Duplication · Edited copy of a member (14 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala
Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/MetricsCodec.scala
Code Duplication · Edited copy of a member (5 corresponding lines) airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala
Code Duplication · Edited copy of a member (17 corresponding lines) airframe-metrics/src/main/scala/wvlet/airframe/metrics/Count.scala
Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) airframe-codec/.jvm/src/main/scala/wvlet/airframe/codec/JDBCCodec.scala
Code Duplication · Edited copy of a member (17 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala
Code Duplication · Edited copy of a member (19 corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala
Code Duplication · Edited copy of a member (13 corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/NestedMessagePackBuilder.scala
Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
Code Duplication · Edited copy of a member (14 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) airframe-control/src/main/scala/wvlet/airframe/control/IO.scala
Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
Code Duplication · Edited copy of a member (11 corresponding lines) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/Router.scala
Code Duplication · Edited copy of a member (16 corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala
Code Duplication · Edited copy of a member (12 corresponding lines) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala
Code Duplication · Edited copy of a member (9 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala
Code Duplication · Edited copy of a member (15 corresponding lines) airframe-di/src/main/scala/wvlet/airframe/lifecycle/LifeCycleManager.scala
Code Duplication · Edited copy of a member (15 corresponding lines) airspec/.jvm/src/main/scala/wvlet/airspec/Compat.scala
Code Duplication · Edited copy of a member (6 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala
Code Duplication · Edited copy of a member (11 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala
Code Duplication · Edited copy of a member (9 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/IOUtil.scala
Code Duplication · Edited copy of a member (14 corresponding lines) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala
Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala
Code Duplication · Edited copy of a member (15 corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/PrefixedULIDCodec.scala
Code Duplication · Edited copy of a member (10 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala
Code Duplication · Edited copy of a member (8 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala
Code Duplication · Edited copy of a member (8 corresponding lines) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala
Code Duplication · Edited copy of a member (8 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
Code Duplication · Edited copy of a member (6 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala
Code Duplication · Edited copy of a member (6 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala
Code Duplication · Edited copy of a member (8 corresponding lines) airframe-http/src/main/scala/wvlet/airframe/http/HttpFilter.scala
Code Duplication · Edited copy of a member (8 corresponding lines) airframe-log/src/main/scala/wvlet/log/Logger.scala
Code Duplication · Edited copy of a member (11 corresponding lines) airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala
Code Duplication · Edited copy of a member (7 corresponding lines) airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala
Code Duplication · Edited copy of a member (6 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala
Code Duplication · Edited copy of a member (11 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala
Code Duplication · Edited copy of a member (11 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala
Code Duplication · Edited copy of a member (5 corresponding lines) airframe-log/.jvm/src/main/scala/wvlet/log/io/IOUtil.scala
Code Duplication · Edited copy of a member (3 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogRecord.scala
Code Duplication · Edited copy of a member (7 corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/TimeCodec.scala
Code Duplication · Edited copy of a member (10 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala
Code Duplication · Edited copy of a member (6 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogLevel.scala
Code Duplication · Edited copy of a member (10 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala
Code Duplication · Edited copy of a member (6 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala
Code Duplication · Edited copy of a member (7 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala
Code Duplication · Edited copy of a member (2 corresponding lines) airframe-http/src/main/scala-3/wvlet/airframe/http/HttpMessageBase.scala
Code Duplication · Edited copy of a member (2 corresponding lines) airframe-http/src/main/scala-3/wvlet/airframe/http/HttpMessageBase.scala
Code Duplication · Edited copy of a member (7 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/IOUtil.scala
Code Duplication · Edited copy of a member (8 corresponding lines) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala
Code Duplication · Edited copy of a member (2 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala
Code Duplication · Edited copy of a member (8 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala
Code Duplication · Edited copy of a member (5 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala
Code Duplication · Edited copy of a member (5 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala
Code Duplication · Edited copy of a member (2 corresponding lines) airframe-launcher/src/main/scala-2/wvlet/airframe/launcher/LauncherCompat.scala
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 4 findings
These 4 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.
€40,000 to €200,000, for 673 to 2,135 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.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 3 Banned license finding(s) in License Compliance.
Resolve the 2 `extractRpcArgLog` spells `Rpc` where 36 names in the project spell it… finding(s) in Naming Consistency — start with HttpAccessLogWriter.scala, HttpLogs.scala.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Maturity, at 60 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 3 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 37,378 lines over the last 90 days, which is about 151,589 lines a year. At that pace, the extra work comes to an estimated 9.7 to 58.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
219 modules, with 376 dependencies between them. 8 loops run through 28 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 179 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
airframe.sql.model.LogicalPlan uses log, so a change to log can break airframe.sql.model.LogicalPlan, while a change to airframe.sql.model.LogicalPlan can't break log.
Position
Below the diagonal: airframe.sql.model.LogicalPlan uses a module listed above it, which is the healthy direction.
8→14 airframe.sql.model.LogicalPlan uses airframe.sql.modelpart of a loop✕
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.
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
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.
8→28 airframe.sql.model.LogicalPlan uses airframe.sql.analyzerpart of a loop✕
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.
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
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.
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
Below the diagonal: airframe.control.Retry uses a module listed above it, which is the healthy 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
Below the diagonal: airframe.control.Retry uses a module listed above it, which is the healthy 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.
11→30 airframe.http.HttpMessage uses airframe.httppart of a loop✕
Connections
19 pairs of types, where a type in airframe.http.HttpMessage uses a type in airframe.http.
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.
airframe.msgpack.spi uses airframe.json, so a change to airframe.json can break airframe.msgpack.spi, while a change to airframe.msgpack.spi can't break airframe.json.
Position
Below the diagonal: airframe.msgpack.spi uses a module listed above it, which is the healthy 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
Below the diagonal: airframe.sql.model uses a module listed above it, which is the healthy direction.
14→21 airframe.sql.model uses airframe.sql.model.Expressionpart of a loop✕
Connections
1 pair of types, where a type in airframe.sql.model uses a type in airframe.sql.model.Expression.
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.
14→25 airframe.sql.model uses airframe.sql.catalogpart of a loop✕
Connections
2 pairs of types, where a type in airframe.sql.model uses a type in airframe.sql.catalog.
airframe.sql.model uses airframe.sql.catalog, so a change to airframe.sql.catalog can break airframe.sql.model, while a change to airframe.sql.model can't break airframe.sql.catalog.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→28 airframe.sql.model uses airframe.sql.analyzerpart of a loop✕
Connections
4 pairs of types, where a type in airframe.sql.model uses a type in airframe.sql.analyzer.
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.
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
Below the diagonal: airframe.surface.reflect uses a module listed above it, which is the healthy 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.
16→19 airframe.tracing uses airframe.lifecyclepart of a loop✕
Connections
1 pair of types, where a type in airframe.tracing uses a type in airframe.lifecycle.
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
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→22 airframe.tracing uses airframepart of a loop✕
Connections
3 pairs of types, where a type in airframe.tracing uses a type in airframe.
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.
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.
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.
airframe.launcher.OptionParser uses log, so a change to log can break airframe.launcher.OptionParser, while a change to airframe.launcher.OptionParser can't break log.
Position
Below the diagonal: airframe.launcher.OptionParser uses a module listed above it, which is the healthy direction.
airframe.launcher.OptionParser uses airframe.surface, so a change to airframe.surface can break airframe.launcher.OptionParser, while a change to airframe.launcher.OptionParser can't break airframe.surface.
Position
Below the diagonal: airframe.launcher.OptionParser uses a module listed above it, which is the healthy direction.
airframe.launcher.OptionParser uses airframe.surface.reflect, so a change to airframe.surface.reflect can break airframe.launcher.OptionParser, while a change to airframe.launcher.OptionParser can't break airframe.surface.reflect.
Position
Below the diagonal: airframe.launcher.OptionParser uses a module listed above it, which is the healthy direction.
18→24 airframe.launcher.OptionParser uses airframe.launcherpart of a loop✕
Connections
1 pair of types, where a type in airframe.launcher.OptionParser uses a type in airframe.launcher.
airframe.launcher.OptionParser uses airframe.launcher, so a change to airframe.launcher can break airframe.launcher.OptionParser, while a change to airframe.launcher.OptionParser can't break airframe.launcher.
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.
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.
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
Below the diagonal: airframe.lifecycle uses a module listed above it, which is the healthy direction.
19→22 airframe.lifecycle uses airframepart of a loop✕
Connections
1 pair of types, where a type in airframe.lifecycle uses a type in airframe.
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.
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.
airframe.sql.model.Expression uses log, so a change to log can break airframe.sql.model.Expression, while a change to airframe.sql.model.Expression can't break log.
Position
Below the diagonal: airframe.sql.model.Expression uses a module listed above it, which is the healthy direction.
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.
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.
21→25 airframe.sql.model.Expression uses airframe.sql.catalogpart of a loop✕
Connections
18 pairs of types, where a type in airframe.sql.model.Expression uses a type in airframe.sql.catalog.
airframe.sql.model.Expression uses airframe.sql.catalog, so a change to airframe.sql.catalog can break airframe.sql.model.Expression, while a change to airframe.sql.model.Expression can't break airframe.sql.catalog.
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.
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.
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.
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.
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.
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.
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.
23→30 airframe.http.client uses airframe.httppart 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.
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.
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
Below the diagonal: airframe.launcher uses a module listed above it, which is the healthy 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.
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.
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
Below the diagonal: airframe.launcher uses a module listed above it, which is the healthy direction.
airframe.launcher uses airframe.launcher.OptionParser, so a change to airframe.launcher.OptionParser can break airframe.launcher, while a change to airframe.launcher can't break airframe.launcher.OptionParser.
Position
Below the diagonal: airframe.launcher uses a module listed above it, which is the healthy 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.
airframe.config uses airframe.surface, so a change to airframe.surface can break airframe.config, while a change to airframe.config can't break airframe.surface.
Position
Below the diagonal: airframe.config uses a module listed above it, which is the healthy 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.
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.
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.
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.
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
Below the diagonal: airframe.http.router uses a module listed above it, which is the healthy direction.
27→30 airframe.http.router uses airframe.httppart of a loop✕
Connections
13 pairs of types, where a type in airframe.http.router uses a type in airframe.http.
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.
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
Below the diagonal: airframe.sql.analyzer uses a module listed above it, which is the healthy 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy 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.
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
Below the diagonal: airframe.http.finagle uses a module listed above it, which is the healthy 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.
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.
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.
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.
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.
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.
airframe.http.okhttp uses airframe.rx, so a change to airframe.rx can break airframe.http.okhttp, while a change to airframe.http.okhttp can't break airframe.rx.
Position
Below the diagonal: airframe.http.okhttp uses a module listed above it, which is the healthy direction.
airframe.http.okhttp uses airframe.http.HttpMessage, so a change to airframe.http.HttpMessage can break airframe.http.okhttp, while a change to airframe.http.okhttp can't break airframe.http.HttpMessage.
Position
Below the diagonal: airframe.http.okhttp uses a module listed above it, which is the healthy direction.
airframe.http.okhttp uses airframe.http.client, so a change to airframe.http.client can break airframe.http.okhttp, while a change to airframe.http.okhttp can't break airframe.http.client.
Position
Below the diagonal: airframe.http.okhttp uses a module listed above it, which is the healthy direction.
airframe.http.okhttp uses airframe.http, so a change to airframe.http can break airframe.http.okhttp, while a change to airframe.http.okhttp can't break airframe.http.
Position
Below the diagonal: airframe.http.okhttp uses a module listed above it, which is the healthy direction.
airframe.http.grpc.internal uses log, so a change to log can break airframe.http.grpc.internal, while a change to airframe.http.grpc.internal can't break log.
Position
Below the diagonal: airframe.http.grpc.internal uses a module listed above it, which is the healthy 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.
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.
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.
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.
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.
37→39 airframe.http.grpc.internal uses airframe.http.grpcpart of a loop✕
Connections
6 pairs of types, where a type in airframe.http.grpc.internal uses a type in airframe.http.grpc.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
airframe.http.recorder uses airframe.http.client, so a change to airframe.http.client can break airframe.http.recorder, while a change to airframe.http.recorder can't break airframe.http.client.
Position
Below the diagonal: airframe.http.recorder uses a module listed above it, which is the healthy 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.
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.
At a glance — Code Health · 64% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
89
High / Critical
A03:2025 — Software Supply Chain Failures
4
Medium
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 3 Banned license finding(s) in License Compliance; Resolve the 2 `extractRpcArgLog` spells `Rpc` where 36 names in the project spell it… finding(s) in Naming Consistency — start with HttpAccessLogWriter.scala, HttpLogs.scala.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Banned license finding(s) in License Compliance.
Resolve the 2 `extractRpcArgLog` spells `Rpc` where 36 names in the project spell it… finding(s) in Naming Consistency — start with HttpAccessLogWriter.scala, HttpLogs.scala.
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.
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.
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.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 91
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.
Serious — 360
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.
Minor — 51
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 14
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 55 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 477 of 502 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a 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.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its 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.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 110 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
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.
+ 22 more group(s) — more in Appendix A; the complete list is findings.md.
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.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
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.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
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).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
58 duplicated block group(s) detected. 7.1 % of the production lines (4,162 of 58,805) are in a reported copy. A further 104 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (8 corresponding lines) · ×9airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:242
Edited copy of a member (6 corresponding lines) · ×7airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:144
Edited copy of a member (10 corresponding lines) · ×6airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala:133
Edited copy of a member (11 corresponding lines) · ×6airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:251
+ 70 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 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 (10 warning-level).
Resolve the 9 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with LogFormat.scala (3), ReflectSurfaceFactory.scala (2), StopWatch.scala. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 7 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with StopWatch.scala (2), Logger.scala (2), Resource.scala. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.3 / 10Stronggated by 4 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
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).
Off the main sequence: base · ×4
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).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
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).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
8 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.
Outdated: ch.qos.logback:logback-core · ×8
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
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.
Banned license: org.openjdk.jmh:jmh-core · ×3
What to do
Resolve the 3 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
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.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
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.
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).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
5 naming inconsistencies among 114 declarations measured against a convention their peers follow.
`extractRpcArgLog` spells `Rpc` where 36 names in the project spell it `RPC` · ×2airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:164
`getProcessIDOfCurrentJVM` spells `ID` where 64 names in the project spell it `Id`airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:122
`getProcessID` spells `ID` where 64 names in the project spell it `Id`airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:135
`toYAML` spells `YAML` where 23 names in the project spell it `Yaml`airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPI.scala:42
What to do
Resolve the 2 `extractRpcArgLog` spells `Rpc` where 36 names in the project spell it… finding(s) in Naming Consistency — start with HttpAccessLogWriter.scala, HttpLogs.scala. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 `getProcessIDOfCurrentJVM` spells `ID` where 64 names in the project… finding(s) in Naming Consistency — start with Shell.scala. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `getProcessID` spells `ID` where 64 names in the project spell it `Id` finding(s) in Naming Consistency — start with Shell.scala. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 4 build units (npm, sbt) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
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).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
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.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
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).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
`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.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
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 15 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:4
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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Read from this repository's Scala source and the Java beside it: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcService.scala:17 — `NettyServerBuilder`), so its Scala source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Scala spelling appears in production source, not proven on every route. A Play application is credited the security headers Play's default `SecurityHeadersFilter` sends unless its build or configuration switches that filter off, and its cookies the HttpOnly flag Play sets by default.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
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.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
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.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
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
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
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 — 56 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — 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 (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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.
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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .rb, .scala source were not judged.
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.
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): 597 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 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; 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
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — 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 Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) 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)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Banned license: org.openjdk.jmh:jmh-core — `org.openjdk.jmh:jmh-core` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in its sbt build. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: org.openjdk.jmh:jmh-generator-bytecode — `org.openjdk.jmh:jmh-generator-bytecode` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in its sbt build. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: org.openjdk.jmh:jmh-generator-reflection — `org.openjdk.jmh:jmh-generator-reflection` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in its sbt build. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
TodoComment airframe-ulid/src/main/scala/wvlet/airframe/ulid/CrockfordBase32.scala:95— // TODO: Use reverseInPlace when Scala 2.12 dropped — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:219— // TODO support type erasure instead of using AnyRefSurface — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:277— // TODO Represent low/hi bounds — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:675— // TODO: Deprecate RuntimeMethodParameter — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:377— // TODO We may need to expand Select(Ident(x.y.z....), TermName("a")) => — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:448— // TODO: This doesn't work for local case class with default parameter values in Scala.js — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:550— // TODO natural type conversion (e.g., Int -> Long, etc.) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:560— // TODO: Support companion object call for instantiating the object — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/test/scala/wvlet/airframe/sql/SQLBenchmark.scala:72— // TODO support rollup operator — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/test/scala/wvlet/airframe/sql/analyzer/TypeResolverTest.scala:356— // TODO ra2 shouldn't be included? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:149— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:590— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:876— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:894— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:151— // TODO union, except, intersect — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:300— // TODO resolve join types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:303— // TODO nodeLocation is correct? => Maybe not, but giving a close location is ok for now — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:405— // TODO parse qName — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:464— // TODO Parse double-type precision properly — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:471— // TODO Parse decimal-type precision properly — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:561— // TODO add predicate — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:581— // TODO: Handle ESCAPE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:264— // TODO Should we handle quotation in the name or just reject such strings? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:355— // TODO handle (catalog).(database).(table) names in the qualifier — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:394— // TODO handle (catalog).(database).(table) names in the qualifier — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TooManyMethods: ICodeEditor airframe-rx-widget/src/main/scala/wvlet/airframe/rx/html/widget/editor/Monaco.scala:2408— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: AirframeMacros airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:20— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HttpServerException airframe-http/src/main/scala/wvlet/airframe/http/HttpServerException.scala:25— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: ITextModel airframe-rx-widget/src/main/scala/wvlet/airframe/rx/html/widget/editor/Monaco.scala:1043— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: HttpMessage airframe-http/src/main/scala/wvlet/airframe/http/HttpMessage.scala:27— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: CompileTimeSurfaceFactory airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:38— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Rx airframe-rx/src/main/scala/wvlet/airframe/rx/Rx.scala:136— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Rx airframe-rx/src/main/scala/wvlet/airframe/rx/Rx.scala:614— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: OffsetPacker airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetPacker.scala:25— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: IEditor airframe-rx-widget/src/main/scala/wvlet/airframe/rx/html/widget/editor/Monaco.scala:1373— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: OffsetUnpacker airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:32— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: SurfaceGenerator airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:64— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SurfaceFinder airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:212— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: editor/Monaco.scala airframe-rx-widget/src/main/scala/wvlet/airframe/rx/html/widget/editor/Monaco.scala— FileTooLong — 3043 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2543 over it, 6.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: model/Expression.scala airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala— FileTooLong — 900 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 400 over it, 1.80× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: airframe/AirframeMacros.scala airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala— FileTooLong — 770 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 270 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: codec/PrimitiveCodec.scala airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala— FileTooLong — 757 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 257 over it, 1.51× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: parser/SQLInterpreter.scala airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala— FileTooLong — 689 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: SQLInterpreter (33-1024). The bar is 500 significant lines; this is 189 over it, 1.38× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: surface/CompileTimeSurfaceFactory.scala airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala— FileTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 174 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: model/LogicalPlan.scala airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala— FileTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 127 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: rx/RxRunner.scala airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala— FileTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: RxRunner (87-784). The bar is 500 significant lines; this is 71 over it, 1.14× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: spi/OffsetUnpacker.scala airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala— FileTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 39 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: rx/Rx.scala airframe-rx/src/main/scala/wvlet/airframe/rx/Rx.scala— FileTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (8 lines × 2) airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala:13— airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala:13-20 | airframe-log/.js/src/main/scala/wvlet/log/JSConsoleLogHandler.scala:13-20 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala:13` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:980— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:980-987 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:1004-1011 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:1013` calls `typeArgs` and `airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:989` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:86— airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:86-93 | airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:151-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:278— airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:278-285 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:356-363 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:278` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:286` calls `reportError`, `logError` and `airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:364` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:166— airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:166-173 | airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:192-199 — before extracting anything, compare `airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala` and `airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:407— airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:407-414 | airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:438-445 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:407` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) airframe-di/.jvm/src/main/scala/wvlet/airframe/lifecycle/JSR250LifeCycleExecutor.scala:37— airframe-di/.jvm/src/main/scala/wvlet/airframe/lifecycle/JSR250LifeCycleExecutor.scala:37-44 | airframe-surface/.jvm/src/main/scala/wvlet/airframe/surface/reflect/package.scala:30-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-di/.jvm/src/main/scala/wvlet/airframe/lifecycle/JSR250LifeCycleExecutor.scala:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/filter/HttpAccessLogFilter.scala:215— airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/filter/HttpAccessLogFilter.scala:215-222 | airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:323-330 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:64— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:64-71 | airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/RuntimeeGenericSurface.scala:44-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:498— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:498-505 | airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:323-330 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×9
Edited copy of a member (8 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:242— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:242-249 | airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:272-284 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:74— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:74-81 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:82-92 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:39— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:39-46 | airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:310-318 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:293— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:293-300 | airspec/src/main/scala-2/wvlet/airspec/AirSpecMacros.scala:58-71 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) airframe-http/src/main/scala/wvlet/airframe/http/HttpFilter.scala:56— airframe-http/src/main/scala/wvlet/airframe/http/HttpFilter.scala:56-63 | airframe-http/src/main/scala/wvlet/airframe/http/HttpContext.scala:64-71 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) airframe-log/src/main/scala/wvlet/log/Logger.scala:147— airframe-log/src/main/scala/wvlet/log/Logger.scala:147-160 | airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:120-127 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:387— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:387-394 | airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:194-201 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:166— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:166-173 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:183-192 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:180— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:180-187 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:199-208 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×7
Edited copy of a member (6 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:144— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:144-149 | airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:153-160 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:57— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:57-62 | airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala:58-67 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:136— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:136-141 | airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:142-151 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:196— airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:196-201 | airframe-log/src/main/scala/wvlet/log/Logger.scala:239-246 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogLevel.scala:35— airframe-core/src/main/scala-3/wvlet/airframe/log/LogLevel.scala:35-40 | airframe-log/src/main/scala/wvlet/log/LogLevel.scala:34-42 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:218— airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:218-223 | airframe-log/src/main/scala/wvlet/log/Logger.scala:264-272 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodecFactory.scala:86— airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodecFactory.scala:86-95 | airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodecFinder.scala:60-65 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Unfinished stub — body is `???` airframe-http/src/main/scala/wvlet/airframe/http/HttpBackend.scala:122— `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.
Unfinished stub — body is `???` airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpResponseBodyCodec.scala:45— `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.
Unfinished stub — body is `???` airframe-launcher/src/main/scala/wvlet/airframe/launcher/StringTreeCodec.scala:43— `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.
Unfinished stub — body is `???` airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:122— `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.
Unfinished stub — body is `???` airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:679— `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.
Unfinished stub — body is `???` airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:680— `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.
Unfinished stub — body is `???` airframe-surface/src/main/scala/wvlet/airframe/surface/RecordSurface.scala:79— `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.
Unfinished stub — body is ??? / NotImplementedError airframe-http/src/main/scala/wvlet/airframe/http/HttpBackend.scala:122— `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.
Unfinished stub — body is ??? / NotImplementedError airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpResponseBodyCodec.scala:45— `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.
Unfinished stub — body is ??? / NotImplementedError airframe-launcher/src/main/scala/wvlet/airframe/launcher/StringTreeCodec.scala:43— `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.
Unfinished stub — body is ??? / NotImplementedError airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:122— `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.
Unfinished stub — body is ??? / NotImplementedError airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:679— `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.
Unfinished stub — body is ??? / NotImplementedError airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:680— `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.
Unfinished stub — body is ??? / NotImplementedError airframe-surface/src/main/scala/wvlet/airframe/surface/RecordSurface.scala:79— `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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×6
Edited copy of a member (10 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala:133— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala:133-142 | airframe-log/.jvm/src/main/scala/wvlet/log/LogRotationHandler.scala:141-155 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:90— airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:90-102 | airframe-rx/.native/src/main/scala-3/wvlet/airframe/rx/compat.scala:98-107 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala:113— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala:113-122 | airframe-log/.jvm/src/main/scala/wvlet/log/LogRotationHandler.scala:116-130 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:124— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:124-133 | airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:128-140 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:291— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:291-300 | airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:331-344 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:157— airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:157-166 | airframe-log/src/main/scala/wvlet/log/Logger.scala:195-206 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×6
Edited copy of a member (11 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:251— airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:251-261 | airframe-log/src/main/scala/wvlet/log/Logger.scala:303-319 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/Router.scala:221— airframe-http/.jvm/src/main/scala/wvlet/airframe/http/Router.scala:221-231 | airframe-http/.jvm/src/main/scala/wvlet/airframe/http/Router.scala:233-243 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:17— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:17-27 | airframe-log/.jvm/src/main/scala/wvlet/log/LogEnv.scala:15-30 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:199— airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:199-214 | airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:185-195 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:133— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:133-144 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:152-162 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:148— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:148-159 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:166-176 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×5
Edited copy of a member (16 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:219— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:219-234 | airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:244-264 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/filter/HttpAccessLogFilter.scala:159— airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/filter/HttpAccessLogFilter.scala:159-174 | airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:105-121 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:716— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:716-731 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:841-860 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:310— airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:310-329 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClientCalls.scala:69-84 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:527— airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:527-542 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:544-559 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×5
Edited copy of a member (14 corresponding lines) airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:73— airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:73-88 | airframe-rx/.native/src/main/scala-3/wvlet/airframe/rx/compat.scala:82-95 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:120— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:120-133 | airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala:136-154 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:94— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:94-107 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:106-122 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:699— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:699-712 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:820-837 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:91— airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:91-104 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:109-122 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×5
Edited copy of a member (7 corresponding lines) airspec/src/main/scala/wvlet/airspec/AirSpecDef.scala:116— airspec/src/main/scala/wvlet/airspec/AirSpecDef.scala:116-122 | airspec/src/main/scala/wvlet/airspec/AirSpecDef.scala:136-143 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala:54— airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala:54-60 | airframe-log/.js/src/main/scala/wvlet/log/JSConsoleLogHandler.scala:58-65 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/TimeCodec.scala:27— airframe-codec/src/main/scala/wvlet/airframe/codec/TimeCodec.scala:27-35 | airframe-msgpack/.jvm/src/main/scala/wvlet/airframe/msgpack/impl/PackerImpl.scala:136-142 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:283— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:283-289 | airspec/src/main/scala-2/wvlet/airspec/AirSpecMacros.scala:43-54 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/IOUtil.scala:30— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/IOUtil.scala:30-36 | airframe-log/.jvm/src/main/scala/wvlet/log/io/IOUtil.scala:31-40 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (5 lines × 2) airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala:32— airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala:32-36 | airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala:84-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:186— airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:186-190 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:201-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:186` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:53— airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:53-57 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:381-385 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:254— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:254-258 | airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:113-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:187— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:187-191 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:216-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: Logger (LCOM4 5) airframe-log/src/main/scala/wvlet/log/Logger.scala:30— Logger's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RPCRequestBenchmark (LCOM4 4) airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/rpc_request/RPCRequestBenchmark.scala:30— RPCRequestBenchmark's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Logger (LCOM4 4) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:30— Logger's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FluentdLogger (LCOM4 4) airframe-fluentd/src/main/scala/wvlet/airframe/fluentd/FluentdLogger.scala:20— FluentdLogger's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SurfaceGenerator (LCOM4 4) airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:64— SurfaceGenerator's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:205— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:205-217 | airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala:231-250 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:75— airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:75-87 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:89-101 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:201— airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:201-217 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:423-435 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/NestedMessagePackBuilder.scala:69— airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/NestedMessagePackBuilder.scala:69-81 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/StreamMessagePackBuilder.scala:71-84 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:54— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:54-68 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:59-76 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) airframe-di/src/main/scala/wvlet/airframe/lifecycle/LifeCycleManager.scala:172— airframe-di/src/main/scala/wvlet/airframe/lifecycle/LifeCycleManager.scala:172-186 | airframe-di/src/main/scala/wvlet/airframe/lifecycle/LifeCycleManager.scala:188-202 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) airspec/.jvm/src/main/scala/wvlet/airspec/Compat.scala:65— airspec/.jvm/src/main/scala/wvlet/airspec/Compat.scala:65-83 | airspec/.native/src/main/scala-3/wvlet/airspec/Compat.scala:47-61 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/PrefixedULIDCodec.scala:28— airframe-codec/src/main/scala/wvlet/airframe/codec/PrefixedULIDCodec.scala:28-42 | airframe-codec/src/main/scala/wvlet/airframe/codec/ULIDCodec.scala:28-42 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×4
Edited copy of a member (5 corresponding lines) airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:20— airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:20-24 | airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:28-32 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) airframe-log/.jvm/src/main/scala/wvlet/log/io/IOUtil.scala:49— airframe-log/.jvm/src/main/scala/wvlet/log/io/IOUtil.scala:49-60 | airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/IOUtil.scala:45-49 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:270— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:270-274 | airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala:306-314 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala:125— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogRotationHandler.scala:125-129 | airframe-log/.jvm/src/main/scala/wvlet/log/LogRotationHandler.scala:132-139 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (2 corresponding lines) · ×4
Edited copy of a member (2 corresponding lines) airframe-http/src/main/scala-3/wvlet/airframe/http/HttpMessageBase.scala:35— airframe-http/src/main/scala-3/wvlet/airframe/http/HttpMessageBase.scala:35-36 | airframe-http/src/main/scala-3/wvlet/airframe/http/HttpServerExceptionBase.scala:37-38 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) airframe-http/src/main/scala-3/wvlet/airframe/http/HttpMessageBase.scala:43— airframe-http/src/main/scala-3/wvlet/airframe/http/HttpMessageBase.scala:43-44 | airframe-http/src/main/scala-3/wvlet/airframe/http/HttpServerExceptionBase.scala:45-46 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:73— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:73-74 | airframe-log/.jvm/src/main/scala/wvlet/log/LogEnv.scala:84-88 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) airframe-launcher/src/main/scala-2/wvlet/airframe/launcher/LauncherCompat.scala:31— airframe-launcher/src/main/scala-2/wvlet/airframe/launcher/LauncherCompat.scala:31-35 | airframe-launcher/src/main/scala-3/wvlet/airframe/launcher/LauncherCompat.scala:29-30 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodec.scala:132— airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodec.scala:132-143 | airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodec.scala:146-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/NestedMessagePackBuilder.scala:70— airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/NestedMessagePackBuilder.scala:70-81 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/StreamMessagePackBuilder.scala:73-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/json/StreamMessagePackBuilder.scala:73` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:74— airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:74-85 | airframe-rx/.native/src/main/scala-3/wvlet/airframe/rx/compat.scala:82-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:188— airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:188-199 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:392-403 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:82— airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:82-92 | airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:95-105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:95` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala:75— airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala:75-85 | airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala:118-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala:75` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) airframe-log/.jvm/src/main/scala/wvlet/log/LogEnv.scala:54— airframe-log/.jvm/src/main/scala/wvlet/log/LogEnv.scala:54-64 | airspec/.jvm/src/main/scala/wvlet/airspec/Compat.scala:129-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-log/.jvm/src/main/scala/wvlet/log/LogEnv.scala:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:220— airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:220-230 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:411-421 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) airframe-codec/src/main/scala/wvlet/airframe/codec/CollectionCodec.scala:200— airframe-codec/src/main/scala/wvlet/airframe/codec/CollectionCodec.scala:200-209 | airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:187-196 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-codec/src/main/scala/wvlet/airframe/codec/CollectionCodec.scala:200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:249— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:249-258 | airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala:286-295 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLParser.scala:51— airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLParser.scala:51-60 | airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLParser.scala:73-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:73— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:73-82 | airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/RuntimeeGenericSurface.scala:53-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Off the main sequence: base — base: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: ulid — ulid: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: log — log: abstractness 0.19, instability 0.00, distance 0.81 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: surface — surface: abstractness 0.20, instability 0.09, distance 0.71 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
FixmeComment airframe-surface/src/test/scala/wvlet/airframe/surface/MethodSurfaceTest.scala:129— // FIXME: Fix StaticMethodParameter in CompileTimeSurfaceFactory for Scala 3 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:239— // FIXME: Is this right ? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:914— // FIXME: Use TastyInspector as runtime-like reflection for Scala 3 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) airspec/src/main/scala/wvlet/airspec/spi/RichAsserts.scala:125— airspec/src/main/scala/wvlet/airspec/spi/RichAsserts.scala:125-144 | airspec/src/main/scala/wvlet/airspec/spi/RichAsserts.scala:146-165 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala:12— airframe-core/.js/src/main/scala-3/wvlet/airframe/log/JSConsoleLogHandler.scala:12-31 | airframe-log/.js/src/main/scala/wvlet/log/JSConsoleLogHandler.scala:11-34 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala:135— airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala:135-154 | airframe-http/src/main/scala/wvlet/airframe/http/client/SyncClient.scala:140-164 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×3
Edited copy of a member (17 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:311— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:311-327 | airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala:355-376 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) airframe-metrics/src/main/scala/wvlet/airframe/metrics/Count.scala:47— airframe-metrics/src/main/scala/wvlet/airframe/metrics/Count.scala:47-63 | airframe-metrics/src/main/scala/wvlet/airframe/metrics/DataSize.scala:52-68 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:186— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:186-202 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:215-233 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala:28— airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala:28-36 | airframe-http-okhttp/src/main/scala/wvlet/airframe/http/okhttp/package.scala:80-88 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:236— airframe-core/src/main/scala-3/wvlet/airframe/log/Logger.scala:236-244 | airframe-log/src/main/scala/wvlet/log/Logger.scala:285-297 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/IOUtil.scala:58— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/IOUtil.scala:58-66 | airframe-log/.jvm/src/main/scala/wvlet/log/io/IOUtil.scala:70-82 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:227— airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:227-241 | airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:264-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:261` calls `packAsMap`, `pack` and `airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:224` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) airframe-control/src/main/scala/wvlet/airframe/control/RateLimiter.scala:148— airframe-control/src/main/scala/wvlet/airframe/control/RateLimiter.scala:148-162 | airframe-control/src/main/scala/wvlet/airframe/control/RateLimiter.scala:178-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-control/src/main/scala/wvlet/airframe/control/RateLimiter.scala:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:286— airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:286-300 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClientCalls.scala:53-67 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
RxRunner.run (cyclomatic 133) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:44— RxRunner.run has cyclomatic complexity 133 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (RxRunner.run) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala holds 3 of the 28 methods over the threshold — including the worst — and 242 of the 523 points over it (46%), 4.7× the next-largest file (airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetQueryPlanner.scala at 51). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
RxRunner.run (cyclomatic 133) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:105— RxRunner.run has cyclomatic complexity 133 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (RxRunner.run) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala holds 3 of the 28 methods over the threshold — including the worst — and 242 of the 523 points over it (46%), 4.7× the next-largest file (airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetQueryPlanner.scala at 51). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
RxRunner.run (cognitive 147) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:44— RxRunner.run has cognitive complexity 147 (threshold 15). Drivers by points: match/switch 42 (103 pts), if/else 27 (41 pts), boolean chains 3 (nesting depth added 75). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (RxRunner.run) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala holds 3 of the 38 methods over the threshold — including the worst — and 272 of the 644 points over it (42%), 5.1× the next-largest file (airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala at 53). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
RxRunner.run (cognitive 147) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:105— RxRunner.run has cognitive complexity 147 (threshold 15). Drivers by points: match/switch 42 (103 pts), if/else 27 (41 pts), boolean chains 3 (nesting depth added 75). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (RxRunner.run) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala holds 3 of the 38 methods over the threshold — including the worst — and 272 of the 644 points over it (42%), 5.1× the next-largest file (airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala at 53). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
MethodTooLong: RxRunner.run airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:105— MethodTooLong — run runs 399 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 299 over it, 3.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DOMRenderer.renderToInternal airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:140— MethodTooLong — renderToInternal runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:334— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:334-355 | airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala:382-416 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:216— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:216-237 | airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:78-99 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:94— airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:94-111 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:131-149 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) airspec/src/main/scala/wvlet/airspec/spi/RichAsserts.scala:167— airspec/src/main/scala/wvlet/airspec/spi/RichAsserts.scala:167-184 | airspec/src/main/scala/wvlet/airspec/spi/RichAsserts.scala:186-203 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:185— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:185-205 | airframe-log/.jvm/src/main/scala/wvlet/log/LogLevelScanner.scala:205-231 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLParser.scala:46— airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLParser.scala:46-66 | airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLParser.scala:68-88 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:199— airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:199-210 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClientCalls.scala:34-45 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:151— airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:151-162 | airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:177-188 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×2
Edited copies of one member (3 members, 13+ corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/MetricsCodec.scala:33— airframe-codec/src/main/scala/wvlet/airframe/codec/MetricsCodec.scala:33-45 | airframe-codec/src/main/scala/wvlet/airframe/codec/MetricsCodec.scala:53-65 | airframe-codec/src/main/scala/wvlet/airframe/codec/MetricsCodec.scala:73-85 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) airframe-codec/.jvm/src/main/scala/wvlet/airframe/codec/JDBCCodec.scala:355— airframe-codec/.jvm/src/main/scala/wvlet/airframe/codec/JDBCCodec.scala:355-368 | airframe-codec/.jvm/src/main/scala/wvlet/airframe/codec/JDBCCodec.scala:375-387 | airframe-codec/.jvm/src/main/scala/wvlet/airframe/codec/JDBCCodec.scala:394-406 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×2
Edited copy of a member (3 corresponding lines) airframe-core/src/main/scala-3/wvlet/airframe/log/LogRecord.scala:20— airframe-core/src/main/scala-3/wvlet/airframe/log/LogRecord.scala:20-22 | airframe-log/src/main/scala/wvlet/log/LogRecord.scala:19-23 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:39— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:39-41 | airframe-log/.jvm/src/main/scala/wvlet/log/LogLevelScanner.scala:38-42 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (21 lines × 2) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleServer.scala:385— airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleServer.scala:385-405 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcServerFactory.scala:48-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `createdServers` to `s"Closing FinagleServerFactory") val ex = Seq.newBuilder[Throwable] for (server <-` in one and `s"Closing GrpcServerFactory") val ex = Seq.newBuilder[Throwable] for (server <-` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (21 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:300— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:300-320 | airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:717-737 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:55— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:55-68 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:61-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:188— airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:188-201 | airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:248-261 — before extracting anything, compare `airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala` and `airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:188` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) airframe-http/.js/src/main/scala/wvlet/airframe/http/client/JSFetchChannel.scala:164— airframe-http/.js/src/main/scala/wvlet/airframe/http/client/JSFetchChannel.scala:164-172 | airframe-http/.jvm/src/main/scala/wvlet/airframe/http/client/JavaHttpClientChannel.scala:224-232 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-http/.js/src/main/scala/wvlet/airframe/http/client/JSFetchChannel.scala:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:202— airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:202-210 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:424-432 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:212` calls `isDefinedAt`, `apply` and `airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:434` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
PlanBuilder.buildCondition (cyclomatic 66) airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetQueryPlanner.scala:84— PlanBuilder.buildCondition has cyclomatic complexity 66 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AnyCodec.pack (cyclomatic 43) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:931— AnyCodec.pack has cyclomatic complexity 43 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
MessageFormat.toMessageFormat (cyclomatic 37) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/MessageFormat.scala:93— MessageFormat.toMessageFormat has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SQLGenerator.printRelation (cyclomatic 37) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:158— SQLGenerator.printRelation has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SQLGenerator.printExpression (cyclomatic 37) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:370— SQLGenerator.printExpression has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
HttpRequestMapper.buildControllerMethodArgs (cyclomatic 35) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/router/HttpRequestMapper.scala:37— HttpRequestMapper.buildControllerMethodArgs has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
OpenAPIGenerator.getOpenAPISchemaOfSurface (cyclomatic 33) airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPIGenerator.scala:448— OpenAPIGenerator.getOpenAPISchemaOfSurface has cyclomatic complexity 33 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DOMRenderer.renderToInternal (cyclomatic 33) airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:140— DOMRenderer.renderToInternal has cyclomatic complexity 33 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
JSONScanner.rscan (cyclomatic 31) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:233— JSONScanner.rscan has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TupleCodec.unpack (cyclomatic 25) airframe-codec/src/main/scala/wvlet/airframe/codec/ScalaStandardCodec.scala:59— TupleCodec.unpack has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DOMRenderer.addAttribute (cyclomatic 22) airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:344— DOMRenderer.addAttribute has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CurlChannel.send (cyclomatic 21) airframe-http/.native/src/main/scala/wvlet/airframe/http/client/CurlChannel.scala:46— CurlChannel.send has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CombinedStream.run (cyclomatic 21) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:615— CombinedStream.run has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This file is where this pass's cyclomatic complexity CONCENTRATES: airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala holds 3 of the 28 methods over the threshold — including the worst — and 242 of the 523 points over it (46%), 4.7× the next-largest file (airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetQueryPlanner.scala at 51). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
SQLGenerator.printDDL (cyclomatic 21) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:272— SQLGenerator.printDDL has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: SQLGenerator.printConditionalExpression (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
JSONScanner.scanNumber (cyclomatic 20) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:334— JSONScanner.scanNumber has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OptionParser.parse (cyclomatic 20) airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionParser.scala:187— OptionParser.parse has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OffsetUnpacker.unpackByte (cyclomatic 20) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:198— OffsetUnpacker.unpackByte has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: OffsetUnpacker.skipValue (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
OpenAPIGenerator.buildFromRouter (cyclomatic 19) airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPIGenerator.scala:205— OpenAPIGenerator.buildFromRouter has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HttpLogs.extractRpcArgLog (cyclomatic 18) airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:190— HttpLogs.extractRpcArgLog has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
defaultMessageCodecFinder.findCodec (cyclomatic 17) airframe-codec/src/main/scala/wvlet/airframe/codec/MessageCodecFinder.scala:74— defaultMessageCodecFinder.findCodec has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
YamlReader.pack (cyclomatic 17) airframe-config/src/main/scala/wvlet/airframe/config/YamlReader.scala:110— YamlReader.pack has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
OffsetUnpacker.unpackShort (cyclomatic 17) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:240— OffsetUnpacker.unpackShort has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: OffsetUnpacker.skipValue (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
ParquetObjectWriter.packValue (cyclomatic 17) airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:185— ParquetObjectWriter.packValue has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Attribute.matched (cyclomatic 17) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:367— Attribute.matched has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AirSpecTaskRunner.runSingle (cyclomatic 17) airspec/src/main/scala/wvlet/airspec/runner/AirSpecTaskRunner.scala:212— AirSpecTaskRunner.runSingle has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FinagleResponseHandler.toHttpResponse (cyclomatic 16) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleResponseHandler.scala:86— FinagleResponseHandler.toHttpResponse has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
HttpRequestMapper.buildControllerMethodArgs (cognitive 57) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/router/HttpRequestMapper.scala:37— HttpRequestMapper.buildControllerMethodArgs has cognitive complexity 57 (threshold 15). Drivers by points: match/switch 10 (24 pts), if/else 13 (20 pts), loops 3 (6 pts), error handling 2 (4 pts), boolean chains 3 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JSONScanner.rscan (cognitive 49) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:233— JSONScanner.rscan has cognitive complexity 49 (threshold 15). Drivers by points: if/else 31 (41 pts), boolean chains 8 (nesting depth added 10). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DOMRenderer.addAttribute (cognitive 46) airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:344— DOMRenderer.addAttribute has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (29 pts), match/switch 6 (13 pts), boolean chains 4 (nesting depth added 22). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
StandardBuilder.set (cognitive 40) airframe-surface/.jvm/src/main/scala/wvlet/airframe/surface/reflect/ObjectBuilder.scala:126— StandardBuilder.set has cognitive complexity 40 (threshold 15). Drivers by points: match/switch 4 (21 pts), if/else 13 (19 pts) (nesting depth added 23). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DOMRenderer.renderToInternal (cognitive 37) airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:140— DOMRenderer.renderToInternal has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (21 pts), match/switch 5 (14 pts), loops 1 (2 pts) (nesting depth added 22). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
OpenAPIGenerator.buildFromRouter (cognitive 33) airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPIGenerator.scala:205— OpenAPIGenerator.buildFromRouter has cognitive complexity 33 (threshold 15). Drivers by points: if/else 25 (27 pts), boolean chains 3, match/switch 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OptionParser.parse (cognitive 31) airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionParser.scala:187— OptionParser.parse has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (21 pts), match/switch 4 (7 pts), loops 2, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JSONScanner.scanNumber (cognitive 30) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:334— JSONScanner.scanNumber has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 3 (8 pts), boolean chains 7 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Attribute.matched (cognitive 29) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:367— Attribute.matched has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (20 pts), match/switch 5 (9 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SQLInterpreter.visitPredicated (cognitive 29) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:558— SQLInterpreter.visitPredicated has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (27 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypeConverter.convert (cognitive 27) airframe-surface/.jvm/src/main/scala/wvlet/airframe/surface/reflect/TypeConverter.scala:34— TypeConverter.convert has cognitive complexity 27 (threshold 15). Drivers by points: if/else 18 (26 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CName.toNaturalName (cognitive 27) airframe-surface/src/main/scala/wvlet/airframe/surface/CName.scala:64— CName.toNaturalName has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParamListCodec.unpack (cognitive 26) airframe-codec/src/main/scala/wvlet/airframe/codec/ObjectCodec.scala:120— ParamListCodec.unpack has cognitive complexity 26 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 4 (9 pts), match/switch 2 (4 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PlanBuilder.buildCondition (cognitive 26) airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetQueryPlanner.scala:84— PlanBuilder.buildCondition has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 9 (17 pts), if/else 9 (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CompileTimeSurfaceFactory.surfaceOf (cognitive 25) airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:75— CompileTimeSurfaceFactory.surfaceOf has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (20 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AirSpecTaskRunner.runSingle (cognitive 25) airspec/src/main/scala/wvlet/airspec/runner/AirSpecTaskRunner.scala:212— AirSpecTaskRunner.runSingle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 6 (11 pts), error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RouteMatcher.buildPathDFA (cognitive 23) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/router/RouteMatcher.scala:195— RouteMatcher.buildPathDFA has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 2 (5 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParquetObjectWriter.packValue (cognitive 23) airframe-parquet/src/main/scala/wvlet/airframe/parquet/ParquetObjectWriter.scala:185— ParquetObjectWriter.packValue has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 2 (5 pts), loops 2 (5 pts), match/switch 3 (4 pts), boolean chains 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CombinedStream.run (cognitive 23) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:615— CombinedStream.run has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 4 (6 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala holds 3 of the 38 methods over the threshold — including the worst — and 272 of the 644 points over it (42%), 5.1× the next-largest file (airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala at 53). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
CommandLauncher.execute (cognitive 22) airframe-launcher/src/main/scala/wvlet/airframe/launcher/Launcher.scala:256— CommandLauncher.execute has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 2 (6 pts), match/switch 2 (4 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
TimeWindowBuilder.parseOffset (cognitive 22) airframe-metrics/.jvm/src/main/scala/wvlet/airframe/metrics/TimeWindow.scala:194— TimeWindowBuilder.parseOffset has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 3 (6 pts) (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CompileTimeSurfaceFactory.methodParametersOf (cognitive 21) airframe-surface/src/main/scala-3/wvlet/airframe/surface/CompileTimeSurfaceFactory.scala:575— CompileTimeSurfaceFactory.methodParametersOf has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 4 (9 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SQLGenerator.printDDL (cognitive 20) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:272— SQLGenerator.printDDL has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SQLInterpreter.visitQuerySpecification (cognitive 20) airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala:205— SQLInterpreter.visitQuerySpecification has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CurlChannel.send (cognitive 19) airframe-http/.native/src/main/scala/wvlet/airframe/http/client/CurlChannel.scala:46— CurlChannel.send has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, loops 2 (3 pts), match/switch 2 (3 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OffsetUnpacker.unpackByte (cognitive 19) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:198— OffsetUnpacker.unpackByte has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AnyCodec.pack (cognitive 18) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:931— AnyCodec.pack has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (8 pts), loops 3 (6 pts), if/else 3 (4 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ServerAddress.apply (cognitive 18) airframe-http/src/main/scala/wvlet/airframe/http/ServerAddress.scala:62— ServerAddress.apply has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), match/switch 3 (8 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LogicalPlanPrinter.print (cognitive 18) airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlanPrinter.scala:34— LogicalPlanPrinter.print has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 3 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
EitherCodec.unpack (cognitive 17) airframe-codec/src/main/scala/wvlet/airframe/codec/ScalaStandardCodec.scala:231— EitherCodec.unpack has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (4 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CommandLineTokenizer.parse (cognitive 17) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/CommandLineTokenizer.scala:31— CommandLineTokenizer.parse has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (11 pts), if/else 4, boolean chains 1, loops 1 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Shell.findJavaCommand (cognitive 17) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:298— Shell.findJavaCommand has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (4 pts), boolean chains 2 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
FinagleResponseHandler.toHttpResponse (cognitive 17) airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleResponseHandler.scala:86— FinagleResponseHandler.toHttpResponse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 4 (8 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
JSFetchChannel.readStream (cognitive 17) airframe-http/.js/src/main/scala/wvlet/airframe/http/client/JSFetchChannel.scala:126— JSFetchChannel.readStream has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 3 (5 pts), error handling 1 (3 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HttpClientIR.buildIR (cognitive 16) airframe-http-codegen/src/main/scala/wvlet/airframe/http/codegen/HttpClientIR.scala:283— HttpClientIR.buildIR has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OffsetPacker.packLong (cognitive 16) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetPacker.scala:146— OffsetPacker.packLong has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling: SQLGenerator.scala ↔ SQLInterpreter.scala airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala:1— `airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala` and `airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLInterpreter.scala` change together 63% of the time (40 of the 63 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 40 shared commits counted here, the most recent 3 are `83068b70` sql (fix): Support special date and time functions (#3921); `329a259e` sql (fix): Support lambda expression (#3926); `1cedd82b` airframe-sql (fix): Resolve columns from CTE inside AliasedRelation (… — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:97— airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:97-130 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:140-177 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:186-219 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:228-261 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:271-303 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:317-349 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:363-395 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Edited copy of a member (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:166— airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:166-226 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:231-309 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) airframe-core/.native/src/main/scala-3/wvlet/airframe/log/LogTimestampFormatter.scala:35— airframe-core/.native/src/main/scala-3/wvlet/airframe/log/LogTimestampFormatter.scala:35-79 | airframe-log/.native/src/main/scala/wvlet/log/LogTimestampFormatter.scala:35-83 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Parallel.scala:72— airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Parallel.scala:72-119 | airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Parallel.scala:137-190 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:236— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:236-268 | airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala:268-310 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:96— airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:96-135 | airframe-log/.jvm/src/main/scala/wvlet/log/LogLevelScanner.scala:103-152 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:318— airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:318-356 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:358-399 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 37+ corresponding lines) · ×1
Edited copies of one member (3 members, 37+ corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:198— airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:198-238 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:240-278 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:280-316 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala:59— airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala:59-87 | airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionSchema.scala:101-130 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:115— airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:115-149 | airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:263-305 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala:49— airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala:49-84 | airframe-http/src/main/scala/wvlet/airframe/http/client/SyncClient.scala:50-85 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:456— airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:456-488 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:497-524 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:534-561 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:60— airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:60-92 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:216-241 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:735— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:735-754 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:763-784 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:864-885 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:896-919 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 26+ corresponding lines) · ×1
Edited copies of one member (4 members, 26+ corresponding lines) airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:108— airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:108-143 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/Expression.scala:150-185 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:249-274 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:317-348 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) airframe-core-base/src/main/scala-3/wvlet/airframe/log/LoggerMacros.scala:22— airframe-core-base/src/main/scala-3/wvlet/airframe/log/LoggerMacros.scala:22-29 | airframe-di-macros/src/main/scala-3/wvlet/airframe/SourceCode.scala:37-45 | airframe-log/src/main/scala-3/wvlet/log/LoggerBase.scala:97-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) airframe-http/src/main/scala/wvlet/airframe/http/client/HttpClients.scala:231— airframe-http/src/main/scala/wvlet/airframe/http/client/HttpClients.scala:231-256 | airframe-http/src/main/scala/wvlet/airframe/http/client/HttpClients.scala:287-309 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 17+ corresponding lines) · ×1
Edited copies of one member (6 members, 17+ corresponding lines) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:598— airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:598-615 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:626-648 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:659-681 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:692-709 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:720-737 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:748-764 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:408— airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:408-416 | airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:418-428 | airframe-json/src/main/scala/wvlet/airframe/json/JSONScanner.scala:430-438 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:472— airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:472-490 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/OffsetUnpacker.scala:492-510 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 19+ corresponding lines) · ×1
Edited copies of one member (4 members, 19+ corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:937— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:937-955 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:957-977 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:979-1001 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:1003-1027 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) airframe-control/src/main/scala/wvlet/airframe/control/IO.scala:37— airframe-control/src/main/scala/wvlet/airframe/control/IO.scala:37-57 | airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/IOUtil.scala:72-83 | airframe-log/.jvm/src/main/scala/wvlet/log/io/IOUtil.scala:88-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:308— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:308-316 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:325-334 | airspec/src/main/scala-2/wvlet/airspec/AirSpecMacros.scala:75-90 | airspec/src/main/scala-2/wvlet/airspec/AirSpecMacros.scala:101-118 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:72— airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:72-79 | airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:86-97 | airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:137-144 | airframe-di/src/main/scala-3/wvlet/airframe/BinderImpl.scala:151-162 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (25–26 lines × 2) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:167— airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:167-192 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:233-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–20 lines × 2) airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala:64— airframe-http/src/main/scala/wvlet/airframe/http/client/AsyncClient.scala:64-83 | airframe-http/src/main/scala/wvlet/airframe/http/client/SyncClient.scala:66-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 2) airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:75— airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:75-92 | airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:224-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-sql/src/main/scala/wvlet/airframe/sql/model/LogicalPlan.scala:75` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:125— airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:125-141 | airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:274-289 — before extracting anything, compare `airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala` and `airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:125` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:597— airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:597-613 | airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala:615-631 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15–16 lines × 2) airframe-http/src/main/scala-2/wvlet/airframe/http/RxRouterMacros.scala:33— airframe-http/src/main/scala-2/wvlet/airframe/http/RxRouterMacros.scala:33-47 | airframe-http/src/main/scala-2/wvlet/airframe/http/RxRouterMacros.scala:59-74 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14–15 lines × 7) airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:101— airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:101-115 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:144-158 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:190-204 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:232-246 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:275-288 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:321-334 | airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:367-380 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:101` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:116` calls `read` and `airframe-codec/src/main/scala/wvlet/airframe/codec/PrimitiveCodec.scala:159` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6–15 lines × 2) airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:644— airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:644-649 | airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:651-665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-rx/src/main/scala/wvlet/airframe/rx/RxRunner.scala:644` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) airframe-control/src/main/scala/wvlet/airframe/control/IO.scala:42— airframe-control/src/main/scala/wvlet/airframe/control/IO.scala:42-54 | airframe-log/.jvm/src/main/scala/wvlet/log/io/IOUtil.scala:90-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-log/.jvm/src/main/scala/wvlet/log/io/IOUtil.scala:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:175— airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:175-187 | airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:225-237 — before extracting anything, compare `airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala` and `airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) airframe-control/.jvm/src/main/scala/wvlet/airframe/control/ThreadUtil.scala:27— airframe-control/.jvm/src/main/scala/wvlet/airframe/control/ThreadUtil.scala:27-37 | airspec/.jvm/src/main/scala/wvlet/airspec/Compat.scala:47-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 3) airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcException.scala:42— airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcException.scala:42-52 | airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/internal/GrpcRequestHandler.scala:106-116 | airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:120-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8–9 lines × 2) airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:94— airframe-core/src/main/scala-3/wvlet/airframe/log/LogFormat.scala:94-102 | airframe-log/src/main/scala/wvlet/log/LogFormat.scala:107-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–7 lines × 3) airframe-core-base/src/main/scala-3/wvlet/airframe/log/LoggerMacros.scala:22— airframe-core-base/src/main/scala-3/wvlet/airframe/log/LoggerMacros.scala:22-27 | airframe-di-macros/src/main/scala-3/wvlet/airframe/SourceCode.scala:37-43 | airframe-log/src/main/scala-3/wvlet/log/LoggerBase.scala:98-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (4–6 lines × 3) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:329— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:329-334 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:767-770 | airspec/src/main/scala-2/wvlet/airspec/AirSpecMacros.scala:104-118 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:329` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–7 lines × 2) airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:91— airframe-rx/.jvm/src/main/scala/wvlet/airframe/rx/compat.scala:91-96 | airframe-rx/.native/src/main/scala-3/wvlet/airframe/rx/compat.scala:98-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (4–5 lines × 6) airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:311— airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:311-314 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:739-742 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:767-770 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:842-846 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:865-869 | airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:897-901 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 2) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:182— airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:182-187 | airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/io/ByteArrayBuffer.scala:193-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (51 lines × 2) airframe-di/src/main/scala/wvlet/airframe/LazyF0.scala:17— airframe-di/src/main/scala/wvlet/airframe/LazyF0.scala:17-67 | airframe-rx/src/main/scala/wvlet/airframe/rx/LazyF0.scala:20-70 — before extracting anything, compare `airframe-di/src/main/scala/wvlet/airframe/LazyF0.scala` and `airframe-rx/src/main/scala/wvlet/airframe/rx/LazyF0.scala` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `airframe-di/src/main/scala/wvlet/airframe/LazyF0.scala:17` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) airframe-http/.jvm/src/main/scala/wvlet/airframe/http/internal/LocalRPCContext.scala:22— airframe-http/.jvm/src/main/scala/wvlet/airframe/http/internal/LocalRPCContext.scala:22-41 | airframe-http/.native/src/main/scala/wvlet/airframe/http/internal/LocalRPCContext.scala:27-47 — before extracting anything, compare `airframe-http/.jvm/src/main/scala/wvlet/airframe/http/internal/LocalRPCContext.scala` and `airframe-http/.native/src/main/scala/wvlet/airframe/http/internal/LocalRPCContext.scala` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) airframe-core/.js/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:15— airframe-core/.js/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:15-22 | airframe-core/.native/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:35-41 | airspec/.native/src/main/scala-3/wvlet/airspec/Compat.scala:82-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (10 lines × 3) airframe-log/.js/src/main/scala/wvlet/log/LogEnv.scala:14— airframe-log/.js/src/main/scala/wvlet/log/LogEnv.scala:14-24 | airframe-log/.native/src/main/scala/wvlet/log/LogEnv.scala:34-43 | airspec/.js/src/main/scala/wvlet/airspec/Compat.scala:86-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap airframe-json/src/main/scala/wvlet/airframe/json/JSONTraverser.scala:44— `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.
Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:354— `!Modifier.isAbstract(cl.getModifiers) && toSearch.isAssignableFrom(cl)` appears character-identically in 2 files — airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala, airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:579— `!isAbstract(t) && findPrimaryConstructorOf(t).exists(!_.paramLists.isEmpty)` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:233— `!x.isAccessor && !name.startsWith("$") && name != "<init>"` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:247— `!x.isImplementationArtifact && !x.isSynthetic && x.fullName != "scala.Any" && x.fullName != "java.lang.Object"` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:224— `digits.isNaN || digits.isInfinity || digits >= -2.0` appears character-identically in 2 files — airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala, airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala:58— `interfaces != null && interfaces.length > 0` appears character-identically in 4 files — airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogEnv.scala, airframe-jmx/src/main/scala/wvlet/airframe/jmx/JMXRegistry.scala, airframe-log/.jvm/src/main/scala/wvlet/log/LogEnv.scala, airspec/.jvm/src/main/scala/wvlet/airspec/Compat.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:113— `lastScannedMillis.isEmpty || lastScannedMillis.get < lastModified` appears character-identically in 2 files — airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala, airframe-log/.jvm/src/main/scala/wvlet/log/LogLevelScanner.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala:189— `lastScheduledMillis.isEmpty || currentTimeMillis - lastScheduledMillis.get > scanIntervalMillis` appears character-identically in 2 files — airframe-core/.jvm/src/main/scala-3/wvlet/airframe/log/LogLevelScanner.scala, airframe-log/.jvm/src/main/scala/wvlet/log/LogLevelScanner.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala:264— `logicalName != null && resourceFilter(logicalName)` appears character-identically in 2 files — airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/Resource.scala, airframe-log/.jvm/src/main/scala/wvlet/log/io/Resource.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:500— `m.isMethod && m.asMethod.isConstructor && m.isPublic` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:255— `m.owner == t.typeSymbol || t.baseClasses .filter(nonObject) .exists(_ == m.owner)` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:220— `nonObject(x.owner) && x.isMethod && x.isPublic && !x.isConstructor && !x.isImplementationArtifact && !x.isMacro && !x.isImplicit && !x.isSyn…` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:601— `s.isMethod && s.asMethod.paramLists.size == 1` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-http-codegen/src/main/scala/wvlet/airframe/http/codegen/HttpClientIR.scala:319— `s.isPrimitive || (s.isOption && s.typeArgs.forall(_.isPrimitive))` appears character-identically in 2 files — airframe-http-codegen/src/main/scala/wvlet/airframe/http/codegen/HttpClientIR.scala, airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPIGenerator.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:119— `symbol.isType && symbol.asType.isAliasType && !belongsToScalaDefault(alias)` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:116— `t.typeArgs.length == 2 && isTaggedType(t)` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala:200— `t.typeSymbol.isAbstract && hasAbstractMethods(t)` appears character-identically in 2 files — airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala:229— `unitIndex >= 0 && (unitIndex < symbol.length)` appears character-identically in 2 files — airframe-core/.jvm/src/main/scala-3/wvlet/airframe/io/StopWatch.scala, airframe-log/src/main/scala/wvlet/log/io/StopWatch.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-http/src/main/scala/wvlet/airframe/http/HttpMessage.scala:135— `x == HttpHeader.MediaType.ApplicationJson || x.startsWith("application/json")` appears character-identically in 2 files — airframe-http/src/main/scala/wvlet/airframe/http/HttpMessage.scala, airframe-http/src/main/scala/wvlet/airframe/http/HttpServerException.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala:32— `x.isMethod && x.isAbstract && !x.isAbstractOverride` appears character-identically in 3 files — airframe-di-macros/src/main/scala-2/wvlet/airframe/AirframeMacros.scala, airframe-surface/.jvm/src/main/scala-2/wvlet/airframe/surface/reflect/ReflectSurfaceFactory.scala, airframe-surface/src/main/scala-2/wvlet/airframe/surface/SurfaceMacros.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Fat interface: Packer (21 abstract members) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/Packer.scala:22— `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.
Fat interface: Unpacker (28 abstract members) airframe-msgpack/src/main/scala/wvlet/airframe/msgpack/spi/Unpacker.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.
D21 · Naming Consistency· `extractRpcArgLog` spells `Rpc` where 36 names in the project spell it `RPC` · ×2
`extractRpcArgLog` spells `Rpc` where 36 names in the project spell it `RPC` airframe-http/.jvm/src/main/scala/wvlet/airframe/http/HttpAccessLogWriter.scala:164— 36 of 38 names in project repository spell the token `RPC` (36 of 38; unit: names in project repository containing `RPC`). Peers: wvlet.airframe.benchmark.rpc_netty.AirframeRPCNetty (airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/rpc_netty/RPCNetty.scala:30); RPCRequestBenchmark.rpcRequestWithRPCMethod (airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/rpc_request/RPCRequestBenchmark.scala:88); wvlet.airframe.http.finagle.FinagleRPCContext (airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleRPCContext.scala:22); GrpcClient.prepareRPCRequestBody (airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:43); wvlet.airframe.http.grpc.gRPC (airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/gRPC.scala:22). Rename to `extractRPCArgLog`. [rule N6]
`extractRpcArgLog` spells `Rpc` where 36 names in the project spell it `RPC` airframe-http/src/main/scala/wvlet/airframe/http/internal/HttpLogs.scala:190— 36 of 38 names in project repository spell the token `RPC` (36 of 38; unit: names in project repository containing `RPC`). Peers: wvlet.airframe.benchmark.rpc_netty.AirframeRPCNetty (airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/rpc_netty/RPCNetty.scala:30); RPCRequestBenchmark.rpcRequestWithRPCMethod (airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/rpc_request/RPCRequestBenchmark.scala:88); wvlet.airframe.http.finagle.FinagleRPCContext (airframe-http-finagle/src/main/scala/wvlet/airframe/http/finagle/FinagleRPCContext.scala:22); GrpcClient.prepareRPCRequestBody (airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/GrpcClient.scala:43); wvlet.airframe.http.grpc.gRPC (airframe-http-grpc/src/main/scala/wvlet/airframe/http/grpc/gRPC.scala:22). Rename to `extractRPCArgLog`. [rule N6]
README/code drift airframe-jmx/README.md:11— 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.
README/code drift airframe-log/README.md:293— 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 14 significant file(s) lose their only recent owner: airframe-http-netty/src/main/scala/wvlet/airframe/http/netty/NettyServer.scala, airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPIGenerator.scala, airframe-http-netty/src/main/scala/wvlet/airframe/http/netty/NettyRequestHandler.scala, airframe-http/src/main/scala/wvlet/airframe/http/HttpMessage.scala, airframe-http-codegen/src/main/scala/wvlet/airframe/http/codegen/HttpClientIR.scala, airframe-http/src/main/scala/wvlet/airframe/http/client/HttpClients.scala, airframe-log/src/main/scala/wvlet/log/LogFormat.scala, airframe-http/src/main/scala/wvlet/airframe/http/HttpLogger.scala (+6 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (15 single-owned of 219 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 219 of the 429 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: airframe-sql/src/main/scala/wvlet/airframe/sql/parser/SQLGenerator.scala.
D21 · Naming Consistency· `getProcessIDOfCurrentJVM` spells `ID` where 64 names in the project spell it `Id` · ×1
`getProcessIDOfCurrentJVM` spells `ID` where 64 names in the project spell it `Id` airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:122— 64 of 66 names in project repository spell the token `Id` (64 of 66; unit: names in project repository containing `Id`). Peers: AirframeSession.sessionId (airframe-di/src/main/scala/wvlet/airframe/AirframeSession.scala:107); Session.sessionId (airframe-di/src/main/scala/wvlet/airframe/Session.scala:36); JMXUtil.getProcessId (airframe-jmx/src/main/scala/wvlet/airframe/jmx/JMXUtil.scala:124); TimeWindow.withTimeZone(zoneId) (airframe-metrics/.jvm/src/main/scala/wvlet/airframe/metrics/TimeWindow.scala:152); DOMRenderer.renderToNode(nodeId) (airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:42). Rename to `getProcessIdOfCurrentJVM`. [rule N6]
D21 · Naming Consistency· `getProcessID` spells `ID` where 64 names in the project spell it `Id` · ×1
`getProcessID` spells `ID` where 64 names in the project spell it `Id` airframe-control/.jvm/src/main/scala/wvlet/airframe/control/Shell.scala:135— 64 of 66 names in project repository spell the token `Id` (64 of 66; unit: names in project repository containing `Id`). Peers: AirframeSession.sessionId (airframe-di/src/main/scala/wvlet/airframe/AirframeSession.scala:107); Session.sessionId (airframe-di/src/main/scala/wvlet/airframe/Session.scala:36); JMXUtil.getProcessId (airframe-jmx/src/main/scala/wvlet/airframe/jmx/JMXUtil.scala:124); TimeWindow.withTimeZone(zoneId) (airframe-metrics/.jvm/src/main/scala/wvlet/airframe/metrics/TimeWindow.scala:152); DOMRenderer.renderToNode(nodeId) (airframe-rx-html/.js/src/main/scala/wvlet/airframe/rx/html/DOMRenderer.scala:42). Rename to `getProcessId`. [rule N6]
D21 · Naming Consistency· `toYAML` spells `YAML` where 23 names in the project spell it `Yaml` · ×1
`toYAML` spells `YAML` where 23 names in the project spell it `Yaml` airframe-http-codegen/src/main/scala/wvlet/airframe/http/openapi/OpenAPI.scala:42— 23 of 24 names in project repository spell the token `Yaml` (23 of 24; unit: names in project repository containing `Yaml`). Peers: ConfigPackageCompat.bindConfigFromYaml (airframe-config/src/main/scala-2/wvlet/airframe/config/ConfigCompat.scala:26); ConfigPackageCompat.bindConfigFromYaml (airframe-config/src/main/scala-2/wvlet/airframe/config/ConfigCompat.scala:29); ConfigCompat.registerFromYaml (airframe-config/src/main/scala-2/wvlet/airframe/config/ConfigCompat.scala:65); ConfigCompat.registerFromYamlOrElse (airframe-config/src/main/scala-2/wvlet/airframe/config/ConfigCompat.scala:69); ConfigPackageCompat.bindConfigFromYaml (airframe-config/src/main/scala-3/wvlet/airframe/config/ConfigCompat.scala:24). Rename to `toYaml`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 4 project(s) overshoot their size bounds, lowering Project Cohesion to 5.0/10. The most over is `(repository root)` (55977 LoC, 2247 module-visible types across 153 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
No ADRs — 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.
No SAST REDACTED:3— 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 15 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.
P3 · Security & performance tooling· Dependabot does not watch npm · ×1
Dependabot does not watch npm REDACTED:4— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
Benchmarks don't track allocations airframe-benchmark/src/main/scala/wvlet/airframe/benchmark/ulid/ULIDBenchmark.scala— 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.
No security response headers detected — 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`.
Secure cookie flags not detected — 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.)
X5 · Nullable reference types· Scala's null is not held to the type system everywhere · ×1
Scala's null is not held to the type system everywhere — 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.
Silent fallback default in catch airframe-surface/.jvm/src/main/scala/wvlet/airframe/surface/reflect/package.scala:82— `annotations` swallows every exception into `Array.empty` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch case or in the Scaladoc, and the row stops firing.
Subsumed condition operand airframe-launcher/src/main/scala/wvlet/airframe/launcher/OptionParser.scala:48— `p.startsWith("--")` can never decide this `||` — every value satisfying `p.startsWith("--")` also satisfies `p.startsWith("-")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Outdated: ch.qos.logback:logback-core — `ch.qos.logback %% logback-core` is declared at 1.5.8 in REDACTED, but 1.6.6 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.5.8 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: commons-collections:commons-collections — `commons-collections %% commons-collections` is declared at 3.2.2 in REDACTED, but 20040616 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.2.2 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: io.netty:netty-all — `io.netty %% netty-all` is declared at 4.2.19.Final in REDACTED, but 4.2.20.Final is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 4.2.19.Final until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.apache.hadoop.thirdparty:hadoop-shaded-guava — `org.apache.hadoop.thirdparty %% hadoop-shaded-guava` is declared at 1.5.0 in REDACTED, but 1.6.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.5.0 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.apache.parquet:parquet-hadoop — `org.apache.parquet %% parquet-hadoop` is declared at 1.18.1 in REDACTED, but 1.18.2 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.18.1 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.duckdb:duckdb_jdbc — `org.duckdb %% duckdb_jdbc` is declared at 2.0.0.0 in REDACTED, but 2.0.0.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.0.0.0 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.scala-lang.modules:scala-parallel-collections_2.13 — `org.scala-lang.modules %% scala-parallel-collections_2.13` is declared at 0.2.0 in REDACTED, but 1.3.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.2.0 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.xerial:sqlite-jdbc — `org.xerial %% sqlite-jdbc` is declared at 3.53.4.0 in REDACTED, but 3.54.1.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.53.4.0 until the declaration is edited — there is no lockfile refresh that would move it.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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.
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.
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.
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.
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.
Run 01a1da93-ae44-74cd-bdb4-de1b9a54a46f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 91 · Warnings: 360 · Recommendations: 43 · Info: 8 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 15:01 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.