Public report of twitter/finagle, 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, 06:48 UTC · Survey ID cd_35ac46d3761948e6bd970864390a227a
twitter/finagle
Measured 14 November 2026, 06:47 UTC, at code version ca472de
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt riskDown 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 large codebase: 112,827 lines of product code in 33 projects, tests not counted · Estimated rebuild effort: about 1.7 person-years · Weakest lens: Code Health, 57
Findings by how serious they are
20 critical351 serious568 minor
9 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, 06:47 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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.
928of 939 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
55dimensions across 6 lenses, read from 112,827 lines of product code in 33 projects.
twitter/finagle is rated At risk because critical security findings are open. It scores 66 out of 100, which the At risk rating leaves unchanged.
Code Health, at 57, is the weakest lens and counts most in the score. The best first step is declaring which values may be missing, worth about 6 points. Handling the errors the code catches and ignores comes next, worth about 5 points. Raising Code Health to 70 would lift the score to about 71.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven known security holes in the packages the code depends on can be used by attackers, and three weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, updating the vulnerable packages and fixing the weaknesses the scanner points to would close these risks. The two passwords or keys in the code's history need replacing, with the old ones switched off.
The product code is 112,827 lines, about €250,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.
If Code Health rose from 57 to 70, the lowest score rated Strong, the score would rise from 66 to about 71.
Code composition: what the lines of code are
Product code 54%Tests 46%
New since the last survey: 82 findings
These 82 critical or serious findings weren't in the previous survey, on 26 October 2026.
Code Duplication · Edited copy of a member (51 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/liveness/FailureAccrualFactory.scala
Code Duplication · Edited copy of a member (26 corresponding lines) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala
Code Duplication · Edited copy of a member (46 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala
Code Duplication · Edited copy of a member (29 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/service/ExpiringService.scala
Code Duplication · Edited copy of a member (48 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftUtil.scala
Code Duplication · Edited copy of a member (39 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala
Code Duplication · Edited copy of a member (27 corresponding lines) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java
Code Duplication · Edited copy of a member (30 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/service/TimeoutFilter.scala
Code Duplication · Edited copy of a member (28 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/filter/NackAdmissionFilter.scala
Code Duplication · Edited copy of a member (23 corresponding lines) finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/Negotiation.scala
Code Duplication · Edited copies of one member (5 members, 23+ corresponding lines) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala
Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala
Code Duplication · Edited copy of a member (12 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Filter.scala
Code Duplication · Edited copy of a member (17 corresponding lines) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/AbstractByteBufByteReader.scala
Code Duplication · Edited copies of one member (4 members, 18+ corresponding lines) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java
Code Duplication · Edited copy of a member (10 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Filter.scala
Code Duplication · Edited copy of a member (18 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/filter/RequestLogger.scala
Code Duplication · Edited copy of a member (17 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/client/StdStackClient.scala
Code Duplication · Edited copy of a member (14 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/filter/ClearBroadcastContextFilter.scala
Code Duplication · Edited copy of a member (17 corresponding lines) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala
Code Duplication · Edited copy of a member (13 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Filter.scala
Code Duplication · Edited copy of a member (6 corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Streams.scala
Code Duplication · Edited copy of a member (15 corresponding lines) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala
Code Duplication · Edited copy of a member (27 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/ThriftCustomPartitioningService.scala
Code Duplication · Edited copy of a member (20 corresponding lines) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Bijections.scala
Code Duplication · Edited copy of a member (22 corresponding lines) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4HttpCodec.scala
Code Duplication · Edited copy of a member (19 corresponding lines) finagle-http/src/main/scala/com/twitter/finagle/http/KerberosAuthenticationFilter.scala
Code Duplication · Edited copy of a member (14 corresponding lines) finagle-http/src/main/scala/com/twitter/finagle/http/filter/StatsFilter.scala
Code Duplication · Edited copy of a member (16 corresponding lines) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java
Code Duplication · Edited copy of a member (12 corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MemcachedTracingFilter.scala
Code Duplication · Edited copy of a member (12 corresponding lines) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala
Code Duplication · Edited copy of a member (17 corresponding lines) finagle-exp/src/main/scala/com/twitter/finagle/exp/fiber_scheduler/util/Optimizer.scala
Code Duplication · Edited copy of a member (14 corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/protocol/text/Framer.scala
Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/LeastLoaded.scala
Code Duplication · Edited copy of a member (15 corresponding lines) finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/HttpRouter.scala
Code Duplication · Edited copy of a member (7 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Stack.scala
Code Duplication · Edited copy of a member (15 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/dispatch/ClientDispatcher.scala
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala
Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala
Code Duplication · Edited copy of a member (14 corresponding lines) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PasswordUtils.scala
Code Duplication · Edited copy of a member (9 corresponding lines) finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/ClientTraceContextFilter.scala
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftRichClient.scala
Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/factory/StatsFactoryWrapper.scala
Code Duplication · Edited copy of a member (11 corresponding lines) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala
Code Duplication · Edited copy of a member (9 corresponding lines) finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueReads.scala
Code Duplication · Edited copy of a member (11 corresponding lines) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala
Code Duplication · Edited copy of a member (10 corresponding lines) finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/StackClientOps.scala
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala
Code Duplication · Edited copy of a member (12 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/stats/JavaLoggerStatsReceiver.scala
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Stack.scala
Code Duplication · Edited copy of a member (15 corresponding lines) finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/MuxChannelHandle.scala
Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) finagle-http/src/main/scala/com/twitter/finagle/http/service/RoutingService.scala
Code Duplication · Edited copy of a member (14 corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/exp/SubscribeClient.scala
Code Duplication · Edited copy of a member (14 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/NameTreeParsers.scala
Code Duplication · Edited copy of a member (7 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/addr/WeightedAddress.scala
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/Thrift.scala
Code Duplication · Edited copy of a member (10 corresponding lines) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala
Code Duplication · Edited copy of a member (10 corresponding lines) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala
Code Duplication · Edited copy of a member (11 corresponding lines) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4StreamTransport.scala
Code Duplication · Edited copy of a member (11 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftReqRepServicePerEndpoint.scala
Code Duplication · Edited copy of a member (9 corresponding lines) finagle-base-http/src/main/scala/com/twitter/finagle/http/DelayedReleaseService.scala
Code Duplication · Edited copy of a member (9 corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/TwemcacheCacheClient.scala
Code Duplication · Edited copy of a member (9 corresponding lines) finagle-stats-core/src/main/scala/com/twitter/finagle/stats/JsonExporter.scala
Code Duplication · Edited copy of a member (10 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/MultiplexedService.scala
Code Duplication · Edited copy of a member (7 corresponding lines) finagle-http/src/main/scala/com/twitter/finagle/http/MethodBuilder.scala
Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/client/ExportSslUsageModule.scala
Code Duplication · Edited copy of a member (11 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/aperture/RandomAperture.scala
Code Duplication · Edited copy of a member (7 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Announcer.scala
Code Duplication · Edited copy of a member (18 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/ssl/client/SslContextClientEngineFactory.scala
Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/client/StackClient.scala
Code Duplication · Edited copy of a member (12 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/ssl/client/JdkClientEngineFactory.scala
Code Duplication · Edited copy of a member (9 corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala
Code Duplication · Edited copy of a member (7 corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/Client.scala
Code Duplication · Edited copy of a member (4 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/service/RetryFilter.scala
Code Duplication · Edited copy of a member (7 corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala
Code Duplication · Edited copy of a member (4 corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/BtreeSortedSetCommands.scala
Code Duplication · Edited copies of one member (5 members, 4+ corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/HashCommands.scala
Code Duplication · Edited copy of a member (3 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/builder/ClientBuilder.scala
Code Duplication · Edited copies of one member (5 members, 4+ corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/KeyCommands.scala
Code Duplication · Edited copy of a member (6 corresponding lines) finagle-benchmark/src/main/scala/com/twitter/finagle/http/HttpMuxerBenchmark.scala
Code Duplication · Edited copy of a member (4 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/Thrift.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: 2 findings
These 2 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.
€83,000 to €420,000, for 1,381 to 4,382 hours of work, about 1.7 person-years for 1 to 4 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 112,827 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
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.
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.
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 €250,000 to build again, about 1.7 person-years of work. Its weakest lens is Code Health, at 57 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
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`. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
560 modules, with 637 dependencies between them. 7 loops run through 50 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 520 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.
Uses a module listed above itPart of a loopThe module itself
6→29 com.twitter.finagle.Stack uses com.twitter.finaglepart of a loop✕
Connections
30 pairs of types, where a type in com.twitter.finagle.Stack uses a type in com.twitter.finagle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.twitter.finagle.Stack uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.Stack, while a change to com.twitter.finagle.Stack can't break com.twitter.finagle.
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.
com.twitter.finagle.loadbalancer uses com.twitter.finagle.util, so a change to com.twitter.finagle.util can break com.twitter.finagle.loadbalancer, while a change to com.twitter.finagle.loadbalancer can't break com.twitter.finagle.util.
Position
Below the diagonal: com.twitter.finagle.loadbalancer uses a module listed above it, which is the healthy direction.
7→29 com.twitter.finagle.loadbalancer uses com.twitter.finaglepart of a loop✕
Connections
27 pairs of types, where a type in com.twitter.finagle.loadbalancer uses a type in com.twitter.finagle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.twitter.finagle.loadbalancer uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.loadbalancer, while a change to com.twitter.finagle.loadbalancer can't break com.twitter.finagle.
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.
com.twitter.finagle.memcached uses com.twitter.finagle.memcached.protocol, so a change to com.twitter.finagle.memcached.protocol can break com.twitter.finagle.memcached, while a change to com.twitter.finagle.memcached can't break com.twitter.finagle.memcached.protocol.
Position
Below the diagonal: com.twitter.finagle.memcached uses a module listed above it, which is the healthy direction.
8→29 com.twitter.finagle.memcached uses com.twitter.finaglepart of a loop✕
Connections
10 pairs of types, where a type in com.twitter.finagle.memcached uses a type in com.twitter.finagle.
com.twitter.finagle.memcached uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.memcached, while a change to com.twitter.finagle.memcached can't break com.twitter.finagle.
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→32 com.twitter.finagle.memcached uses (global)part of a loop✕
Connections
1 pair of types, where a type in com.twitter.finagle.memcached uses a type in (global).
com.twitter.finagle.memcached uses (global), so a change to (global) can break com.twitter.finagle.memcached, while a change to com.twitter.finagle.memcached can't break (global).
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→29 com.twitter.finagle.mux.transport uses com.twitter.finaglepart of a loop✕
Connections
2 pairs of types, where a type in com.twitter.finagle.mux.transport uses a type in com.twitter.finagle.
com.twitter.finagle.mux.transport uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.mux.transport, while a change to com.twitter.finagle.mux.transport can't break com.twitter.finagle.
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.
com.twitter.finagle.postgresql.BackendMessage uses com.twitter.finagle.postgresql.Types, so a change to com.twitter.finagle.postgresql.Types can break com.twitter.finagle.postgresql.BackendMessage, while a change to com.twitter.finagle.postgresql.BackendMessage can't break com.twitter.finagle.postgresql.Types.
Position
Below the diagonal: com.twitter.finagle.postgresql.BackendMessage uses a module listed above it, which is the healthy direction.
10→27 com.twitter.finagle.postgresql.BackendMessage uses com.twitter.finagle.postgresqlpart of a loop✕
Connections
21 pairs of types, where a type in com.twitter.finagle.postgresql.BackendMessage uses a type in com.twitter.finagle.postgresql.
com.twitter.finagle.postgresql.BackendMessage uses com.twitter.finagle.postgresql, so a change to com.twitter.finagle.postgresql can break com.twitter.finagle.postgresql.BackendMessage, while a change to com.twitter.finagle.postgresql.BackendMessage can't break com.twitter.finagle.postgresql.
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.
com.twitter.finagle.postgresql.Response uses com.twitter.finagle.postgresql.Types, so a change to com.twitter.finagle.postgresql.Types can break com.twitter.finagle.postgresql.Response, while a change to com.twitter.finagle.postgresql.Response can't break com.twitter.finagle.postgresql.Types.
Position
Below the diagonal: com.twitter.finagle.postgresql.Response uses a module listed above it, which is the healthy direction.
11→27 com.twitter.finagle.postgresql.Response uses com.twitter.finagle.postgresqlpart of a loop✕
Connections
7 pairs of types, where a type in com.twitter.finagle.postgresql.Response uses a type in com.twitter.finagle.postgresql.
com.twitter.finagle.postgresql.Response uses com.twitter.finagle.postgresql, so a change to com.twitter.finagle.postgresql can break com.twitter.finagle.postgresql.Response, while a change to com.twitter.finagle.postgresql.Response can't break com.twitter.finagle.postgresql.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→19 com.twitter.finagle.ssl.server uses com.twitter.finagle.sslpart of a loop✕
Connections
9 pairs of types, where a type in com.twitter.finagle.ssl.server uses a type in com.twitter.finagle.ssl.
com.twitter.finagle.ssl.server uses com.twitter.finagle.ssl, so a change to com.twitter.finagle.ssl can break com.twitter.finagle.ssl.server, while a change to com.twitter.finagle.ssl.server can't break com.twitter.finagle.ssl.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→29 com.twitter.finagle.ssl.server uses com.twitter.finaglepart of a loop✕
Connections
1 pair of types, where a type in com.twitter.finagle.ssl.server uses a type in com.twitter.finagle.
com.twitter.finagle.ssl.server uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.ssl.server, while a change to com.twitter.finagle.ssl.server can't break com.twitter.finagle.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→29 com.twitter.finagle.tracing uses com.twitter.finaglepart of a loop✕
Connections
20 pairs of types, where a type in com.twitter.finagle.tracing uses a type in com.twitter.finagle.
com.twitter.finagle.tracing uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.tracing, while a change to com.twitter.finagle.tracing can't break com.twitter.finagle.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→32 com.twitter.finagle.tracing uses (global)part of a loop✕
Connections
2 pairs of types, where a type in com.twitter.finagle.tracing uses a type in (global).
The types involved
com.twitter.finagle.tracing.DefaultTracer → Proxy
com.twitter.finagle.tracing.SpanId → Proxy
Direction
com.twitter.finagle.tracing uses (global), so a change to (global) can break com.twitter.finagle.tracing, while a change to com.twitter.finagle.tracing can't break (global).
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.
com.twitter.finagle.transport uses com.twitter.finagle.ssl.session, so a change to com.twitter.finagle.ssl.session can break com.twitter.finagle.transport, while a change to com.twitter.finagle.transport can't break com.twitter.finagle.ssl.session.
Position
Below the diagonal: com.twitter.finagle.transport uses a module listed above it, which is the healthy direction.
14→29 com.twitter.finagle.transport uses com.twitter.finaglepart of a loop✕
Connections
3 pairs of types, where a type in com.twitter.finagle.transport uses a type in com.twitter.finagle.
com.twitter.finagle.transport uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.transport, while a change to com.twitter.finagle.transport can't break com.twitter.finagle.
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.
com.twitter.finagle.mux uses com.twitter.finagle.mux.transport, so a change to com.twitter.finagle.mux.transport can break com.twitter.finagle.mux, while a change to com.twitter.finagle.mux can't break com.twitter.finagle.mux.transport.
Position
Below the diagonal: com.twitter.finagle.mux uses a module listed above it, which is the healthy direction.
15→29 com.twitter.finagle.mux uses com.twitter.finaglepart of a loop✕
Connections
7 pairs of types, where a type in com.twitter.finagle.mux uses a type in com.twitter.finagle.
com.twitter.finagle.mux uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.mux, while a change to com.twitter.finagle.mux can't break com.twitter.finagle.
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.
com.twitter.finagle.postgresql.machine uses com.twitter.finagle.postgresql.BackendMessage, so a change to com.twitter.finagle.postgresql.BackendMessage can break com.twitter.finagle.postgresql.machine, while a change to com.twitter.finagle.postgresql.machine can't break com.twitter.finagle.postgresql.BackendMessage.
Position
Below the diagonal: com.twitter.finagle.postgresql.machine uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql.machine uses com.twitter.finagle.postgresql.Response, so a change to com.twitter.finagle.postgresql.Response can break com.twitter.finagle.postgresql.machine, while a change to com.twitter.finagle.postgresql.machine can't break com.twitter.finagle.postgresql.Response.
Position
Below the diagonal: com.twitter.finagle.postgresql.machine uses a module listed above it, which is the healthy direction.
16→27 com.twitter.finagle.postgresql.machine uses com.twitter.finagle.postgresqlpart of a loop✕
Connections
5 pairs of types, where a type in com.twitter.finagle.postgresql.machine uses a type in com.twitter.finagle.postgresql.
com.twitter.finagle.postgresql.machine uses com.twitter.finagle.postgresql, so a change to com.twitter.finagle.postgresql can break com.twitter.finagle.postgresql.machine, while a change to com.twitter.finagle.postgresql.machine can't break com.twitter.finagle.postgresql.
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.
com.twitter.finagle.redis.exp uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.redis.exp, while a change to com.twitter.finagle.redis.exp can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.redis.exp uses a module listed above it, which is the healthy direction.
17→20 com.twitter.finagle.redis.exp uses com.twitter.finagle.redis.protocolpart of a loop✕
Connections
9 pairs of types, where a type in com.twitter.finagle.redis.exp uses a type in com.twitter.finagle.redis.protocol.
com.twitter.finagle.redis.exp uses com.twitter.finagle.redis.protocol, so a change to com.twitter.finagle.redis.protocol can break com.twitter.finagle.redis.exp, while a change to com.twitter.finagle.redis.exp can't break com.twitter.finagle.redis.protocol.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→29 com.twitter.finagle.redis.exp uses com.twitter.finaglepart of a loop✕
Connections
7 pairs of types, where a type in com.twitter.finagle.redis.exp uses a type in com.twitter.finagle.
com.twitter.finagle.redis.exp uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.redis.exp, while a change to com.twitter.finagle.redis.exp can't break com.twitter.finagle.
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.
com.twitter.finagle.service uses com.twitter.finagle.tracing, so a change to com.twitter.finagle.tracing can break com.twitter.finagle.service, while a change to com.twitter.finagle.service can't break com.twitter.finagle.tracing.
Position
Below the diagonal: com.twitter.finagle.service uses a module listed above it, which is the healthy direction.
18→29 com.twitter.finagle.service uses com.twitter.finaglepart of a loop✕
Connections
47 pairs of types, where a type in com.twitter.finagle.service uses a type in com.twitter.finagle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.twitter.finagle.service uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.service, while a change to com.twitter.finagle.service can't break com.twitter.finagle.
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.
com.twitter.finagle.ssl uses com.twitter.finagle.ssl.server, so a change to com.twitter.finagle.ssl.server can break com.twitter.finagle.ssl, while a change to com.twitter.finagle.ssl can't break com.twitter.finagle.ssl.server.
Position
Below the diagonal: com.twitter.finagle.ssl uses a module listed above it, which is the healthy direction.
19→29 com.twitter.finagle.ssl uses com.twitter.finaglepart of a loop✕
Connections
1 pair of types, where a type in com.twitter.finagle.ssl uses a type in com.twitter.finagle.
com.twitter.finagle.ssl uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.ssl, while a change to com.twitter.finagle.ssl can't break com.twitter.finagle.
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.
com.twitter.finagle.redis.protocol uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.redis.protocol, while a change to com.twitter.finagle.redis.protocol can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.redis.protocol uses a module listed above it, which is the healthy direction.
com.twitter.finagle.redis.protocol uses com.twitter.finagle.redis.exp, so a change to com.twitter.finagle.redis.exp can break com.twitter.finagle.redis.protocol, while a change to com.twitter.finagle.redis.protocol can't break com.twitter.finagle.redis.exp.
Position
Below the diagonal: com.twitter.finagle.redis.protocol uses a module listed above it, which is the healthy direction.
20→29 com.twitter.finagle.redis.protocol uses com.twitter.finaglepart of a loop✕
Connections
1 pair of types, where a type in com.twitter.finagle.redis.protocol uses a type in com.twitter.finagle.
com.twitter.finagle.redis.protocol uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.redis.protocol, while a change to com.twitter.finagle.redis.protocol can't break com.twitter.finagle.
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.
com.twitter.finagle.ssl.client uses com.twitter.finagle.ssl, so a change to com.twitter.finagle.ssl can break com.twitter.finagle.ssl.client, while a change to com.twitter.finagle.ssl.client can't break com.twitter.finagle.ssl.
Position
Below the diagonal: com.twitter.finagle.ssl.client uses a module listed above it, which is the healthy direction.
21→29 com.twitter.finagle.ssl.client uses com.twitter.finaglepart of a loop✕
Connections
4 pairs of types, where a type in com.twitter.finagle.ssl.client uses a type in com.twitter.finagle.
com.twitter.finagle.ssl.client uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.ssl.client, while a change to com.twitter.finagle.ssl.client can't break com.twitter.finagle.
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.
com.twitter.finagle.param uses com.twitter.finagle.loadbalancer, so a change to com.twitter.finagle.loadbalancer can break com.twitter.finagle.param, while a change to com.twitter.finagle.param can't break com.twitter.finagle.loadbalancer.
Position
Below the diagonal: com.twitter.finagle.param uses a module listed above it, which is the healthy direction.
com.twitter.finagle.param uses com.twitter.finagle.ssl.server, so a change to com.twitter.finagle.ssl.server can break com.twitter.finagle.param, while a change to com.twitter.finagle.param can't break com.twitter.finagle.ssl.server.
Position
Below the diagonal: com.twitter.finagle.param uses a module listed above it, which is the healthy direction.
com.twitter.finagle.param uses com.twitter.finagle.service, so a change to com.twitter.finagle.service can break com.twitter.finagle.param, while a change to com.twitter.finagle.param can't break com.twitter.finagle.service.
Position
Below the diagonal: com.twitter.finagle.param uses a module listed above it, which is the healthy direction.
com.twitter.finagle.param uses com.twitter.finagle.ssl.client, so a change to com.twitter.finagle.ssl.client can break com.twitter.finagle.param, while a change to com.twitter.finagle.param can't break com.twitter.finagle.ssl.client.
Position
Below the diagonal: com.twitter.finagle.param uses a module listed above it, which is the healthy direction.
22→29 com.twitter.finagle.param uses com.twitter.finaglepart of a loop✕
Connections
2 pairs of types, where a type in com.twitter.finagle.param uses a type in com.twitter.finagle.
com.twitter.finagle.param uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.param, while a change to com.twitter.finagle.param can't break com.twitter.finagle.
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.
com.twitter.finagle.client uses com.twitter.finagle.util, so a change to com.twitter.finagle.util can break com.twitter.finagle.client, while a change to com.twitter.finagle.client can't break com.twitter.finagle.util.
Position
Below the diagonal: com.twitter.finagle.client uses a module listed above it, which is the healthy direction.
com.twitter.finagle.client uses com.twitter.finagle.Stack, so a change to com.twitter.finagle.Stack can break com.twitter.finagle.client, while a change to com.twitter.finagle.client can't break com.twitter.finagle.Stack.
Position
Below the diagonal: com.twitter.finagle.client uses a module listed above it, which is the healthy direction.
com.twitter.finagle.client uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.client, while a change to com.twitter.finagle.client can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.client uses a module listed above it, which is the healthy direction.
com.twitter.finagle.client uses com.twitter.finagle.service, so a change to com.twitter.finagle.service can break com.twitter.finagle.client, while a change to com.twitter.finagle.client can't break com.twitter.finagle.service.
Position
Below the diagonal: com.twitter.finagle.client uses a module listed above it, which is the healthy direction.
com.twitter.finagle.client uses com.twitter.finagle.param, so a change to com.twitter.finagle.param can break com.twitter.finagle.client, while a change to com.twitter.finagle.client can't break com.twitter.finagle.param.
Position
Below the diagonal: com.twitter.finagle.client uses a module listed above it, which is the healthy direction.
23→29 com.twitter.finagle.client uses com.twitter.finaglepart of a loop✕
Connections
47 pairs of types, where a type in com.twitter.finagle.client uses a type in com.twitter.finagle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.twitter.finagle.client uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.client, while a change to com.twitter.finagle.client can't break com.twitter.finagle.
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.
com.twitter.finagle.server uses com.twitter.finagle.ssl.session, so a change to com.twitter.finagle.ssl.session can break com.twitter.finagle.server, while a change to com.twitter.finagle.server can't break com.twitter.finagle.ssl.session.
Position
Below the diagonal: com.twitter.finagle.server uses a module listed above it, which is the healthy direction.
com.twitter.finagle.server uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.server, while a change to com.twitter.finagle.server can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.server uses a module listed above it, which is the healthy direction.
com.twitter.finagle.server uses com.twitter.finagle.param, so a change to com.twitter.finagle.param can break com.twitter.finagle.server, while a change to com.twitter.finagle.server can't break com.twitter.finagle.param.
Position
Below the diagonal: com.twitter.finagle.server uses a module listed above it, which is the healthy direction.
24→29 com.twitter.finagle.server uses com.twitter.finaglepart of a loop✕
Connections
18 pairs of types, where a type in com.twitter.finagle.server uses a type in com.twitter.finagle.
com.twitter.finagle.server uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.server, while a change to com.twitter.finagle.server can't break com.twitter.finagle.
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.
com.twitter.finagle.http uses com.twitter.finagle.tracing, so a change to com.twitter.finagle.tracing can break com.twitter.finagle.http, while a change to com.twitter.finagle.http can't break com.twitter.finagle.tracing.
Position
Below the diagonal: com.twitter.finagle.http uses a module listed above it, which is the healthy direction.
com.twitter.finagle.http uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.http, while a change to com.twitter.finagle.http can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.http uses a module listed above it, which is the healthy direction.
com.twitter.finagle.http uses com.twitter.finagle.client, so a change to com.twitter.finagle.client can break com.twitter.finagle.http, while a change to com.twitter.finagle.http can't break com.twitter.finagle.client.
Position
Below the diagonal: com.twitter.finagle.http uses a module listed above it, which is the healthy direction.
25→29 com.twitter.finagle.http uses com.twitter.finaglepart of a loop✕
Connections
27 pairs of types, where a type in com.twitter.finagle.http uses a type in com.twitter.finagle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.twitter.finagle.http uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.http, while a change to com.twitter.finagle.http can't break com.twitter.finagle.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→32 com.twitter.finagle.http uses (global)part of a loop✕
Connections
2 pairs of types, where a type in com.twitter.finagle.http uses a type in (global).
The types involved
com.twitter.finagle.http.RequestProxy → Proxy
com.twitter.finagle.http.ResponseProxy → Proxy
Direction
com.twitter.finagle.http uses (global), so a change to (global) can break com.twitter.finagle.http, while a change to com.twitter.finagle.http can't break (global).
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.
com.twitter.finagle.mysql uses com.twitter.finagle.tracing, so a change to com.twitter.finagle.tracing can break com.twitter.finagle.mysql, while a change to com.twitter.finagle.mysql can't break com.twitter.finagle.tracing.
Position
Below the diagonal: com.twitter.finagle.mysql uses a module listed above it, which is the healthy direction.
com.twitter.finagle.mysql uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.mysql, while a change to com.twitter.finagle.mysql can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.mysql uses a module listed above it, which is the healthy direction.
com.twitter.finagle.mysql uses com.twitter.finagle.client, so a change to com.twitter.finagle.client can break com.twitter.finagle.mysql, while a change to com.twitter.finagle.mysql can't break com.twitter.finagle.client.
Position
Below the diagonal: com.twitter.finagle.mysql uses a module listed above it, which is the healthy direction.
26→29 com.twitter.finagle.mysql uses com.twitter.finaglepart of a loop✕
Connections
14 pairs of types, where a type in com.twitter.finagle.mysql uses a type in com.twitter.finagle.
com.twitter.finagle.mysql uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.mysql, while a change to com.twitter.finagle.mysql can't break com.twitter.finagle.
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.
com.twitter.finagle.postgresql uses com.twitter.finagle.postgresql.Types, so a change to com.twitter.finagle.postgresql.Types can break com.twitter.finagle.postgresql, while a change to com.twitter.finagle.postgresql can't break com.twitter.finagle.postgresql.Types.
Position
Below the diagonal: com.twitter.finagle.postgresql uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql uses com.twitter.finagle.postgresql.Response, so a change to com.twitter.finagle.postgresql.Response can break com.twitter.finagle.postgresql, while a change to com.twitter.finagle.postgresql can't break com.twitter.finagle.postgresql.Response.
Position
Below the diagonal: com.twitter.finagle.postgresql uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.postgresql, while a change to com.twitter.finagle.postgresql can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.postgresql uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql uses com.twitter.finagle.postgresql.machine, so a change to com.twitter.finagle.postgresql.machine can break com.twitter.finagle.postgresql, while a change to com.twitter.finagle.postgresql can't break com.twitter.finagle.postgresql.machine.
Position
Below the diagonal: com.twitter.finagle.postgresql uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql uses com.twitter.finagle.client, so a change to com.twitter.finagle.client can break com.twitter.finagle.postgresql, while a change to com.twitter.finagle.postgresql can't break com.twitter.finagle.client.
Position
Below the diagonal: com.twitter.finagle.postgresql uses a module listed above it, which is the healthy direction.
27→29 com.twitter.finagle.postgresql uses com.twitter.finaglepart of a loop✕
Connections
5 pairs of types, where a type in com.twitter.finagle.postgresql uses a type in com.twitter.finagle.
com.twitter.finagle.postgresql uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.postgresql, while a change to com.twitter.finagle.postgresql can't break com.twitter.finagle.
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.
com.twitter.finagle.toggle uses com.twitter.finagle.server, so a change to com.twitter.finagle.server can break com.twitter.finagle.toggle, while a change to com.twitter.finagle.toggle can't break com.twitter.finagle.server.
Position
Below the diagonal: com.twitter.finagle.toggle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.memcached.protocol, so a change to com.twitter.finagle.memcached.protocol can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.memcached.protocol.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.ssl.session, so a change to com.twitter.finagle.ssl.session can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.ssl.session.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.util, so a change to com.twitter.finagle.util can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.util.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.memcached, so a change to com.twitter.finagle.memcached can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.memcached.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.mux, so a change to com.twitter.finagle.mux can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.mux.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.service, so a change to com.twitter.finagle.service can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.service.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.redis.protocol, so a change to com.twitter.finagle.redis.protocol can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.redis.protocol.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.http, so a change to com.twitter.finagle.http can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.http.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.mysql, so a change to com.twitter.finagle.mysql can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.mysql.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.postgresql, so a change to com.twitter.finagle.postgresql can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.postgresql.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
com.twitter.finagle uses com.twitter.finagle.toggle, so a change to com.twitter.finagle.toggle can break com.twitter.finagle, while a change to com.twitter.finagle can't break com.twitter.finagle.toggle.
Position
Below the diagonal: com.twitter.finagle uses a module listed above it, which is the healthy direction.
29→32 com.twitter.finagle uses (global)part of a loop✕
Connections
2 pairs of types, where a type in com.twitter.finagle uses a type in (global).
The types involved
com.twitter.finagle.ProxyAnnouncement → Proxy
com.twitter.finagle.ServiceProxy → Proxy
Direction
com.twitter.finagle uses (global), so a change to (global) can break com.twitter.finagle, while a change to com.twitter.finagle can't break (global).
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.
com.twitter.finagle.postgresql.transport uses com.twitter.finagle.ssl.session, so a change to com.twitter.finagle.ssl.session can break com.twitter.finagle.postgresql.transport, while a change to com.twitter.finagle.postgresql.transport can't break com.twitter.finagle.ssl.session.
Position
Below the diagonal: com.twitter.finagle.postgresql.transport uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql.transport uses com.twitter.finagle.postgresql.Response, so a change to com.twitter.finagle.postgresql.Response can break com.twitter.finagle.postgresql.transport, while a change to com.twitter.finagle.postgresql.transport can't break com.twitter.finagle.postgresql.Response.
Position
Below the diagonal: com.twitter.finagle.postgresql.transport uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql.transport uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.postgresql.transport, while a change to com.twitter.finagle.postgresql.transport can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.postgresql.transport uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql.transport uses com.twitter.finagle.postgresql.machine, so a change to com.twitter.finagle.postgresql.machine can break com.twitter.finagle.postgresql.transport, while a change to com.twitter.finagle.postgresql.transport can't break com.twitter.finagle.postgresql.machine.
Position
Below the diagonal: com.twitter.finagle.postgresql.transport uses a module listed above it, which is the healthy direction.
com.twitter.finagle.postgresql.transport uses com.twitter.finagle.postgresql, so a change to com.twitter.finagle.postgresql can break com.twitter.finagle.postgresql.transport, while a change to com.twitter.finagle.postgresql.transport can't break com.twitter.finagle.postgresql.
Position
Below the diagonal: com.twitter.finagle.postgresql.transport uses a module listed above it, which is the healthy direction.
com.twitter.finagle.stats uses com.twitter.finagle.service, so a change to com.twitter.finagle.service can break com.twitter.finagle.stats, while a change to com.twitter.finagle.stats can't break com.twitter.finagle.service.
Position
Below the diagonal: com.twitter.finagle.stats uses a module listed above it, which is the healthy direction.
com.twitter.finagle.stats uses com.twitter.finagle.http, so a change to com.twitter.finagle.http can break com.twitter.finagle.stats, while a change to com.twitter.finagle.stats can't break com.twitter.finagle.http.
Position
Below the diagonal: com.twitter.finagle.stats uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in (global) uses a type in com.twitter.finagle.http.
The types involved
Proxy → com.twitter.finagle.http.Request
Proxy → com.twitter.finagle.http.Response
Direction
(global) uses com.twitter.finagle.http, so a change to com.twitter.finagle.http can break (global), while a change to (global) can't break com.twitter.finagle.http.
Position
Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in (global) uses a type in com.twitter.finagle.mysql.
The types involved
Shared → com.twitter.finagle.mysql.Row
Direction
(global) uses com.twitter.finagle.mysql, so a change to com.twitter.finagle.mysql can break (global), while a change to (global) can't break com.twitter.finagle.mysql.
Position
Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
com.twitter.finagle.exp.routing uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.exp.routing, while a change to com.twitter.finagle.exp.routing can't break com.twitter.finagle.
Position
Below the diagonal: com.twitter.finagle.exp.routing uses a module listed above it, which is the healthy direction.
com.twitter.finagle.filter uses com.twitter.finagle.tracing, so a change to com.twitter.finagle.tracing can break com.twitter.finagle.filter, while a change to com.twitter.finagle.filter can't break com.twitter.finagle.tracing.
Position
Below the diagonal: com.twitter.finagle.filter uses a module listed above it, which is the healthy direction.
com.twitter.finagle.filter uses com.twitter.finagle.service, so a change to com.twitter.finagle.service can break com.twitter.finagle.filter, while a change to com.twitter.finagle.filter can't break com.twitter.finagle.service.
Position
Below the diagonal: com.twitter.finagle.filter uses a module listed above it, which is the healthy direction.
com.twitter.finagle.filter uses com.twitter.finagle.http, so a change to com.twitter.finagle.http can break com.twitter.finagle.filter, while a change to com.twitter.finagle.filter can't break com.twitter.finagle.http.
Position
Below the diagonal: com.twitter.finagle.filter uses a module listed above it, which is the healthy direction.
com.twitter.finagle.filter uses com.twitter.finagle.toggle, so a change to com.twitter.finagle.toggle can break com.twitter.finagle.filter, while a change to com.twitter.finagle.filter can't break com.twitter.finagle.toggle.
Position
Below the diagonal: com.twitter.finagle.filter uses a module listed above it, which is the healthy direction.
45 pairs of types, where a type in com.twitter.finagle.filter uses a type in com.twitter.finagle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.twitter.finagle.filter uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.filter, while a change to com.twitter.finagle.filter can't break com.twitter.finagle.
Position
Below the diagonal: com.twitter.finagle.filter uses a module listed above it, which is the healthy direction.
com.twitter.finagle.http2.transport.client uses com.twitter.finagle.transport, so a change to com.twitter.finagle.transport can break com.twitter.finagle.http2.transport.client, while a change to com.twitter.finagle.http2.transport.client can't break com.twitter.finagle.transport.
Position
Below the diagonal: com.twitter.finagle.http2.transport.client uses a module listed above it, which is the healthy direction.
com.twitter.finagle.http2.transport.client uses com.twitter.finagle.client, so a change to com.twitter.finagle.client can break com.twitter.finagle.http2.transport.client, while a change to com.twitter.finagle.http2.transport.client can't break com.twitter.finagle.client.
Position
Below the diagonal: com.twitter.finagle.http2.transport.client uses a module listed above it, which is the healthy direction.
com.twitter.finagle.http2.transport.client uses com.twitter.finagle.http, so a change to com.twitter.finagle.http can break com.twitter.finagle.http2.transport.client, while a change to com.twitter.finagle.http2.transport.client can't break com.twitter.finagle.http.
Position
Below the diagonal: com.twitter.finagle.http2.transport.client uses a module listed above it, which is the healthy direction.
com.twitter.finagle.http2.transport.client uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.http2.transport.client, while a change to com.twitter.finagle.http2.transport.client can't break com.twitter.finagle.
Position
Below the diagonal: com.twitter.finagle.http2.transport.client uses a module listed above it, which is the healthy direction.
com.twitter.finagle.loadbalancer.aperture uses com.twitter.finagle.util, so a change to com.twitter.finagle.util can break com.twitter.finagle.loadbalancer.aperture, while a change to com.twitter.finagle.loadbalancer.aperture can't break com.twitter.finagle.util.
Position
Below the diagonal: com.twitter.finagle.loadbalancer.aperture uses a module listed above it, which is the healthy direction.
com.twitter.finagle.loadbalancer.aperture uses com.twitter.finagle.loadbalancer, so a change to com.twitter.finagle.loadbalancer can break com.twitter.finagle.loadbalancer.aperture, while a change to com.twitter.finagle.loadbalancer.aperture can't break com.twitter.finagle.loadbalancer.
Position
Below the diagonal: com.twitter.finagle.loadbalancer.aperture uses a module listed above it, which is the healthy direction.
com.twitter.finagle.loadbalancer.aperture uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.loadbalancer.aperture, while a change to com.twitter.finagle.loadbalancer.aperture can't break com.twitter.finagle.
Position
Below the diagonal: com.twitter.finagle.loadbalancer.aperture uses a module listed above it, which is the healthy direction.
com.twitter.finagle.pushsession uses com.twitter.finagle.ssl.session, so a change to com.twitter.finagle.ssl.session can break com.twitter.finagle.pushsession, while a change to com.twitter.finagle.pushsession can't break com.twitter.finagle.ssl.session.
Position
Below the diagonal: com.twitter.finagle.pushsession uses a module listed above it, which is the healthy direction.
com.twitter.finagle.pushsession uses com.twitter.finagle.client, so a change to com.twitter.finagle.client can break com.twitter.finagle.pushsession, while a change to com.twitter.finagle.pushsession can't break com.twitter.finagle.client.
Position
Below the diagonal: com.twitter.finagle.pushsession uses a module listed above it, which is the healthy direction.
com.twitter.finagle.pushsession uses com.twitter.finagle.server, so a change to com.twitter.finagle.server can break com.twitter.finagle.pushsession, while a change to com.twitter.finagle.pushsession can't break com.twitter.finagle.server.
Position
Below the diagonal: com.twitter.finagle.pushsession uses a module listed above it, which is the healthy direction.
com.twitter.finagle.pushsession uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.pushsession, while a change to com.twitter.finagle.pushsession can't break com.twitter.finagle.
Position
Below the diagonal: com.twitter.finagle.pushsession uses a module listed above it, which is the healthy direction.
com.twitter.finagle.thrift uses com.twitter.finagle.tracing, so a change to com.twitter.finagle.tracing can break com.twitter.finagle.thrift, while a change to com.twitter.finagle.thrift can't break com.twitter.finagle.tracing.
Position
Below the diagonal: com.twitter.finagle.thrift uses a module listed above it, which is the healthy direction.
com.twitter.finagle.thrift uses com.twitter.finagle.service, so a change to com.twitter.finagle.service can break com.twitter.finagle.thrift, while a change to com.twitter.finagle.thrift can't break com.twitter.finagle.service.
Position
Below the diagonal: com.twitter.finagle.thrift uses a module listed above it, which is the healthy direction.
com.twitter.finagle.thrift uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.thrift, while a change to com.twitter.finagle.thrift can't break com.twitter.finagle.
Position
Below the diagonal: com.twitter.finagle.thrift uses a module listed above it, which is the healthy direction.
com.twitter.finagle.http.exp.routing uses com.twitter.finagle.http, so a change to com.twitter.finagle.http can break com.twitter.finagle.http.exp.routing, while a change to com.twitter.finagle.http.exp.routing can't break com.twitter.finagle.http.
Position
Below the diagonal: com.twitter.finagle.http.exp.routing uses a module listed above it, which is the healthy direction.
com.twitter.finagle.http.exp.routing uses com.twitter.finagle.exp.routing, so a change to com.twitter.finagle.exp.routing can break com.twitter.finagle.http.exp.routing, while a change to com.twitter.finagle.http.exp.routing can't break com.twitter.finagle.exp.routing.
Position
Below the diagonal: com.twitter.finagle.http.exp.routing uses a module listed above it, which is the healthy direction.
com.twitter.finagle.mux.pushsession uses com.twitter.finagle.mux.transport, so a change to com.twitter.finagle.mux.transport can break com.twitter.finagle.mux.pushsession, while a change to com.twitter.finagle.mux.pushsession can't break com.twitter.finagle.mux.transport.
Position
Below the diagonal: com.twitter.finagle.mux.pushsession uses a module listed above it, which is the healthy direction.
com.twitter.finagle.mux.pushsession uses com.twitter.finagle.mux, so a change to com.twitter.finagle.mux can break com.twitter.finagle.mux.pushsession, while a change to com.twitter.finagle.mux.pushsession can't break com.twitter.finagle.mux.
Position
Below the diagonal: com.twitter.finagle.mux.pushsession uses a module listed above it, which is the healthy direction.
com.twitter.finagle.mux.pushsession uses com.twitter.finagle, so a change to com.twitter.finagle can break com.twitter.finagle.mux.pushsession, while a change to com.twitter.finagle.mux.pushsession can't break com.twitter.finagle.
Position
Below the diagonal: com.twitter.finagle.mux.pushsession uses a module listed above it, which is the healthy direction.
com.twitter.finagle.mux.pushsession uses com.twitter.finagle.pushsession, so a change to com.twitter.finagle.pushsession can break com.twitter.finagle.mux.pushsession, while a change to com.twitter.finagle.mux.pushsession can't break com.twitter.finagle.pushsession.
Position
Below the diagonal: com.twitter.finagle.mux.pushsession uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 57% · 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
15
High / Critical
A03:2025 — Software Supply Chain Failures
8
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
Roadmap
Top priorities: 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; Swallowed exception (caught, then discarded); Resolve the 514 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (6), Message.scala (3), Client.scala (3).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
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.
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.
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.
Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
How the grades work
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 — 20
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 — 351
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 — 568
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
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, 928 of 939 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 MEASURED: test source is present (.scala, .java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
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, .java) and this repository declares an sbt build (repository root, 721 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 an sbt build (REDACTED), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its sbt dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D19 Documentation Quality — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — 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. 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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.
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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
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.
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was IncludeCode.run at 31. A further 14 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 Status.fromCode at 59 — they are counted neither in the figure above nor in this dimension's score. 12 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: finagle-base-http/src/main/scala/com/twitter/finagle/http/Status.scala (Status.fromCode at 59), finagle-zipkin-core/src/main/scala/com/twitter/finagle/zipkin/core/RawZipkinTracer.scala (RawZipkinTracer.record at 30), finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Type.scala (Type.getCodeString at 29), finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheKeeperException.scala (ApacheKeeperException.apply at 27), finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/transport/MessageDecoder.scala (MessageDecoder.fromBuf at 23), and 7 more not listed here. 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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with IncludeCode.run (cyclomatic 31), Interpreter.apply (cyclomatic 28), NameTree.eval (cyclomatic 20). — 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 9 together lifts Cyclomatic Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 34 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with IncludeCode.run (cognitive 48), Interpreter.apply (cognitive 39). — 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 6.8 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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 Classes9.7 / 10Stronggated by 7 serious findings✓ 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 7 TooManyMethods finding(s) in God Classes — start with Message.scala, ClientBuilder.scala, Tracing.scala. — One of this dimension's main actionable groups (7 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.
33 duplicated block group(s) detected. 2.7 % of the production lines (3,083 of 112,827) are in a reported copy. A further 86 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 (14 corresponding lines) · ×6finagle-core/src/main/scala/com/twitter/finagle/filter/ClearBroadcastContextFilter.scala:20
Edited copy of a member (7 corresponding lines) · ×6finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:78
Edited copy of a member (9 corresponding lines) · ×6finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/ClientTraceContextFilter.scala:13
Edited copy of a member (12 corresponding lines) · ×5finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:269
Edited copy of a member (10 corresponding lines) · ×5finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:113
+ 59 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with ClearBroadcastContextFilter.scala, StatsFilter.scala, Framer.scala. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with Stack.scala, WeightedAddress.scala, MethodBuilder.scala. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with ClientTraceContextFilter.scala, ValueReads.scala, DelayedReleaseService.scala. — One of this dimension's main actionable groups (6 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 3 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.
33 production modules (sbt+RubyGems), 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; 3 module(s) off the main sequence, with abstractness counted on 28 of the 33 (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: finagle-grpc-context · ×3
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 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 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ChannelSnooper.scala, Metrics.scala. — One of this dimension's main actionable groups (2 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.
0 outdated direct gem(s), 0 pinning defect(s). 1 declaration(s) graded against rubygems.org, none of them against a committed Gemfile.lock — this repository commits none, which a published gem correctly does not, so currency is read off the declared requirements: a declaration that does not cap below the current release resolves to it on `bundle install`. 1 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
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.
0 of 1 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 1 runtime gem(s) this repository declares. It commits no Gemfile.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. This repository publishes itself under Apache License Version 2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares an sbt build (REDACTED), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What 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.
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is finagle-core/src/main/scala/com/twitter/finagle/Exceptions.scala. Counted over 325 of the 1204 production source files in this repository: 652 are under the ~2,400-byte size floor this dimension measures over, and the remaining 227 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
✓ 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.
120 deducted task-comment markers across 112827 LoC (0.1/KLoC) → score 9.8. 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 120 TodoComment finding(s) in Explicit Debt — start with ServerCommands.scala (24), Parameter.scala (6), PropertiesSpec.scala (5). — One of this dimension's main actionable groups (120 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 5 build units (Bundler, 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: REDACTED 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.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
15 finding(s): 0 critical, 11 high, 3 medium, 1 low. 8 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 2 file(s) — `doc/src/sphinx/_themes/flask/layout.html` (lines 1–4, line 6, lines 19–23, …), `doc/src/sphinx/_themes/flask_small/layout.html` (lines 1–16, lines 19–22) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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 8 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 (8 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 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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 anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
517 of 552 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is finagle-core/src/main/scala/com/twitter/finagle/builder/ClientBuilder.scala. Counted over 552 of the 1204 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3finagle-core/src/main/scala/com/twitter/finagle/builder/ClientBuilder.scala:1
Dormant codebase
What to do
Resolve the 514 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (6), Message.scala (3), Client.scala (3). — One of this dimension's main actionable groups (514 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ClientBuilder.scala, PartitioningStrategy.scala, Thrift.scala. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_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 EndpointerStackClient.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 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 1 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 dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, 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.
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.
`toPacket` 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. — finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Request.scala:72
`newNodeManager` 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. — finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/PartitioningStrategy.scala:629
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.
`toPacket` 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. — finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Request.scala:72
`newNodeManager` 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. — finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/PartitioningStrategy.scala:629
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×28) — finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:37, finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:41, finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:45, …
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.
Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
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.
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 & versioning9.9 / 10Exemplary✓ Tool-verified
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.
1 public type in `com.twitter.finagle.common.zookeeper` is marked as implementation by its own namespace, folder or name: `ServerSetImpl` (finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/ServerSetImpl.java:70, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/ServerSetImpl.java:70
What to do
Hide `com.twitter.finagle.common.zookeeper` (`ServerSetImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Do you agree with this assessment?
P2 · Observability7.8 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `doc/src/sphinx/code/client-server-anatomy`, `doc/src/sphinx/code/protocols`, `doc/src/sphinx/code/quickstart`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 1 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:17
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.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
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 builds on an HTTP-server library (REDACTED:579 — depends on `finagle-http`) but serves no HTTP of its own: its production source starts no server (no `newServerAt`/`bindAndHandle`, server builder, `Server.serve`, `Http.serve`, tapir server interpreter or Netty HTTP pipeline), declares no application one runs (no Play application, servlet, cask `MainRoutes`, `HttpApp` or twitter-server), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library.
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.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×3) — finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PasswordUtils.scala:29, finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/machine/HandshakeMachine.scala:76, finagle-toggle/src/main/scala/com/twitter/finagle/toggle/StandardToggleMap.scala:165
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PasswordUtils.scala:29` (MessageDigest.getInstance("SHA-1")), `finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/machine/HandshakeMachine.scala:76` (MessageDigest.getInstance("MD5")), `finagle-toggle/src/main/scala/com/twitter/finagle/toggle/StandardToggleMap.scala:165` (MessageDigest.getInstance("SHA-1")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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.
Do you agree with this assessment?
X13 · Undrained process stream3.5 / 10Weak✓ Tool-verified
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
The JDK pipes both `stdout` and `stderr` of a child started this way — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and here `p.getInputStream` (stdout) is read while the child's end is awaited, but nothing in this scope ever reads `p.getErrorStream` (stderr). The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds to stderr (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the `waitFor` or end of stream this code waits on never comes. Nothing fails loudly: the thread hangs and the stuck child holds its resources until something kills it. Read both streams (a thread or `Future` per stream), merge them with `redirectErrorStream(true)` before `start()`, discard the unwanted one with `redirectError(ProcessBuilder.Redirect.DISCARD)` (or `redirectOutput`), or use `scala.sys.process`, which pumps both. — finagle-redis/src/main/scala/com/twitter/finagle/redis/util/TestServer.scala:18
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
`uncompressedLength` is read from the bytes being parsed at line 88 (`getInt`), then used to size a `ByteBuffer.allocate` at line 90 — and nowhere in its scope is `uncompressedLength` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `uncompressedLength` against the bytes actually remaining and a maximum the format allows before allocating. — finagle-memcached/src/main/scala/com/twitter/finagle/memcached/compressing/scheme/Lz4MemcachedCompression.scala:90
What to do
Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
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.
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.
`Files.lines(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.anyMatch` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.lines(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — finagle-http/src/main/scala/com/twitter/finagle/http/KerberosAuthenticationFilter.scala:136
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. 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` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone — Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries 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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. 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.
`case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×18) — finagle-zipkin-core/src/main/scala/com/twitter/finagle/zipkin/core/Endpoint.scala:39, finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/pushsession/MuxDowngradingNegotiator.scala:195, finagle-thrift/src/main/scala/com/twitter/finagle/thrift/Protocols.scala:209, …
`case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×10) — finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:100, finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:106, finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:212, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:156, finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:268, finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:154, …
`rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — finagle-thrift/src/main/ruby/lib/finagle-thrift/client.rb:80
`case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — finagle-redis/src/main/scala/com/twitter/finagle/redis/util/TestServer.scala:34
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 1162 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.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
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 applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~96255 lines of test source are present (.scala, .java) 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.
D19 Documentation Quality — D19 withholds "Documentation: empty section": 1 candidate(s) were measured and not published.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 4 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Ruby 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. Aggregate roots were found in only one source directory (finagle-redis), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .py, .rb, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 (4 signals for this style, 2 needed — the count is met but a required primary signal is absent): 3 aggregate root(s) (AggregateRoot/IAggregateRoot); 717 value object(s); 31 domain event(s); its 3 declared aggregate(s) carry no behaviour — data bags on an AggregateRoot base: measured, not claimed as DDD; its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level finagle-example/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
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, Python, Ruby source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — 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.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — 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 Ruby, Scala, Java and Python were read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter; a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
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
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 Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — 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.
TodoComment finagle-thriftmux/src/main/scala/com/twitter/finagle/ThriftMux.scala:352— // TODO set the Path here. — 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 finagle-thrift/src/test/scala/com/twitter/finagle/thrift/TFinagleBinaryProtocolTest.scala:72— // todo: remove this test after dropping support for JDK8. — 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 finagle-thrift/src/test/scala/com/twitter/finagle/thrift/TFinagleBinaryProtocolTest.scala:94— // todo: remove this test after dropping support for JDK8. — 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 finagle-thrift/src/main/scala/com/twitter/finagle/thrift/TTwitterServerFilter.scala:87— // TODO: only try once? — 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 finagle-thrift/src/main/scala/com/twitter/finagle/thrift/transport/ThriftClientPreparer.scala:97— // TODO: also apply this for Protocols.binaryFactory — 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 finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/PartitioningStrategy.scala:737— // TODO reconcile these types w/ req / rep — 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 finagle-stats-core/src/main/scala/com/twitter/finagle/stats/MetricsStatsReceiver.scala:100— // todo: ideally these would be computed as rates over time, but this is 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 finagle-serversets/src/test/scala/com/twitter/finagle/serverset2/ZkSessionEndToEndTest.scala:23— // TODO: figure out why MockTimer doesn't work. — 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 finagle-serversets/src/main/scala/com/twitter/finagle/zookeeper/ZkClientFactory.scala:40— // TODO: Watchers are tied to the life of the client, — 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 finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:718— // TODO(William Farner): Cancel the watch when — 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 finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/ServerSetImpl.java:122— // TODO(John Sirois): Inject the helper so that backoff strategy can be configurable. — 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 finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/ZooKeeperClient.java:125— // TODO(John Sirois): DigestAuthenticationProvider is broken - uses platform default charset — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ConnectionCommands.scala:37— // TODO: ECHO — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ConnectionCommands.scala:39— // TODO: PING with argument — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:10— // TODO: CLIENT KILL — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:12— // TODO: CLIENT LIST — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:14— // TODO: CLIENT GETNAME — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:16— // TODO: CLIENT PAUSE — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:18— // TODO: CLIENT SETNAME — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:38— // TODO: ROLE — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:40— // TODO: SHUTDOWN — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:45— // TODO: BGREWRITEAOF — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:47— // TODO: BGSAVE — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:49— // TODO: COMMAND — 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 finagle-redis/src/main/scala/com/twitter/finagle/redis/ServerCommands.scala:51— // TODO: COMMAND COUNT — 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.
Swallowed exception (caught, then discarded) finagle-zipkin-core/src/main/scala/com/twitter/finagle/zipkin/core/Endpoint.scala:39— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:100— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:106— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:212— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:218— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/pushsession/MuxDowngradingNegotiator.scala:195— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/Protocols.scala:56— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/Protocols.scala:209— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/Protocols.scala:223— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:99— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:105— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:206— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:212— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-thrift/src/main/ruby/lib/finagle-thrift/client.rb:80— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/Vector.scala:38— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/Vector.scala:44— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-redis/src/main/scala/com/twitter/finagle/redis/util/TestServer.scala:34— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/transport/ChannelTransportContext.scala:38— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/server/ServiceIdentifierExtractor.scala:55— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/pushsession/Netty4PushChannelHandle.scala:100— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/Parameter.scala:45— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/Parameter.scala:60— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/Parameter.scala:69— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/Parameter.scala:80— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/Parameter.scala:91— `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
TooManyMethods: Message finagle-base-http/src/main/scala/com/twitter/finagle/http/Message.scala:28— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× 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: ClientBuilder finagle-core/src/main/scala/com/twitter/finagle/builder/ClientBuilder.scala:245— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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: Tracing finagle-core/src/main/scala/com/twitter/finagle/tracing/Tracing.scala:131— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: Request finagle-base-http/src/main/scala/com/twitter/finagle/http/Request.scala:24— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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: Row finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:55— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: NameTreeParsers finagle-core/src/main/scala/com/twitter/finagle/NameTreeParsers.scala:15— 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: AbstractByteBufByteReader finagle-netty4/src/main/scala/com/twitter/finagle/netty4/AbstractByteBufByteReader.scala:26— 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×6
Edited copy of a member (14 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/filter/ClearBroadcastContextFilter.scala:20— finagle-core/src/main/scala/com/twitter/finagle/filter/ClearBroadcastContextFilter.scala:20-35 | finagle-core/src/main/scala/com/twitter/finagle/filter/ClearContextValueFilter.scala:19-32 — 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) finagle-http/src/main/scala/com/twitter/finagle/http/filter/StatsFilter.scala:19— finagle-http/src/main/scala/com/twitter/finagle/http/filter/StatsFilter.scala:19-32 | finagle-http/src/main/scala/com/twitter/finagle/http/filter/StreamingStatsFilter.scala:12-26 — 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) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/protocol/text/Framer.scala:19— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/protocol/text/Framer.scala:19-32 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/protocol/text/Framer.scala:38-51 — 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) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PasswordUtils.scala:28— finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PasswordUtils.scala:28-41 | finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PasswordUtils.scala:56-69 — 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) finagle-redis/src/main/scala/com/twitter/finagle/redis/exp/SubscribeClient.scala:100— finagle-redis/src/main/scala/com/twitter/finagle/redis/exp/SubscribeClient.scala:100-113 | finagle-redis/src/main/scala/com/twitter/finagle/redis/exp/SubscribeClient.scala:136-149 — 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) finagle-core/src/main/scala/com/twitter/finagle/NameTreeParsers.scala:177— finagle-core/src/main/scala/com/twitter/finagle/NameTreeParsers.scala:177-190 | finagle-core/src/main/scala/com/twitter/finagle/NameTreeParsers.scala:192-205 — 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) · ×6
Edited copy of a member (7 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:78— finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:78-84 | finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:101-107 — 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) finagle-core/src/main/scala/com/twitter/finagle/addr/WeightedAddress.scala:24— finagle-core/src/main/scala/com/twitter/finagle/addr/WeightedAddress.scala:24-30 | finagle-core/src/main/scala/com/twitter/finagle/addr/WeightedAddress.scala:46-53 — 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) finagle-http/src/main/scala/com/twitter/finagle/http/MethodBuilder.scala:99— finagle-http/src/main/scala/com/twitter/finagle/http/MethodBuilder.scala:99-105 | finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/MethodBuilder.scala:114-120 — 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) finagle-core/src/main/scala/com/twitter/finagle/Announcer.scala:32— finagle-core/src/main/scala/com/twitter/finagle/Announcer.scala:32-38 | finagle-core/src/main/scala/com/twitter/finagle/Resolver.scala:33-39 — 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) finagle-redis/src/main/scala/com/twitter/finagle/redis/Client.scala:124— finagle-redis/src/main/scala/com/twitter/finagle/redis/Client.scala:124-130 | finagle-redis/src/main/scala/com/twitter/finagle/redis/SentinelCommands.scala:12-20 — 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) finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:45— finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:45-52 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Streams.scala:29-35 — 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.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×6
Edited copy of a member (9 corresponding lines) finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/ClientTraceContextFilter.scala:13— finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/ClientTraceContextFilter.scala:13-21 | finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/ServerTraceContextFilter.scala:17-25 — 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) finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueReads.scala:152— finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueReads.scala:152-160 | finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueWrites.scala:116-124 — 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) finagle-base-http/src/main/scala/com/twitter/finagle/http/DelayedReleaseService.scala:9— finagle-base-http/src/main/scala/com/twitter/finagle/http/DelayedReleaseService.scala:9-19 | finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/DelayedReleaseService.scala:9-17 — 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) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/TwemcacheCacheClient.scala:59— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/TwemcacheCacheClient.scala:59-70 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:667-675 — 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) finagle-stats-core/src/main/scala/com/twitter/finagle/stats/JsonExporter.scala:70— finagle-stats-core/src/main/scala/com/twitter/finagle/stats/JsonExporter.scala:70-78 | finagle-stats-core/src/main/scala/com/twitter/finagle/stats/PrometheusExporter.scala:305-313 — 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) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:310— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:310-318 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/TwemcacheCacheClient.scala:25-33 — 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.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×5
Edited copy of a member (12 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:269— finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:269-280 | finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:286-297 — 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) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MemcachedTracingFilter.scala:24— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MemcachedTracingFilter.scala:24-35 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MemcachedTracingFilter.scala:41-53 — 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) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:318— finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:318-329 | finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:344-355 — 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) finagle-core/src/main/scala/com/twitter/finagle/stats/JavaLoggerStatsReceiver.scala:19— finagle-core/src/main/scala/com/twitter/finagle/stats/JavaLoggerStatsReceiver.scala:19-30 | finagle-core/src/main/scala/com/twitter/finagle/stats/JavaLoggerStatsReceiver.scala:32-43 — 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) finagle-core/src/main/scala/com/twitter/finagle/ssl/client/JdkClientEngineFactory.scala:22— finagle-core/src/main/scala/com/twitter/finagle/ssl/client/JdkClientEngineFactory.scala:22-33 | finagle-core/src/main/scala/com/twitter/finagle/ssl/server/JdkServerEngineFactory.scala:19-30 — 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 copy of a member (10 corresponding lines) · ×5
Edited copy of a member (10 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:113— finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:113-123 | finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:199-208 — 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) finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/StackClientOps.scala:90— finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/StackClientOps.scala:90-99 | finagle-opencensus-tracing/src/main/scala/com/twitter/finagle/tracing/opencensus/StackServerOps.scala:88-97 — 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) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:220— finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:220-229 | finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:244-253 — 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) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:414— finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:414-423 | finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:438-447 — 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) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/MultiplexedService.scala:45— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/MultiplexedService.scala:45-54 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/MultiplexedService.scala:61-71 — 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) · ×5
Edited copy of a member (11 corresponding lines) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:268— finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:268-278 | finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:293-303 — 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) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:504— finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:504-516 | finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:546-556 — 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) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4StreamTransport.scala:182— finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4StreamTransport.scala:182-196 | finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4StreamTransport.scala:241-251 — 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) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftReqRepServicePerEndpoint.scala:66— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftReqRepServicePerEndpoint.scala:66-77 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftServicePerEndpoint.scala:60-70 — 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) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/aperture/RandomAperture.scala:154— finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/aperture/RandomAperture.scala:154-164 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/aperture/WeightedAperture.scala:137-147 — 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.
Swallowed exception (empty catch) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:156— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:268— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:154— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:261— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) finagle-benchmark/src/main/scala/com/twitter/finagle/thrift/ThriftGenBenchmark.scala:71— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×4
Edited copy of a member (17 corresponding lines) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/AbstractByteBufByteReader.scala:127— finagle-netty4/src/main/scala/com/twitter/finagle/netty4/AbstractByteBufByteReader.scala:127-143 | finagle-netty4/src/main/scala/com/twitter/finagle/netty4/AbstractByteBufByteReader.scala:145-161 — 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) finagle-core/src/main/scala/com/twitter/finagle/client/StdStackClient.scala:61— finagle-core/src/main/scala/com/twitter/finagle/client/StdStackClient.scala:61-79 | finagle-core/src/main/scala/com/twitter/finagle/pushsession/PushStackClient.scala:65-81 — 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) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:84— finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:84-100 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:304-320 — 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) finagle-exp/src/main/scala/com/twitter/finagle/exp/fiber_scheduler/util/Optimizer.scala:386— finagle-exp/src/main/scala/com/twitter/finagle/exp/fiber_scheduler/util/Optimizer.scala:386-404 | finagle-exp/src/main/scala/com/twitter/finagle/exp/fiber_scheduler/util/Optimizer.scala:409-425 — 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 (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala:94— finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala:94-108 | finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/server/Netty4ServerSslConfigurations.scala:158-177 — 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) finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/HttpRouter.scala:217— finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/HttpRouter.scala:217-231 | finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/HttpRouter.scala:249-263 — 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) finagle-core/src/main/scala/com/twitter/finagle/dispatch/ClientDispatcher.scala:39— finagle-core/src/main/scala/com/twitter/finagle/dispatch/ClientDispatcher.scala:39-53 | finagle-core/src/main/scala/com/twitter/finagle/dispatch/GenSerialClientDispatcher.scala:69-88 — 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) finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/MuxChannelHandle.scala:63— finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/MuxChannelHandle.scala:63-77 | finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/MuxChannelHandle.scala:90-104 — 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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:80— finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:80-93 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:120-139 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:149-165 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:371-383 — These 4 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 4 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 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:711— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:711-723 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:725-737 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:739-751 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:753-765 — These 4 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 4 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 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:82— finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:82-94 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Keys.scala:100-112 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Sets.scala:47-57 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/SortedSets.scala:338-348 — These 4 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 4 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 4 times.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×3
Edited copies of one member (3 members, 11+ corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala:123— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala:123-133 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala:136-147 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala:169-181 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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, 11+ corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftRichClient.scala:194— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftRichClient.scala:194-204 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftRichClient.scala:266-276 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftRichClient.scala:285-297 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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, 11+ corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:330— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:330-340 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:349-359 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:373-383 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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 (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/service/RetryFilter.scala:271— finagle-core/src/main/scala/com/twitter/finagle/service/RetryFilter.scala:271-274 | finagle-core/src/main/scala/com/twitter/finagle/service/TimeoutFilter.scala:311-321 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/BtreeSortedSetCommands.scala:32— finagle-redis/src/main/scala/com/twitter/finagle/redis/BtreeSortedSetCommands.scala:32-35 | finagle-redis/src/main/scala/com/twitter/finagle/redis/HashCommands.scala:32-35 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/Thrift.scala:475— finagle-thrift/src/main/scala/com/twitter/finagle/Thrift.scala:475-478 | finagle-thriftmux/src/main/scala/com/twitter/finagle/ThriftMux.scala:379-382 — These two members are one piece of code written twice and then edited apart: 4 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 (22 lines × 2) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:92— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:92-113 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:199-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. Read the line range as the matched WINDOW rather than a finished unit: at `finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:92` 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 (22 lines × 2) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:93— finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:93-114 | finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:205-226 — 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 `finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:93` 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 (22 lines × 2) finagle-toggle/src/main/scala/com/twitter/finagle/server/WriteOnce.scala:19— finagle-toggle/src/main/scala/com/twitter/finagle/server/WriteOnce.scala:19-40 | finagle-toggle/src/main/scala/com/twitter/finagle/toggle/WriteOnce.scala:19-40 — `finagle-toggle/src/main/scala/com/twitter/finagle/server/WriteOnce.scala` and `finagle-toggle/src/main/scala/com/twitter/finagle/toggle/WriteOnce.scala` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 22 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Bijections.scala:64— finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Bijections.scala:64-72 | finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Bijections.scala:119-127 — 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 (9 lines × 2) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:85— finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:85-93 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:305-313 — 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 `finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:85` 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 (9 lines × 2) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:192— finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:192-200 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:235-243 — 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 `finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:192` 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 (6 lines × 2) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala:123— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala:123-128 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala:136-142 — 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 `finagle-memcached/src/main/scala/com/twitter/finagle/memcached/MockClient.scala:123` 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 (6 lines × 2) finagle-core/src/main/scala/com/twitter/finagle/client/StackClient.scala:56— finagle-core/src/main/scala/com/twitter/finagle/client/StackClient.scala:56-61 | finagle-core/src/main/scala/com/twitter/finagle/server/StackServer.scala:33-38 — 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 (6 lines × 2) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/partitioning/MemcachedPartitioningService.scala:130— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/partitioning/MemcachedPartitioningService.scala:130-135 | finagle-redis/src/main/scala/com/twitter/finagle/redis/RedisPartitioningService.scala:203-209 — 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.
Off the main sequence: finagle-grpc-context — finagle-grpc-context: 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: finagle-netty4 — finagle-netty4: abstractness 0.04, instability 0.18, distance 0.78 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Off the main sequence: finagle-core — finagle-core: abstractness 0.17, instability 0.09, distance 0.74 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
Weak hash algorithm finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PasswordUtils.scala:29— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/machine/HandshakeMachine.scala:76— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm finagle-toggle/src/main/scala/com/twitter/finagle/toggle/StandardToggleMap.scala:165— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
LogFormatter.escape (cognitive 16) finagle-http/src/main/scala/com/twitter/finagle/http/filter/LoggingFilter.scala:17— LogFormatter.escape has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 5). 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 shape REPEATS in the file: one other method here (LogFormatter.escape) 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.
LogFormatter.escape (cognitive 16) finagle-http/src/main/scala/com/twitter/finagle/http/filter/LoggingFilter.scala:24— LogFormatter.escape has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 5). 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 shape REPEATS in the file: one other method here (LogFormatter.escape) 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.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:271— finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:271-297 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:611-647 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/ThriftCustomPartitioningService.scala:95— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/ThriftCustomPartitioningService.scala:95-129 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/ThriftHashingPartitioningService.scala:114-140 — These two members are one piece of code written twice and then edited apart: 27 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) finagle-core/src/main/scala/com/twitter/finagle/filter/RequestLogger.scala:53— finagle-core/src/main/scala/com/twitter/finagle/filter/RequestLogger.scala:53-70 | finagle-core/src/main/scala/com/twitter/finagle/filter/VerboseRequestTracer.scala:58-76 — 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) finagle-core/src/main/scala/com/twitter/finagle/ssl/client/SslContextClientEngineFactory.scala:26— finagle-core/src/main/scala/com/twitter/finagle/ssl/client/SslContextClientEngineFactory.scala:26-43 | finagle-core/src/main/scala/com/twitter/finagle/ssl/server/SslContextServerEngineFactory.scala:23-40 — 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 (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Streams.scala:111— finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Streams.scala:111-116 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Streams.scala:133-139 — 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) finagle-benchmark/src/main/scala/com/twitter/finagle/http/HttpMuxerBenchmark.scala:96— finagle-benchmark/src/main/scala/com/twitter/finagle/http/HttpMuxerBenchmark.scala:96-101 | finagle-benchmark/src/main/scala/com/twitter/finagle/http/HttpRouterBenchmark.scala:98-103 — 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.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:688— finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:688-704 | finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:730-747 | finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:775-793 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 17+ corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/Thrift.scala:451— finagle-thrift/src/main/scala/com/twitter/finagle/Thrift.scala:451-467 | finagle-thrift/src/main/scala/com/twitter/finagle/Thrift.scala:624-640 | finagle-thriftmux/src/main/scala/com/twitter/finagle/ThriftMux.scala:666-682 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 4+ corresponding lines) · ×2
Edited copies of one member (5 members, 4+ corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/HashCommands.scala:110— finagle-redis/src/main/scala/com/twitter/finagle/redis/HashCommands.scala:110-113 | finagle-redis/src/main/scala/com/twitter/finagle/redis/KeyCommands.scala:161-164 | finagle-redis/src/main/scala/com/twitter/finagle/redis/PubSubCommands.scala:15-18 | finagle-redis/src/main/scala/com/twitter/finagle/redis/SetCommands.scala:113-116 | finagle-redis/src/main/scala/com/twitter/finagle/redis/SortedSetCommands.scala:211-214 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 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 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 4+ corresponding lines) finagle-redis/src/main/scala/com/twitter/finagle/redis/KeyCommands.scala:30— finagle-redis/src/main/scala/com/twitter/finagle/redis/KeyCommands.scala:30-33 | finagle-redis/src/main/scala/com/twitter/finagle/redis/ListCommands.scala:67-70 | finagle-redis/src/main/scala/com/twitter/finagle/redis/SetCommands.scala:74-77 | finagle-redis/src/main/scala/com/twitter/finagle/redis/StringCommands.scala:73-76 | finagle-redis/src/main/scala/com/twitter/finagle/redis/TopologyCommands.scala:26-29 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 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 5 times and the copies will drift further apart.
Duplicated block (14 lines × 2) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:116— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:116-129 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:223-236 — 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 `finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:116` 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 (14 lines × 2) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:117— finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:117-130 | finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:229-242 — 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 `finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:117` 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 (10 lines × 2) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:784— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:784-793 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:798-807 — 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 `finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:784` 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) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:81— finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:81-90 | finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:193-202 — 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 `finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:81` 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) finagle-benchmark/src/main/scala/com/twitter/finagle/thrift/ThriftGenBenchmark.scala:38— finagle-benchmark/src/main/scala/com/twitter/finagle/thrift/ThriftGenBenchmark.scala:38-45 | finagle-benchmark/src/main/scala/com/twitter/finagle/thrift/ThriftGenBenchmark.scala:101-108 — 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 `finagle-benchmark/src/main/scala/com/twitter/finagle/thrift/ThriftGenBenchmark.scala:38` 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 (8 lines × 2) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:284— finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:284-291 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:629-636 — 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 `finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:284` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala:77— finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala:77-81 | finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/server/Netty4ServerSslConfigurations.scala:81-85 — 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 `finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala:77` 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 (5 lines × 2) finagle-core/src/main/scala/com/twitter/finagle/client/EndpointerStackClient.scala:98— finagle-core/src/main/scala/com/twitter/finagle/client/EndpointerStackClient.scala:98-102 | finagle-thriftmux/src/main/scala/com/twitter/finagle/ThriftMux.scala:628-632 — 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 (13 lines × 2) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PlainHandshake.scala:13— finagle-mysql/src/main/scala/com/twitter/finagle/mysql/PlainHandshake.scala:13-25 | finagle-mysql/src/main/scala/com/twitter/finagle/mysql/SecureHandshake.scala:84-96 — 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 (13 lines × 2) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:522— finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:522-534 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:674-686 — 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 `finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:522` 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.
Low cohesion: SimpleChannelSnooper (LCOM4 17) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/channel/ChannelSnooper.scala:77— SimpleChannelSnooper's methods fall into 17 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 17 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: Metrics (LCOM4 6) finagle-stats-core/src/main/scala/com/twitter/finagle/stats/Metrics.scala:150— Metrics's methods fall into 6 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 6 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.
Unfinished stub — body is `???` finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Request.scala:72— `toPacket` 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 `???` finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/PartitioningStrategy.scala:629— `newNodeManager` 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 finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Request.scala:72— `toPacket` 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 finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/PartitioningStrategy.scala:629— `newNodeManager` 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.
IncludeCode.run (cyclomatic 31) doc/src/sphinx/exts/includecode.py:32— IncludeCode.run has cyclomatic complexity 31 (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.
Interpreter.apply (cyclomatic 28) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Interpreter.scala:19— Interpreter.apply has cyclomatic complexity 28 (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.
NameTree.eval (cyclomatic 20) finagle-core/src/main/scala/com/twitter/finagle/NameTree.scala:251— NameTree.eval has cyclomatic complexity 20 (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.
Simulation.main (cyclomatic 18) finagle-benchmark/src/main/scala/com/twitter/finagle/balancersim/Simulation.scala:43— Simulation.main has cyclomatic complexity 18 (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.
NameTree.simplify (cyclomatic 18) finagle-core/src/main/scala/com/twitter/finagle/NameTree.scala:159— NameTree.simplify 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.
Namer.bind (cyclomatic 18) finagle-core/src/main/scala/com/twitter/finagle/Namer.scala:218— Namer.bind 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.
AuthNegotiation.step (cyclomatic 18) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/AuthNegotiation.scala:192— AuthNegotiation.step 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.
Group.withMaxSyncConcurrency (cyclomatic 16) finagle-exp/src/main/scala/com/twitter/finagle/exp/fiber_scheduler/fiber/Group.scala:71— Group.withMaxSyncConcurrency has cyclomatic complexity 16 (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.
MuxClientSession.handleProcessMessage (cyclomatic 16) finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/MuxClientSession.scala:246— MuxClientSession.handleProcessMessage has cyclomatic complexity 16 (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.
IncludeCode.run (cognitive 48) doc/src/sphinx/exts/includecode.py:32— IncludeCode.run has cognitive complexity 48 (threshold 15). Drivers by points: if/else 19 (34 pts), boolean chains 5, ternaries 4 (5 pts), error handling 3, loops 1 (nesting depth added 16). 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.
Interpreter.apply (cognitive 39) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Interpreter.scala:19— Interpreter.apply has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (25 pts), match/switch 7 (13 pts), boolean chains 1 (nesting depth added 15). 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.
Rfc7230HeaderValidation.validateValue (cognitive 25) finagle-base-http/src/main/scala/com/twitter/finagle/http/headers/Rfc7230HeaderValidation.scala:126— Rfc7230HeaderValidation.validateValue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (21 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (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.
ClientDispatcher.decodePacket (cognitive 25) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/ClientDispatcher.scala:181— ClientDispatcher.decodePacket has cognitive complexity 25 (threshold 15). Drivers by points: loops 5 (20 pts), if/else 3 (4 pts), match/switch 1 (nesting depth added 16). 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.
LinearPathMatcher.extractMatchingParameterValues (cognitive 23) finagle-http/src/main/scala/com/twitter/finagle/http/exp/routing/PathMatcher.scala:355— LinearPathMatcher.extractMatchingParameterValues has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 3 (8 pts), boolean chains 1 (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.
Message.decodeTreq (cognitive 23) finagle-mux/src/main/scala/com/twitter/finagle/mux/transport/Message.scala:446— Message.decodeTreq has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 3 (5 pts), loops 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.
Netty4FormPostEncoder.encode (cognitive 23) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4FormPostEncoder.scala:42— Netty4FormPostEncoder.encode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 4 (9 pts), loops 1 (4 pts) (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.
WeightedP2CPick.pick (cognitive 22) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/aperture/WeightedP2CPick.scala:25— WeightedP2CPick.pick has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (22 pts) (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.
ClientDecoder.decodeData (cognitive 22) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/protocol/text/client/ClientDecoder.scala:80— ClientDecoder.decodeData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (21 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.
StringUtil.splitWorker (cognitive 21) finagle-base-http/src/main/scala/com/twitter/finagle/http/util/StringUtil.scala:90— StringUtil.splitWorker has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 2 (3 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.
Simulation.main (cognitive 21) finagle-benchmark/src/main/scala/com/twitter/finagle/balancersim/Simulation.scala:43— Simulation.main has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 4 (9 pts), boolean chains 1, match/switch 1 (nesting depth added 7). 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.
RequeueFilter.issueRequest (cognitive 21) finagle-core/src/main/scala/com/twitter/finagle/service/RequeueFilter.scala:65— RequeueFilter.issueRequest has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 2, match/switch 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.
Name.all (cognitive 20) finagle-core/src/main/scala/com/twitter/finagle/Name.scala:160— Name.all has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (13 pts), if/else 7 (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.
NameTree.simplify (cognitive 20) finagle-core/src/main/scala/com/twitter/finagle/NameTree.scala:159— NameTree.simplify has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 7 (15 pts), if/else 5 (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.
Netty4ClientSslConfigurations.startClientWithKey (cognitive 20) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala:62— Netty4ClientSslConfigurations.startClientWithKey has cognitive complexity 20 (threshold 15). Drivers by points: loops 7 (19 pts), match/switch 1 (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.
Netty4ServerSslConfigurations.startServerWithKey (cognitive 20) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/server/Netty4ServerSslConfigurations.scala:64— Netty4ServerSslConfigurations.startServerWithKey has cognitive complexity 20 (threshold 15). Drivers by points: loops 7 (19 pts), match/switch 1 (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.
QueryParamDecoder.decodeParams (cognitive 19) finagle-base-http/src/main/scala/com/twitter/finagle/http/QueryParamDecoder.scala:16— QueryParamDecoder.decodeParams has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 3 (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.
P2CPick.pick (cognitive 19) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/p2c/P2CPick.scala:23— P2CPick.pick has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2 (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.
TraceId.deserialize (cognitive 19) finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceId.scala:61— TraceId.deserialize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 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.
Group.withMaxSyncConcurrency (cognitive 19) finagle-exp/src/main/scala/com/twitter/finagle/exp/fiber_scheduler/fiber/Group.scala:71— Group.withMaxSyncConcurrency has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6, loops 1 (2 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.
ZstdDecoder.decode (cognitive 19) finagle-netty4/src/main/java/com/twitter/finagle/netty4/codec/compression/zstd/ZstdDecoder.java:47— ZstdDecoder.decode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), error handling 2 (5 pts), match/switch 1 (2 pts), loops 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.
HttpDtab.readXDtabPairs (cognitive 18) finagle-base-http/src/main/scala/com/twitter/finagle/http/codec/HttpDtab.scala:171— HttpDtab.readXDtabPairs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 4 (7 pts), match/switch 1 (2 pts) (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.
UriUtils.isValidUri (cognitive 18) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/util/UriUtils.scala:11— UriUtils.isValidUri has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3, 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.
Endpoint.parseJson (cognitive 18) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/Entry.scala:110— Endpoint.parseJson has cognitive complexity 18 (threshold 15). Drivers by points: loops 10 (15 pts), match/switch 2 (3 pts) (nesting depth added 6). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ClientTraceAnnotationsFilter.module (cognitive 18) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ClientTraceAnnotationsFilter.scala:16— ClientTraceAnnotationsFilter.module has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
NameTree.eval (cognitive 17) finagle-core/src/main/scala/com/twitter/finagle/NameTree.scala:251— NameTree.eval has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 6 (14 pts), if/else 3 (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.
StabilizingAddr.apply (cognitive 17) finagle-core/src/main/scala/com/twitter/finagle/addr/StabilizingAddr.scala:36— StabilizingAddr.apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), match/switch 3 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 3). 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.
LengthFieldFramer.readNextFrameLength (cognitive 17) finagle-core/src/main/scala/com/twitter/finagle/decoder/LengthFieldFramer.scala:91— LengthFieldFramer.readNextFrameLength has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 1 (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.
Trace.letTracerAndId (cognitive 17) finagle-core/src/main/scala/com/twitter/finagle/tracing/Trace.scala:183— Trace.letTracerAndId has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 2 (5 pts) (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.
RedisPartitioningService.mergeResponses (cognitive 17) finagle-redis/src/main/scala/com/twitter/finagle/redis/RedisPartitioningService.scala:127— RedisPartitioningService.mergeResponses has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), match/switch 4 (7 pts), loops 1 (3 pts) (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.
Namer.bind (cognitive 16) finagle-core/src/main/scala/com/twitter/finagle/Namer.scala:218— Namer.bind has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 4 (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.
HeapLeastLoaded.get (cognitive 16) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/heap/HeapLeastLoaded.scala:136— HeapLeastLoaded.get has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, loops 1 (nesting depth added 5). 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.
TraceInitializerFilter.apply (cognitive 16) finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:79— TraceInitializerFilter.apply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (16 pts) (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.
AnnotatingTracingFilter.apply (cognitive 16) finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:141— AnnotatingTracingFilter.apply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (5 pts) (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.
MuxClientSession.handleProcessMessage (cognitive 16) finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/MuxClientSession.scala:246— MuxClientSession.handleProcessMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (3 pts), boolean chains 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.
AuthNegotiation.step (cognitive 16) finagle-mysql/src/main/scala/com/twitter/finagle/mysql/AuthNegotiation.scala:192— AuthNegotiation.step has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 5 (7 pts) (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.
PgNumeric.bigDecimalToNumeric (cognitive 16) finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/PgNumeric.scala:52— PgNumeric.bigDecimalToNumeric has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 1 (2 pts) (nesting depth added 5). 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.
Zk2Resolver.merge (cognitive 16) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/Zk2Resolver.scala:64— Zk2Resolver.merge has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), match/switch 3 (8 pts) (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.
Change coupling: EndpointerStackClient.scala ↔ ListeningStackServer.scala finagle-core/src/main/scala/com/twitter/finagle/client/EndpointerStackClient.scala:1— `finagle-core/src/main/scala/com/twitter/finagle/client/EndpointerStackClient.scala` and `finagle-core/src/main/scala/com/twitter/finagle/server/ListeningStackServer.scala` change together 53% of the time (9 of the 17 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `11ca7e82` finagle: more comprehensive support for dimensional metrics; `188c6f6b` finagle-core: Don't migrate all metrics yet; `4867a5c7` finagle-core: Move SourceRole subtypes into its object — run `git show` on any of them.
Near-duplicate member pair (46 shared lines) finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:81— finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:81-130 | finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/service/ThriftMuxResponseClassifier.scala:193-242 — These two members are variants of one another: 46 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/liveness/FailureAccrualFactory.scala:180— finagle-core/src/main/scala/com/twitter/finagle/liveness/FailureAccrualFactory.scala:180-230 | finagle-partitioning/src/main/scala/com/twitter/finagle/partitioning/ConsistentHashingFailureAccrualFactory.scala:25-80 — These two members are one piece of code written twice and then edited apart: 51 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 (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala:62— finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/client/Netty4ClientSslConfigurations.scala:62-87 | finagle-netty4/src/main/scala/com/twitter/finagle/netty4/ssl/server/Netty4ServerSslConfigurations.scala:64-91 — 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 copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:84— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:84-129 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/service/ThriftResponseClassifier.scala:191-236 — These two members are one piece of code written twice and then edited apart: 46 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 (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/service/ExpiringService.scala:28— finagle-core/src/main/scala/com/twitter/finagle/service/ExpiringService.scala:28-59 | finagle-core/src/main/scala/com/twitter/finagle/service/ExpiringService.scala:76-104 — 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 (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftUtil.scala:71— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftUtil.scala:71-120 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/ThriftUtil.scala:126-173 — 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 (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:227— finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:227-265 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:320-360 — 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 copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/service/TimeoutFilter.scala:212— finagle-core/src/main/scala/com/twitter/finagle/service/TimeoutFilter.scala:212-246 | finagle-core/src/main/scala/com/twitter/finagle/service/TimeoutFilter.scala:253-282 — These two members are one piece of code written twice and then edited apart: 30 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/filter/NackAdmissionFilter.scala:86— finagle-core/src/main/scala/com/twitter/finagle/filter/NackAdmissionFilter.scala:86-113 | finagle-exp/src/main/scala/com/twitter/finagle/exp/ConcurrencyLimitFilter.scala:74-102 — These two members are one piece of code written twice and then edited apart: 28 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/Negotiation.scala:233— finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/Negotiation.scala:233-255 | finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/Negotiation.scala:284-311 — 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 (5 members, 23+ corresponding lines) · ×1
Edited copies of one member (5 members, 23+ corresponding lines) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:141— finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:141-163 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:165-189 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:209-232 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:252-274 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:276-302 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 23 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:102— finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:102-119 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:121-139 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:191-207 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:234-250 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:208— finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:208-223 | finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:245-260 | finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:341-356 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 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, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:278— finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:278-295 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:301-319 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:381-403 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:622-640 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 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 copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:300— finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:300-312 | finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:318-330 — 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 (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Bijections.scala:63— finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Bijections.scala:63-82 | finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Bijections.scala:118-137 — 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 (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4HttpCodec.scala:53— finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4HttpCodec.scala:53-74 | finagle-netty4-http/src/main/scala/com/twitter/finagle/netty4/http/Netty4HttpCodec.scala:105-126 — 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 (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) finagle-http/src/main/scala/com/twitter/finagle/http/KerberosAuthenticationFilter.scala:62— finagle-http/src/main/scala/com/twitter/finagle/http/KerberosAuthenticationFilter.scala:62-80 | finagle-http/src/main/scala/com/twitter/finagle/http/KerberosAuthenticationFilter.scala:85-103 — 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 copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:516— finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:516-534 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:671-686 — 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 copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/LeastLoaded.scala:28— finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/LeastLoaded.scala:28-43 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/PeakEwma.scala:98-111 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/aperture/LoadBand.scala:126-145 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:696— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:696-709 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:767-779 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:781-793 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:795-807 — These 4 members are one piece of code written 4 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 4 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) finagle-core/src/main/scala/com/twitter/finagle/factory/StatsFactoryWrapper.scala:19— finagle-core/src/main/scala/com/twitter/finagle/factory/StatsFactoryWrapper.scala:19-35 | finagle-core/src/main/scala/com/twitter/finagle/filter/DtabStatsFilter.scala:14-22 | finagle-core/src/main/scala/com/twitter/finagle/filter/ServerStatsFilter.scala:27-36 | finagle-core/src/main/scala/com/twitter/finagle/service/StatsServiceFactory.scala:35-43 — 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 (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) finagle-http/src/main/scala/com/twitter/finagle/http/service/RoutingService.scala:43— finagle-http/src/main/scala/com/twitter/finagle/http/service/RoutingService.scala:43-47 | finagle-http/src/main/scala/com/twitter/finagle/http/service/RoutingService.scala:52-57 | finagle-http/src/main/scala/com/twitter/finagle/http/service/RoutingService.scala:62-67 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 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 (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/client/ExportSslUsageModule.scala:8— finagle-core/src/main/scala/com/twitter/finagle/client/ExportSslUsageModule.scala:8-14 | finagle-core/src/main/scala/com/twitter/finagle/server/ExportSslUsageModule.scala:8-14 | finagle-mux/src/main/scala/com/twitter/finagle/mux/ExportCompressionUsage.scala:8-17 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 5+ corresponding lines) · ×1
Edited copies of one member (4 members, 5+ corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/client/StackClient.scala:24— finagle-core/src/main/scala/com/twitter/finagle/client/StackClient.scala:24-30 | finagle-core/src/main/scala/com/twitter/finagle/server/StackServer.scala:43-48 | finagle-core/src/main/scala/com/twitter/finagle/tracing/ForwardAnnotation.scala:69-76 | finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:57-61 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 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 copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) finagle-core/src/main/scala/com/twitter/finagle/builder/ClientBuilder.scala:909— finagle-core/src/main/scala/com/twitter/finagle/builder/ClientBuilder.scala:909-911 | finagle-core/src/main/scala/com/twitter/finagle/param/ClientTransportParams.scala:65-68 — 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 (31 lines × 2) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichClientParam.scala:138— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichClientParam.scala:138-168 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichServerParam.scala:86-116 — 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 (23 lines × 2) finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichClientParam.scala:184— finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichClientParam.scala:184-206 | finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichServerParam.scala:132-154 — 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 (19 lines × 2) finagle-core/src/main/scala/com/twitter/finagle/service/ExpiringService.scala:28— finagle-core/src/main/scala/com/twitter/finagle/service/ExpiringService.scala:28-46 | finagle-core/src/main/scala/com/twitter/finagle/service/ExpiringService.scala:76-94 — 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 `finagle-core/src/main/scala/com/twitter/finagle/service/ExpiringService.scala:28` 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) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:227— finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:227-241 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:320-334 — 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 `finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:227` 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 (11 lines × 2) finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:213— finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:213-223 | finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:250-260 — 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 `finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:213` 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 (9–11 lines × 2) finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:254— finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:254-262 | finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:279-289 — 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 `finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/client/apache/ApacheZooKeeper.scala:254` 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. 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 (10 lines × 4) finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:714— finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:714-723 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:728-737 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:742-751 | finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:756-765 — all 4 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 `finagle-memcached/src/main/scala/com/twitter/finagle/memcached/Client.scala:714` 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–10 lines × 4) finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:85— finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:85-94 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Keys.scala:103-112 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Sets.scala:49-57 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/SortedSets.scala:340-348 — 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 all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:85` 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 (10 lines × 3) finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:210— finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:210-219 | finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:247-256 | finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:343-352 — all 3 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 `finagle-core/src/main/scala/com/twitter/finagle/tracing/TraceInitializerFilter.scala:210` 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 (9 lines × 4) finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:80— finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:80-88 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:120-128 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:149-157 | finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:371-379 — all 4 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 `finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:80` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:131` calls `P2CPeakEwma` and `finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/Balancers.scala:158` 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 (34 lines × 2) doc/src/sphinx/code/client-server-anatomy/netty3/Pipeline.scala:8— doc/src/sphinx/code/client-server-anatomy/netty3/Pipeline.scala:8-41 | doc/src/sphinx/code/client-server-anatomy/netty4/Pipeline.scala:8-41 — 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 `doc/src/sphinx/code/client-server-anatomy/netty3/Pipeline.scala:8` 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. Note first that the copies are not typed on the same thing: `CharsetUtil` names `io.netty.util.CharsetUtil` in one and `org.jboss.netty.util.CharsetUtil` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) finagle-base-http/src/main/scala/com/twitter/finagle/http/GenStreamingSerialServerDispatcher.scala:151— finagle-base-http/src/main/scala/com/twitter/finagle/http/GenStreamingSerialServerDispatcher.scala:151-167 | finagle-core/src/main/scala/com/twitter/finagle/dispatch/ServerDispatcher.scala:133-149 — 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 (7 lines × 3) finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/BtreeSortedSet.scala:39— finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/BtreeSortedSet.scala:39-45 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:57-64 | finagle-redis/src/main/scala/com/twitter/finagle/redis/protocol/commands/Hashes.scala:69-76 — 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.
Duplicated block (8 lines × 3) finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:308— finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:308-315 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:523-530 | finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:675-682 — all 3 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 `finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:308` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) finagle-redis/src/main/scala/com/twitter/finagle/redis/util/TestServer.scala:18— The JDK pipes both `stdout` and `stderr` of a child started this way — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and here `p.getInputStream` (stdout) is read while the child's end is awaited, but nothing in this scope ever reads `p.getErrorStream` (stderr). The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds to stderr (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the `waitFor` or end of stream this code waits on never comes. Nothing fails loudly: the thread hangs and the stuck child holds its resources until something kills it. Read both streams (a thread or `Future` per stream), merge them with `redirectErrorStream(true)` before `start()`, discard the unwanted one with `redirectError(ProcessBuilder.Redirect.DISCARD)` (or `redirectOutput`), or use `scala.sys.process`, which pumps both.
X15 · Unvalidated length from an untrusted reader· Length read from the parsed input is spent without ever being bounded · ×1
Length read from the parsed input is spent without ever being bounded finagle-memcached/src/main/scala/com/twitter/finagle/memcached/compressing/scheme/Lz4MemcachedCompression.scala:90— `uncompressedLength` is read from the bytes being parsed at line 88 (`getInt`), then used to size a `ByteBuffer.allocate` at line 90 — and nowhere in its scope is `uncompressedLength` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `uncompressedLength` against the bytes actually remaining and a maximum the format allows before allocating.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the function that made it · ×1
Disposable created and abandoned in the function that made it finagle-http/src/main/scala/com/twitter/finagle/http/KerberosAuthenticationFilter.scala:136— `Files.lines(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.anyMatch` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.lines(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
Orphaned file finagle-thriftmux/src/main/scala/com/twitter/finagle/ThriftMux.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-core/src/main/scala/com/twitter/finagle/Stack.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/Group.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-http/src/main/scala/com/twitter/finagle/Http.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-core/src/main/scala/com/twitter/finagle/client/StackClient.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-mux/src/main/scala/com/twitter/finagle/mux/transport/Message.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/ServerSetImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-mux/src/main/scala/com/twitter/finagle/Mux.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/MethodBuilder.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-toggle/src/main/scala/com/twitter/finagle/toggle/ToggleMap.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-base-http/src/main/scala/com/twitter/finagle/http/Message.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-stats-core/src/main/scala/com/twitter/finagle/stats/BucketedHistogram.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/ZooKeeperClient.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-core/src/main/scala/com/twitter/finagle/loadbalancer/LoadBalancerFactory.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-core/src/main/scala/com/twitter/finagle/Backoff.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Request.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-netty4/src/main/scala/com/twitter/finagle/netty4/pushsession/Netty4PushChannelHandle.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-exp/src/main/scala/com/twitter/finagle/exp/fiber_scheduler/FiberScheduler.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Client.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-base-http/src/main/scala/com/twitter/finagle/http/Request.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-core/src/main/scala/com/twitter/finagle/Filter.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-http/src/main/scala/com/twitter/finagle/http/SpnegoAuthenticator.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file finagle-core/src/main/scala/com/twitter/finagle/service/RetryPolicy.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:37— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:41— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:45— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:49— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:53— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:57— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:61— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:65— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:69— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:73— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:77— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:81— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:85— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:89— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:113— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/btree/BtreeClientIntegrationSuite.scala:135— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/geo/GeoClientIntegrationSuite.scala:39— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/hash/HashClientIntegrationSuite.scala:74— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/hash/HashClientIntegrationSuite.scala:91— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/hash/HashClientIntegrationSuite.scala:105— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/key/KeyClientIntegrationSuite.scala:22— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/list/ListClientIntegrationSuite.scala:143— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/set/SetClientIntegrationSuite.scala:176— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/sorted-set/SortedSetClientIntegrationSuite.scala:177— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test finagle-redis/src/it/scala/com/twitter/finagle/redis/commands/topology/TopologyClientIntegrationSuite.scala:20— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Duplicated predicate finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichClientParam.scala:115— `SysPropStringLengthLimit.isDefined || SysPropContainerLengthLimit.isDefined` appears character-identically in 2 files — finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichClientParam.scala, finagle-thrift/src/main/scala/com/twitter/finagle/thrift/RichServerParam.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 finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueReads.scala:159— `first.accepts(tpe) || second.accepts(tpe)` appears character-identically in 2 files — finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueReads.scala, finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueWrites.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 finagle-thrift/src/main/scala/com/twitter/finagle/thrift/TTwitterServerFilter.scala:88— `msg.`type` == TMessageType.CALL && msg.name == ThriftTracing.CanTraceMethodName` appears character-identically in 2 files — finagle-thrift/src/main/scala/com/twitter/finagle/thrift/TTwitterServerFilter.scala, finagle-thriftmux/src/main/scala/com/twitter/finagle/thriftmux/pushsession/MuxDowngradingNegotiator.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 finagle-netty4/src/main/scala/com/twitter/finagle/netty4/channel/AbstractNetty4ClientChannelInitializer.scala:80— `readTimeout.isFinite && readTimeout > Duration.Zero` appears character-identically in 2 files — finagle-netty4/src/main/scala/com/twitter/finagle/netty4/channel/AbstractNetty4ClientChannelInitializer.scala, finagle-netty4/src/main/scala/com/twitter/finagle/netty4/channel/Netty4FramedServerChannelInitializer.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 finagle-base-http/src/main/scala/com/twitter/finagle/http/GenStreamingSerialServerDispatcher.scala:113— `res.isReturn && state.compareAndSet(Running, Idle)` appears character-identically in 2 files — finagle-base-http/src/main/scala/com/twitter/finagle/http/GenStreamingSerialServerDispatcher.scala, finagle-core/src/main/scala/com/twitter/finagle/dispatch/ServerDispatcher.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 finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueReads.scala:377— `tpe == PgType.Text || tpe == PgType.Json || tpe == PgType.Varchar || tpe == PgType.Bpchar || tpe == PgType.Name || tpe == PgType.Unknown` appears character-identically in 2 files — finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueReads.scala, finagle-postgresql/src/main/scala/com/twitter/finagle/postgresql/types/ValueWrites.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 finagle-stats-core/src/main/scala/com/twitter/finagle/stats/JsonExporter.scala:73— `value.builder.verbosity != Verbosity.Debug || pattern(value.hierarchicalName)` appears character-identically in 2 files — finagle-stats-core/src/main/scala/com/twitter/finagle/stats/JsonExporter.scala, finagle-stats-core/src/main/scala/com/twitter/finagle/stats/PrometheusExporter.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 finagle-netty4/src/main/scala/com/twitter/finagle/netty4/channel/AbstractNetty4ClientChannelInitializer.scala:85— `writeTimeout.isFinite && writeTimeout > Duration.Zero` appears character-identically in 2 files — finagle-netty4/src/main/scala/com/twitter/finagle/netty4/channel/AbstractNetty4ClientChannelInitializer.scala, finagle-netty4/src/main/scala/com/twitter/finagle/netty4/channel/Netty4FramedServerChannelInitializer.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.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file finagle-core/src/main/scala/com/twitter/finagle/builder/ClientBuilder.scala:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file finagle-thrift/src/main/scala/com/twitter/finagle/thrift/exp/partitioning/PartitioningStrategy.scala:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file finagle-thrift/src/main/scala/com/twitter/finagle/Thrift.scala:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Silent fallback default on parse failure finagle-base-http/src/main/scala/com/twitter/finagle/http/util/StringUtil.scala:17— `toSomeShort` answers `0` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. 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.
Silent fallback default on parse failure finagle-base-http/src/main/scala/com/twitter/finagle/http/util/StringUtil.scala:34— `toSomeInt` answers `0` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. 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.
Silent fallback default on parse failure finagle-base-http/src/main/scala/com/twitter/finagle/http/util/StringUtil.scala:51— `toSomeLong` answers `0L` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: finagle-core/src/main/scala/com/twitter/finagle/Exceptions.scala, finagle-core/src/main/scala/com/twitter/finagle/InetResolver.scala, finagle-serversets/src/main/scala/com/twitter/finagle/serverset2/Zk2Resolver.scala, finagle-mux/src/main/scala/com/twitter/finagle/mux/pushsession/MuxServerSession.scala. Pair on, review, or document these before any departure.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 6.0/10. The most over is `(repository root)` (112054 LoC, 2774 module-visible types across 183 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.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Dormant codebase — 517 of 552 significant files have no living knowledge — the codebase as a whole is dormant, not 517 separate risks. Counted over 552 of the 1204 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
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.
P10 · Library API & versioning· Implementation type on the public API · ×1
Implementation type on the public API finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/ServerSetImpl.java:70— 1 public type in `com.twitter.finagle.common.zookeeper` is marked as implementation by its own namespace, folder or name: `ServerSetImpl` (finagle-serversets/src/main/java/com/twitter/finagle/common/zookeeper/ServerSetImpl.java:70, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Logging is not universal — Only 1/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `doc/src/sphinx/code/client-server-anatomy`, `doc/src/sphinx/code/protocols`, `doc/src/sphinx/code/quickstart`.
No SAST REDACTED:17— 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 1 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.
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 1162 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 finagle-exp/src/main/scala/com/twitter/finagle/exp/fiber_scheduler/util/Cgroup.scala:100— `readLong` swallows every exception into `0L` — 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.
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.
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 01a1d8cf-cbbd-700e-ab0c-934976975d01 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 20 · Warnings: 351 · Recommendations: 568 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 06:47 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.