Executive summary
Netflix/zuul falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 57 out of 100 and is rated Adequate, and all 18 of its critical findings are security problems.
Maturity, at 49, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 8 points. Recording design decisions comes next, also worth about 8. Raising Maturity to 70 would lift the score to about 64.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one password or key is open to anyone who can read the repository. Pinning each tool to an exact version, setting a waiting period for automatic updates and replacing the exposed password or key would close these risks.
The product code is 26,407 lines, about €44,000 to rebuild.
If Maturity rose from 49 to 70, the lowest score rated Strong, the score would rise from 57 to about 64.
New since the last survey: 21 findings
- Code Duplication · Edited copy of a member (28 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/proxyprotocol/HAProxyMessageChannelHandler.java
- Code Duplication · Edited copy of a member (26 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/netty/filter/BaseZuulFilterRunner.java
- Code Duplication · Edited copy of a member (17 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/message/http/HttpQueryParams.java
- Code Duplication · Edited copy of a member (21 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/throttle/RejectionUtils.java
- Code Duplication · Edited copy of a member (23 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/netty/server/http2/Http2Configuration.java
- Code Duplication · Edited copy of a member (12 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/close/BaseConnectionCloseHandler.java
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) zuul-core/src/main/java/com/netflix/zuul/passport/CurrentPassport.java
- Code Duplication · Edited copy of a member (11 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/monitoring/ConnCounter.java
- Code Duplication · Edited copy of a member (18 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/metrics/HttpBodySizeRecordingChannelHandler.java
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) zuul-core/src/main/java/com/netflix/zuul/netty/server/Server.java
- Code Duplication · Edited copy of a member (12 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/ssl/ServerSslConfig.java
- Code Duplication · Edited copy of a member (7 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/metrics/EventLoopGroupMetrics.java
- Code Duplication · Edited copy of a member (12 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/stats/ErrorStatsData.java
- Code Duplication · Edited copy of a member (10 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/netty/ZuulToNettyHttpHeaders.java
- Code Duplication · Edited copy of a member (9 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/util/VipUtils.java
- Code Duplication · Edited copy of a member (10 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/SourceAddressChannelHandler.java
- Code Duplication · Edited copy of a member (15 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/SslExceptionsHandler.java
- Code Duplication · Edited copy of a member (9 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/Attrs.java
- Code Duplication · Edited copy of a member (8 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/close/BaseConnectionCloseHandler.java
- Code Duplication · Edited copy of a member (5 corresponding lines) zuul-sample/src/main/java/com/netflix/zuul/sample/push/SampleSSEPushChannelInitializer.java
- Code Duplication · Edited copy of a member (7 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/message/Header.java
Fixed since the last survey: 5 findings
- Secret Scanning · Leaked secret: private-key-store REDACTED
- Secret Scanning · Leaked secret: private-key zuul-sample/src/main/resources/ssl/server.key
- Secret Scanning · Leaked secret: private-key zuul-sample/src/main/resources/ssl/client.key
- Secrets (history) · Secret: private-key zuul-sample/src/main/resources/ssl/client.key
- Secrets (history) · Secret: private-key zuul-sample/src/main/resources/ssl/server.key
Rebuild cost: about €44,000 · Estimate
| Cost to rebuild | €15,000 to €74,000, for 245 to 778 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 26,407 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 config | 2 netty.common.accesslog | 3 netty.common.close | 4 netty.common.http2 | 5 netty.common.metrics | 6 netty.common.ssl | 7 netty.common.status | 8 zuul.resolver | 9 zuul.discovery | 10 zuul.message.http | 11 zuul.netty.ssl | 12 zuul.passport | 13 zuul.stats | 14 zuul | 15 zuul.netty.server.push | 16 zuul.niws | 17 zuul.stats.status | 18 netty.common.proxyprotocol | 19 netty.common.throttle | 20 zuul.filters | 21 zuul.monitoring | 22 zuul.exception | 23 zuul.filters.passport | 24 zuul.netty | 25 zuul.netty.connectionpool | 26 zuul.origins | 27 zuul.context | 28 zuul.netty.timeouts | 29 zuul.message | 30 zuul.netty.insights | 31 netty.common | 32 zuul.filters.http | 33 zuul.message.util | 34 zuul.netty.filter | 35 zuul.util | 36 zuul.filters.common | 37 zuul.filters.endpoint | 38 zuul.netty.server | 39 netty.common.channel.config | 40 zuul.netty.server.http2 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 config | ||||||||||||||||||||||||||||||||||||||||
| 2 netty.common.accesslog | ||||||||||||||||||||||||||||||||||||||||
| 3 netty.common.close | ||||||||||||||||||||||||||||||||||||||||
| 4 netty.common.http2 | ||||||||||||||||||||||||||||||||||||||||
| 5 netty.common.metrics | ||||||||||||||||||||||||||||||||||||||||
| 6 netty.common.ssl | ||||||||||||||||||||||||||||||||||||||||
| 7 netty.common.status | ||||||||||||||||||||||||||||||||||||||||
| 8 zuul.resolver | ||||||||||||||||||||||||||||||||||||||||
| 9 zuul.discovery | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 zuul.message.http | 2 | 2 | 10 | |||||||||||||||||||||||||||||||||||||
| 11 zuul.netty.ssl | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 zuul.passport | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 zuul.stats | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 zuul | 4 | 1 | 15 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 zuul.netty.server.push | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 zuul.niws | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 zuul.stats.status | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 netty.common.proxyprotocol | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 netty.common.throttle | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 zuul.filters | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 zuul.monitoring | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 zuul.exception | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 zuul.filters.passport | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 24 zuul.netty | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 zuul.netty.connectionpool | 2 | 2 | 8 | 5 | 3 | 5 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 26 zuul.origins | 2 | 5 | 2 | 2 | 1 | 1 | 1 | 3 | 4 | |||||||||||||||||||||||||||||||
| 27 zuul.context | 3 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 28 zuul.netty.timeouts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 zuul.message | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 zuul.netty.insights | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 netty.common | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 zuul.filters.http | 4 | 10 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 zuul.message.util | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 zuul.netty.filter | 6 | 6 | 1 | 8 | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 35 zuul.util | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 36 zuul.filters.common | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 zuul.filters.endpoint | 1 | 1 | 4 | 1 | 2 | 1 | 2 | 1 | 1 | 2 | 4 | 1 | 1 | 3 | 1 | 2 | ||||||||||||||||||||||||
| 38 zuul.netty.server | 3 | 2 | 6 | 1 | 3 | 6 | 1 | 11 | 1 | 1 | 1 | 1 | 4 | 1 | 1 | 1 | 5 | 1 | 5 | |||||||||||||||||||||
| 39 netty.common.channel.config | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 zuul.netty.server.http2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 |
9→8 zuul.discovery uses zuul.resolver✕
- Connections
- 2 pairs of types, where a type in zuul.discovery uses a type in zuul.resolver.
- The types involved
com.netflix.zuul.discovery.DynamicServerResolver→com.netflix.zuul.resolver.Resolvercom.netflix.zuul.discovery.DynamicServerResolver→com.netflix.zuul.resolver.ResolverListener
- Direction
- zuul.discovery uses zuul.resolver, so a change to zuul.resolver can break zuul.discovery, while a change to zuul.discovery can't break zuul.resolver.
- Position
- Below the diagonal: zuul.discovery uses a module listed above it, which is the healthy direction.
10→20 zuul.message.http uses zuul.filters part of a loop✕
- Connections
- 2 pairs of types, where a type in zuul.message.http uses a type in zuul.filters.
- The types involved
com.netflix.zuul.message.http.HttpRequestMessageImpl→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.message.http.HttpResponseMessageImpl→com.netflix.zuul.filters.ZuulFilter
- Direction
- zuul.message.http uses zuul.filters, so a change to zuul.filters can break zuul.message.http, while a change to zuul.message.http can't break zuul.filters.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→27 zuul.message.http uses zuul.context part of a loop✕
- Connections
- 2 pairs of types, where a type in zuul.message.http uses a type in zuul.context.
- The types involved
com.netflix.zuul.message.http.HttpRequestMessageImpl→com.netflix.zuul.context.SessionContextcom.netflix.zuul.message.http.HttpResponseMessageImpl→com.netflix.zuul.context.SessionContext
- Direction
- zuul.message.http uses zuul.context, so a change to zuul.context can break zuul.message.http, while a change to zuul.message.http can't break zuul.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→29 zuul.message.http uses zuul.message part of a loop✕
- Connections
- 10 pairs of types, where a type in zuul.message.http uses a type in zuul.message.
- The types involved
com.netflix.zuul.message.http.HttpHeaderNames→com.netflix.zuul.message.HeaderNamecom.netflix.zuul.message.http.HttpHeaderNamesCache→com.netflix.zuul.message.HeaderNamecom.netflix.zuul.message.http.HttpRequestInfo→com.netflix.zuul.message.Headerscom.netflix.zuul.message.http.HttpRequestInfo→com.netflix.zuul.message.ZuulMessagecom.netflix.zuul.message.http.HttpRequestMessage→com.netflix.zuul.message.ZuulMessagecom.netflix.zuul.message.http.HttpRequestMessageImpl→com.netflix.zuul.message.Headerscom.netflix.zuul.message.http.HttpRequestMessageImpl→com.netflix.zuul.message.ZuulMessagecom.netflix.zuul.message.http.HttpResponseInfo→com.netflix.zuul.message.ZuulMessagecom.netflix.zuul.message.http.HttpResponseMessageImpl→com.netflix.zuul.message.Headerscom.netflix.zuul.message.http.HttpResponseMessageImpl→com.netflix.zuul.message.ZuulMessage
- Direction
- zuul.message.http uses zuul.message, so a change to zuul.message can break zuul.message.http, while a change to zuul.message.http can't break zuul.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→6 zuul.netty.ssl uses netty.common.ssl✕
- Connections
- 2 pairs of types, where a type in zuul.netty.ssl uses a type in netty.common.ssl.
- The types involved
com.netflix.zuul.netty.ssl.BaseSslContextFactory→com.netflix.netty.common.ssl.ServerSslConfigcom.netflix.zuul.netty.ssl.ClientSslContextFactory→com.netflix.netty.common.ssl.ServerSslConfig
- Direction
- zuul.netty.ssl uses netty.common.ssl, so a change to netty.common.ssl can break zuul.netty.ssl, while a change to zuul.netty.ssl can't break netty.common.ssl.
- Position
- Below the diagonal: zuul.netty.ssl uses a module listed above it, which is the healthy direction.
12→27 zuul.passport uses zuul.context part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.passport uses a type in zuul.context.
- The types involved
com.netflix.zuul.passport.CurrentPassport→com.netflix.zuul.context.SessionContext
- Direction
- zuul.passport uses zuul.context, so a change to zuul.context can break zuul.passport, while a change to zuul.passport can't break zuul.context.
- 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→27 zuul.stats uses zuul.context part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.stats uses a type in zuul.context.
- The types involved
com.netflix.zuul.stats.RequestMetricsPublisher→com.netflix.zuul.context.SessionContext
- Direction
- zuul.stats uses zuul.context, so a change to zuul.context can break zuul.stats, while a change to zuul.stats can't break zuul.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→10 zuul uses zuul.message.http✕
- Connections
- 4 pairs of types, where a type in zuul uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.BasicRequestCompleteHandler→com.netflix.zuul.message.http.HttpRequestInfocom.netflix.zuul.BasicRequestCompleteHandler→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.RequestCompleteHandler→com.netflix.zuul.message.http.HttpRequestInfocom.netflix.zuul.RequestCompleteHandler→com.netflix.zuul.message.http.HttpResponseMessage
- Direction
- zuul uses zuul.message.http, so a change to zuul.message.http can break zuul, while a change to zuul can't break zuul.message.http.
- Position
- Below the diagonal: zuul uses a module listed above it, which is the healthy direction.
14→13 zuul uses zuul.stats✕
- Connections
- 1 pair of types, where a type in zuul uses a type in zuul.stats.
- The types involved
com.netflix.zuul.BasicRequestCompleteHandler→com.netflix.zuul.stats.RequestMetricsPublisher
- Direction
- zuul uses zuul.stats, so a change to zuul.stats can break zuul, while a change to zuul can't break zuul.stats.
- Position
- Below the diagonal: zuul uses a module listed above it, which is the healthy direction.
14→20 zuul uses zuul.filters part of a loop✕
- Connections
- 15 pairs of types, where a type in zuul uses a type in zuul.filters.
- The types involved
com.netflix.zuul.ApplyAfter→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.ApplyBefore→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.BasicFilterUsageNotifier→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.DefaultFilterFactory→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.DynamicFilterLoader→com.netflix.zuul.filters.FilterRegistrycom.netflix.zuul.DynamicFilterLoader→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.DynamicFilterLoader→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.Filter→com.netflix.zuul.filters.FilterSyncTypecom.netflix.zuul.Filter→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.FilterFactory→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.FilterLoader→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.FilterLoader→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.FilterUsageNotifier→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.StaticFilterLoader→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.StaticFilterLoader→com.netflix.zuul.filters.ZuulFilter
- Direction
- zuul uses zuul.filters, so a change to zuul.filters can break zuul, while a change to zuul can't break zuul.filters.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→29 zuul uses zuul.message part of a loop✕
- Connections
- 1 pair of types, where a type in zuul uses a type in zuul.message.
- The types involved
com.netflix.zuul.FilterConstraint→com.netflix.zuul.message.ZuulMessage
- Direction
- zuul uses zuul.message, so a change to zuul.message can break zuul, while a change to zuul can't break zuul.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→10 zuul.netty.server.push uses zuul.message.http✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.push uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.netty.server.push.PushAuthHandler→com.netflix.zuul.message.http.Cookies
- Direction
- zuul.netty.server.push uses zuul.message.http, so a change to zuul.message.http can break zuul.netty.server.push, while a change to zuul.netty.server.push can't break zuul.message.http.
- Position
- Below the diagonal: zuul.netty.server.push uses a module listed above it, which is the healthy direction.
15→38 zuul.netty.server.push uses zuul.netty.server part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.push uses a type in zuul.netty.server.
- The types involved
com.netflix.zuul.netty.server.push.PushChannelInitializer→com.netflix.zuul.netty.server.BaseZuulChannelInitializer
- Direction
- zuul.netty.server.push uses zuul.netty.server, so a change to zuul.netty.server can break zuul.netty.server.push, while a change to zuul.netty.server.push can't break zuul.netty.server.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→39 zuul.netty.server.push uses netty.common.channel.config part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.push uses a type in netty.common.channel.config.
- The types involved
com.netflix.zuul.netty.server.push.PushChannelInitializer→com.netflix.netty.common.channel.config.ChannelConfig
- Direction
- zuul.netty.server.push uses netty.common.channel.config, so a change to netty.common.channel.config can break zuul.netty.server.push, while a change to zuul.netty.server.push can't break netty.common.channel.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→9 zuul.niws uses zuul.discovery✕
- Connections
- 1 pair of types, where a type in zuul.niws uses a type in zuul.discovery.
- The types involved
com.netflix.zuul.niws.RequestAttempt→com.netflix.zuul.discovery.DiscoveryResult
- Direction
- zuul.niws uses zuul.discovery, so a change to zuul.discovery can break zuul.niws, while a change to zuul.niws can't break zuul.discovery.
- Position
- Below the diagonal: zuul.niws uses a module listed above it, which is the healthy direction.
16→27 zuul.niws uses zuul.context part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.niws uses a type in zuul.context.
- The types involved
com.netflix.zuul.niws.RequestAttempts→com.netflix.zuul.context.SessionContext
- Direction
- zuul.niws uses zuul.context, so a change to zuul.context can break zuul.niws, while a change to zuul.niws can't break zuul.context.
- 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→10 zuul.stats.status uses zuul.message.http✕
- Connections
- 1 pair of types, where a type in zuul.stats.status uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.stats.status.StatusCategoryUtils→com.netflix.zuul.message.http.HttpResponseMessage
- Direction
- zuul.stats.status uses zuul.message.http, so a change to zuul.message.http can break zuul.stats.status, while a change to zuul.stats.status can't break zuul.message.http.
- Position
- Below the diagonal: zuul.stats.status uses a module listed above it, which is the healthy direction.
17→27 zuul.stats.status uses zuul.context part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.stats.status uses a type in zuul.context.
- The types involved
com.netflix.zuul.stats.status.StatusCategoryUtils→com.netflix.zuul.context.SessionContext
- Direction
- zuul.stats.status uses zuul.context, so a change to zuul.context can break zuul.stats.status, while a change to zuul.stats.status can't break zuul.context.
- 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 zuul.stats.status uses zuul.message part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.stats.status uses a type in zuul.message.
- The types involved
com.netflix.zuul.stats.status.StatusCategoryUtils→com.netflix.zuul.message.ZuulMessage
- Direction
- zuul.stats.status uses zuul.message, so a change to zuul.message can break zuul.stats.status, while a change to zuul.stats.status can't break zuul.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→14 netty.common.proxyprotocol uses zuul✕
- Connections
- 1 pair of types, where a type in netty.common.proxyprotocol uses a type in zuul.
- The types involved
com.netflix.netty.common.proxyprotocol.HAProxyMessageChannelHandler→com.netflix.zuul.Key
- Direction
- netty.common.proxyprotocol uses zuul, so a change to zuul can break netty.common.proxyprotocol, while a change to netty.common.proxyprotocol can't break zuul.
- Position
- Below the diagonal: netty.common.proxyprotocol uses a module listed above it, which is the healthy direction.
19→17 netty.common.throttle uses zuul.stats.status✕
- Connections
- 2 pairs of types, where a type in netty.common.throttle uses a type in zuul.stats.status.
- The types involved
com.netflix.netty.common.throttle.RejectionUtils→com.netflix.zuul.stats.status.StatusCategorycom.netflix.netty.common.throttle.RequestRejectedEvent→com.netflix.zuul.stats.status.StatusCategory
- Direction
- netty.common.throttle uses zuul.stats.status, so a change to zuul.stats.status can break netty.common.throttle, while a change to netty.common.throttle can't break zuul.stats.status.
- Position
- Below the diagonal: netty.common.throttle uses a module listed above it, which is the healthy direction.
20→14 zuul.filters uses zuul✕
- Connections
- 2 pairs of types, where a type in zuul.filters uses a type in zuul.
- The types involved
com.netflix.zuul.filters.ZuulFilter→com.netflix.zuul.FilterCategorycom.netflix.zuul.filters.ZuulFilter→com.netflix.zuul.FilterConstraint
- Direction
- zuul.filters uses zuul, so a change to zuul can break zuul.filters, while a change to zuul.filters can't break zuul.
- Position
- Below the diagonal: zuul.filters uses a module listed above it, which is the healthy direction.
20→29 zuul.filters uses zuul.message part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.filters uses a type in zuul.message.
- The types involved
com.netflix.zuul.filters.ZuulFilter→com.netflix.zuul.message.ZuulMessage
- Direction
- zuul.filters uses zuul.message, so a change to zuul.message can break zuul.filters, while a change to zuul.filters can't break zuul.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→14 zuul.monitoring uses zuul✕
- Connections
- 2 pairs of types, where a type in zuul.monitoring uses a type in zuul.
- The types involved
com.netflix.zuul.monitoring.ConnCounter→com.netflix.zuul.Attrscom.netflix.zuul.monitoring.ConnTimer→com.netflix.zuul.Attrs
- Direction
- zuul.monitoring uses zuul, so a change to zuul can break zuul.monitoring, while a change to zuul.monitoring can't break zuul.
- Position
- Below the diagonal: zuul.monitoring uses a module listed above it, which is the healthy direction.
22→16 zuul.exception uses zuul.niws✕
- Connections
- 2 pairs of types, where a type in zuul.exception uses a type in zuul.niws.
- The types involved
com.netflix.zuul.exception.OutboundException→com.netflix.zuul.niws.RequestAttemptcom.netflix.zuul.exception.OutboundException→com.netflix.zuul.niws.RequestAttempts
- Direction
- zuul.exception uses zuul.niws, so a change to zuul.niws can break zuul.exception, while a change to zuul.exception can't break zuul.niws.
- Position
- Below the diagonal: zuul.exception uses a module listed above it, which is the healthy direction.
22→17 zuul.exception uses zuul.stats.status✕
- Connections
- 2 pairs of types, where a type in zuul.exception uses a type in zuul.stats.status.
- The types involved
com.netflix.zuul.exception.ErrorType→com.netflix.zuul.stats.status.StatusCategorycom.netflix.zuul.exception.OutboundErrorType→com.netflix.zuul.stats.status.StatusCategory
- Direction
- zuul.exception uses zuul.stats.status, so a change to zuul.stats.status can break zuul.exception, while a change to zuul.exception can't break zuul.stats.status.
- Position
- Below the diagonal: zuul.exception uses a module listed above it, which is the healthy direction.
22→20 zuul.exception uses zuul.filters✕
- Connections
- 1 pair of types, where a type in zuul.exception uses a type in zuul.filters.
- The types involved
com.netflix.zuul.exception.ZuulFilterConcurrencyExceededException→com.netflix.zuul.filters.ZuulFilter
- Direction
- zuul.exception uses zuul.filters, so a change to zuul.filters can break zuul.exception, while a change to zuul.exception can't break zuul.filters.
- Position
- Below the diagonal: zuul.exception uses a module listed above it, which is the healthy direction.
23→12 zuul.filters.passport uses zuul.passport✕
- Connections
- 3 pairs of types, where a type in zuul.filters.passport uses a type in zuul.passport.
- The types involved
com.netflix.zuul.filters.passport.InboundPassportStampingFilter→com.netflix.zuul.passport.PassportStatecom.netflix.zuul.filters.passport.OutboundPassportStampingFilter→com.netflix.zuul.passport.PassportStatecom.netflix.zuul.filters.passport.PassportStampingFilter→com.netflix.zuul.passport.PassportState
- Direction
- zuul.filters.passport uses zuul.passport, so a change to zuul.passport can break zuul.filters.passport, while a change to zuul.filters.passport can't break zuul.passport.
- Position
- Below the diagonal: zuul.filters.passport uses a module listed above it, which is the healthy direction.
23→20 zuul.filters.passport uses zuul.filters✕
- Connections
- 3 pairs of types, where a type in zuul.filters.passport uses a type in zuul.filters.
- The types involved
com.netflix.zuul.filters.passport.InboundPassportStampingFilter→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.filters.passport.OutboundPassportStampingFilter→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.filters.passport.PassportStampingFilter→com.netflix.zuul.filters.SyncZuulFilterAdapter
- Direction
- zuul.filters.passport uses zuul.filters, so a change to zuul.filters can break zuul.filters.passport, while a change to zuul.filters.passport can't break zuul.filters.
- Position
- Below the diagonal: zuul.filters.passport uses a module listed above it, which is the healthy direction.
24→22 zuul.netty uses zuul.exception✕
- Connections
- 2 pairs of types, where a type in zuul.netty uses a type in zuul.exception.
- The types involved
com.netflix.zuul.netty.NettyRequestAttemptFactory→com.netflix.zuul.exception.ErrorTypecom.netflix.zuul.netty.NettyRequestAttemptFactory→com.netflix.zuul.exception.OutboundException
- Direction
- zuul.netty uses zuul.exception, so a change to zuul.exception can break zuul.netty, while a change to zuul.netty can't break zuul.exception.
- Position
- Below the diagonal: zuul.netty uses a module listed above it, which is the healthy direction.
24→27 zuul.netty uses zuul.context part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.netty uses a type in zuul.context.
- The types involved
com.netflix.zuul.netty.NettyRequestAttemptFactory→com.netflix.zuul.context.SessionContext
- Direction
- zuul.netty uses zuul.context, so a change to zuul.context can break zuul.netty, while a change to zuul.netty can't break zuul.context.
- 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→5 zuul.netty.connectionpool uses netty.common.metrics✕
- Connections
- 2 pairs of types, where a type in zuul.netty.connectionpool uses a type in netty.common.metrics.
- The types involved
com.netflix.zuul.netty.connectionpool.DefaultOriginChannelInitializer→com.netflix.netty.common.metrics.HttpMetricsChannelHandlercom.netflix.zuul.netty.connectionpool.OriginChannelInitializer→com.netflix.netty.common.metrics.HttpMetricsChannelHandler
- Direction
- zuul.netty.connectionpool uses netty.common.metrics, so a change to netty.common.metrics can break zuul.netty.connectionpool, while a change to zuul.netty.connectionpool can't break netty.common.metrics.
- Position
- Below the diagonal: zuul.netty.connectionpool uses a module listed above it, which is the healthy direction.
25→8 zuul.netty.connectionpool uses zuul.resolver✕
- Connections
- 2 pairs of types, where a type in zuul.netty.connectionpool uses a type in zuul.resolver.
- The types involved
com.netflix.zuul.netty.connectionpool.DefaultClientChannelManager→com.netflix.zuul.resolver.Resolvercom.netflix.zuul.netty.connectionpool.ServerPoolListener→com.netflix.zuul.resolver.ResolverListener
- Direction
- zuul.netty.connectionpool uses zuul.resolver, so a change to zuul.resolver can break zuul.netty.connectionpool, while a change to zuul.netty.connectionpool can't break zuul.resolver.
- Position
- Below the diagonal: zuul.netty.connectionpool uses a module listed above it, which is the healthy direction.
25→9 zuul.netty.connectionpool uses zuul.discovery✕
- Connections
- 8 pairs of types, where a type in zuul.netty.connectionpool uses a type in zuul.discovery.
- The types involved
com.netflix.zuul.netty.connectionpool.BasicRequestStat→com.netflix.zuul.discovery.DiscoveryResultcom.netflix.zuul.netty.connectionpool.ClientChannelManager→com.netflix.zuul.discovery.DiscoveryResultcom.netflix.zuul.netty.connectionpool.DefaultClientChannelManager→com.netflix.zuul.discovery.DiscoveryResultcom.netflix.zuul.netty.connectionpool.DefaultClientChannelManager→com.netflix.zuul.discovery.ResolverResultcom.netflix.zuul.netty.connectionpool.PerServerConnectionPool→com.netflix.zuul.discovery.DiscoveryResultcom.netflix.zuul.netty.connectionpool.PooledConnection→com.netflix.zuul.discovery.DiscoveryResultcom.netflix.zuul.netty.connectionpool.RequestStat→com.netflix.zuul.discovery.DiscoveryResultcom.netflix.zuul.netty.connectionpool.ServerPoolListener→com.netflix.zuul.discovery.DiscoveryResult
- Direction
- zuul.netty.connectionpool uses zuul.discovery, so a change to zuul.discovery can break zuul.netty.connectionpool, while a change to zuul.netty.connectionpool can't break zuul.discovery.
- Position
- Below the diagonal: zuul.netty.connectionpool uses a module listed above it, which is the healthy direction.
25→12 zuul.netty.connectionpool uses zuul.passport✕
- Connections
- 5 pairs of types, where a type in zuul.netty.connectionpool uses a type in zuul.passport.
- The types involved
com.netflix.zuul.netty.connectionpool.ClientChannelManager→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.netty.connectionpool.DefaultClientChannelManager→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.netty.connectionpool.IConnectionPool→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.netty.connectionpool.NettyClientConnectionFactory→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.netty.connectionpool.PerServerConnectionPool→com.netflix.zuul.passport.CurrentPassport
- Direction
- zuul.netty.connectionpool uses zuul.passport, so a change to zuul.passport can break zuul.netty.connectionpool, while a change to zuul.netty.connectionpool can't break zuul.passport.
- Position
- Below the diagonal: zuul.netty.connectionpool uses a module listed above it, which is the healthy direction.
25→22 zuul.netty.connectionpool uses zuul.exception✕
- Connections
- 3 pairs of types, where a type in zuul.netty.connectionpool uses a type in zuul.exception.
- The types involved
com.netflix.zuul.netty.connectionpool.BasicRequestStat→com.netflix.zuul.exception.ErrorTypecom.netflix.zuul.netty.connectionpool.OriginConnectException→com.netflix.zuul.exception.ErrorTypecom.netflix.zuul.netty.connectionpool.RequestStat→com.netflix.zuul.exception.ErrorType
- Direction
- zuul.netty.connectionpool uses zuul.exception, so a change to zuul.exception can break zuul.netty.connectionpool, while a change to zuul.netty.connectionpool can't break zuul.exception.
- Position
- Below the diagonal: zuul.netty.connectionpool uses a module listed above it, which is the healthy direction.
25→26 zuul.netty.connectionpool uses zuul.origins part of a loop✕
- Connections
- 5 pairs of types, where a type in zuul.netty.connectionpool uses a type in zuul.origins.
- The types involved
com.netflix.zuul.netty.connectionpool.ConnectionPoolConfig→com.netflix.zuul.origins.OriginNamecom.netflix.zuul.netty.connectionpool.ConnectionPoolConfigImpl→com.netflix.zuul.origins.OriginNamecom.netflix.zuul.netty.connectionpool.ConnectionPoolHandler→com.netflix.zuul.origins.OriginNamecom.netflix.zuul.netty.connectionpool.ConnectionPoolMetrics→com.netflix.zuul.origins.OriginNamecom.netflix.zuul.netty.connectionpool.DefaultClientChannelManager→com.netflix.zuul.origins.OriginName
- Direction
- zuul.netty.connectionpool uses zuul.origins, so a change to zuul.origins can break zuul.netty.connectionpool, while a change to zuul.netty.connectionpool can't break zuul.origins.
- 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→27 zuul.netty.connectionpool uses zuul.context part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.netty.connectionpool uses a type in zuul.context.
- The types involved
com.netflix.zuul.netty.connectionpool.RequestStat→com.netflix.zuul.context.SessionContext
- Direction
- zuul.netty.connectionpool uses zuul.context, so a change to zuul.context can break zuul.netty.connectionpool, while a change to zuul.netty.connectionpool can't break zuul.context.
- 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→31 zuul.netty.connectionpool uses netty.common part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.netty.connectionpool uses a type in netty.common.
- The types involved
com.netflix.zuul.netty.connectionpool.ConnectionPoolHandler→com.netflix.netty.common.CompleteEvent
- Direction
- zuul.netty.connectionpool uses netty.common, so a change to netty.common can break zuul.netty.connectionpool, while a change to zuul.netty.connectionpool can't break netty.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→9 zuul.origins uses zuul.discovery✕
- Connections
- 2 pairs of types, where a type in zuul.origins uses a type in zuul.discovery.
- The types involved
com.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.discovery.DiscoveryResultcom.netflix.zuul.origins.NettyOrigin→com.netflix.zuul.discovery.DiscoveryResult
- Direction
- zuul.origins uses zuul.discovery, so a change to zuul.discovery can break zuul.origins, while a change to zuul.origins can't break zuul.discovery.
- Position
- Below the diagonal: zuul.origins uses a module listed above it, which is the healthy direction.
26→10 zuul.origins uses zuul.message.http✕
- Connections
- 5 pairs of types, where a type in zuul.origins uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.origins.InstrumentedOrigin→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.origins.NettyOrigin→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.origins.NettyOrigin→com.netflix.zuul.message.http.HttpResponseMessage
- Direction
- zuul.origins uses zuul.message.http, so a change to zuul.message.http can break zuul.origins, while a change to zuul.origins can't break zuul.message.http.
- Position
- Below the diagonal: zuul.origins uses a module listed above it, which is the healthy direction.
26→12 zuul.origins uses zuul.passport✕
- Connections
- 2 pairs of types, where a type in zuul.origins uses a type in zuul.passport.
- The types involved
com.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.origins.NettyOrigin→com.netflix.zuul.passport.CurrentPassport
- Direction
- zuul.origins uses zuul.passport, so a change to zuul.passport can break zuul.origins, while a change to zuul.origins can't break zuul.passport.
- Position
- Below the diagonal: zuul.origins uses a module listed above it, which is the healthy direction.
26→16 zuul.origins uses zuul.niws✕
- Connections
- 2 pairs of types, where a type in zuul.origins uses a type in zuul.niws.
- The types involved
com.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.niws.RequestAttemptcom.netflix.zuul.origins.NettyOrigin→com.netflix.zuul.niws.RequestAttempt
- Direction
- zuul.origins uses zuul.niws, so a change to zuul.niws can break zuul.origins, while a change to zuul.origins can't break zuul.niws.
- Position
- Below the diagonal: zuul.origins uses a module listed above it, which is the healthy direction.
26→17 zuul.origins uses zuul.stats.status✕
- Connections
- 1 pair of types, where a type in zuul.origins uses a type in zuul.stats.status.
- The types involved
com.netflix.zuul.origins.OriginThrottledException→com.netflix.zuul.stats.status.StatusCategory
- Direction
- zuul.origins uses zuul.stats.status, so a change to zuul.stats.status can break zuul.origins, while a change to zuul.origins can't break zuul.stats.status.
- Position
- Below the diagonal: zuul.origins uses a module listed above it, which is the healthy direction.
26→22 zuul.origins uses zuul.exception✕
- Connections
- 1 pair of types, where a type in zuul.origins uses a type in zuul.exception.
- The types involved
com.netflix.zuul.origins.OriginThrottledException→com.netflix.zuul.exception.ZuulException
- Direction
- zuul.origins uses zuul.exception, so a change to zuul.exception can break zuul.origins, while a change to zuul.origins can't break zuul.exception.
- Position
- Below the diagonal: zuul.origins uses a module listed above it, which is the healthy direction.
26→24 zuul.origins uses zuul.netty✕
- Connections
- 1 pair of types, where a type in zuul.origins uses a type in zuul.netty.
- The types involved
com.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.netty.NettyRequestAttemptFactory
- Direction
- zuul.origins uses zuul.netty, so a change to zuul.netty can break zuul.origins, while a change to zuul.origins can't break zuul.netty.
- Position
- Below the diagonal: zuul.origins uses a module listed above it, which is the healthy direction.
26→25 zuul.origins uses zuul.netty.connectionpool✕
- Connections
- 3 pairs of types, where a type in zuul.origins uses a type in zuul.netty.connectionpool.
- The types involved
com.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.netty.connectionpool.ClientChannelManagercom.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.netty.connectionpool.PooledConnectioncom.netflix.zuul.origins.NettyOrigin→com.netflix.zuul.netty.connectionpool.PooledConnection
- Direction
- zuul.origins uses zuul.netty.connectionpool, so a change to zuul.netty.connectionpool can break zuul.origins, while a change to zuul.origins can't break zuul.netty.connectionpool.
- Position
- Below the diagonal: zuul.origins uses a module listed above it, which is the healthy direction.
26→27 zuul.origins uses zuul.context part of a loop✕
- Connections
- 4 pairs of types, where a type in zuul.origins uses a type in zuul.context.
- The types involved
com.netflix.zuul.origins.BasicNettyOrigin→com.netflix.zuul.context.SessionContextcom.netflix.zuul.origins.BasicNettyOriginManager→com.netflix.zuul.context.SessionContextcom.netflix.zuul.origins.NettyOrigin→com.netflix.zuul.context.SessionContextcom.netflix.zuul.origins.OriginManager→com.netflix.zuul.context.SessionContext
- Direction
- zuul.origins uses zuul.context, so a change to zuul.context can break zuul.origins, while a change to zuul.origins can't break zuul.context.
- 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.
27→10 zuul.context uses zuul.message.http✕
- Connections
- 3 pairs of types, where a type in zuul.context uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.context.CommonContextKeys→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.context.CommonContextKeys→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.context.SessionContext→com.netflix.zuul.message.http.HttpResponseMessage
- Direction
- zuul.context uses zuul.message.http, so a change to zuul.message.http can break zuul.context, while a change to zuul.context can't break zuul.message.http.
- Position
- Below the diagonal: zuul.context uses a module listed above it, which is the healthy direction.
27→12 zuul.context uses zuul.passport✕
- Connections
- 1 pair of types, where a type in zuul.context uses a type in zuul.passport.
- The types involved
com.netflix.zuul.context.CommonContextKeys→com.netflix.zuul.passport.CurrentPassport
- Direction
- zuul.context uses zuul.passport, so a change to zuul.passport can break zuul.context, while a change to zuul.context can't break zuul.passport.
- Position
- Below the diagonal: zuul.context uses a module listed above it, which is the healthy direction.
27→16 zuul.context uses zuul.niws✕
- Connections
- 1 pair of types, where a type in zuul.context uses a type in zuul.niws.
- The types involved
com.netflix.zuul.context.CommonContextKeys→com.netflix.zuul.niws.RequestAttempts
- Direction
- zuul.context uses zuul.niws, so a change to zuul.niws can break zuul.context, while a change to zuul.context can't break zuul.niws.
- Position
- Below the diagonal: zuul.context uses a module listed above it, which is the healthy direction.
27→17 zuul.context uses zuul.stats.status✕
- Connections
- 1 pair of types, where a type in zuul.context uses a type in zuul.stats.status.
- The types involved
com.netflix.zuul.context.CommonContextKeys→com.netflix.zuul.stats.status.StatusCategory
- Direction
- zuul.context uses zuul.stats.status, so a change to zuul.stats.status can break zuul.context, while a change to zuul.context can't break zuul.stats.status.
- Position
- Below the diagonal: zuul.context uses a module listed above it, which is the healthy direction.
27→20 zuul.context uses zuul.filters✕
- Connections
- 2 pairs of types, where a type in zuul.context uses a type in zuul.filters.
- The types involved
com.netflix.zuul.context.CommonContextKeys→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.context.SessionContext→com.netflix.zuul.filters.FilterError
- Direction
- zuul.context uses zuul.filters, so a change to zuul.filters can break zuul.context, while a change to zuul.context can't break zuul.filters.
- Position
- Below the diagonal: zuul.context uses a module listed above it, which is the healthy direction.
27→26 zuul.context uses zuul.origins✕
- Connections
- 1 pair of types, where a type in zuul.context uses a type in zuul.origins.
- The types involved
com.netflix.zuul.context.ZuulSessionContextDecorator→com.netflix.zuul.origins.OriginManager
- Direction
- zuul.context uses zuul.origins, so a change to zuul.origins can break zuul.context, while a change to zuul.context can't break zuul.origins.
- Position
- Below the diagonal: zuul.context uses a module listed above it, which is the healthy direction.
28→10 zuul.netty.timeouts uses zuul.message.http✕
- Connections
- 1 pair of types, where a type in zuul.netty.timeouts uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.netty.timeouts.OriginTimeoutManager→com.netflix.zuul.message.http.HttpRequestMessage
- Direction
- zuul.netty.timeouts uses zuul.message.http, so a change to zuul.message.http can break zuul.netty.timeouts, while a change to zuul.netty.timeouts can't break zuul.message.http.
- Position
- Below the diagonal: zuul.netty.timeouts uses a module listed above it, which is the healthy direction.
28→26 zuul.netty.timeouts uses zuul.origins✕
- Connections
- 1 pair of types, where a type in zuul.netty.timeouts uses a type in zuul.origins.
- The types involved
com.netflix.zuul.netty.timeouts.OriginTimeoutManager→com.netflix.zuul.origins.NettyOrigin
- Direction
- zuul.netty.timeouts uses zuul.origins, so a change to zuul.origins can break zuul.netty.timeouts, while a change to zuul.netty.timeouts can't break zuul.origins.
- Position
- Below the diagonal: zuul.netty.timeouts uses a module listed above it, which is the healthy direction.
29→20 zuul.message uses zuul.filters✕
- Connections
- 2 pairs of types, where a type in zuul.message uses a type in zuul.filters.
- The types involved
com.netflix.zuul.message.ZuulMessage→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.message.ZuulMessageImpl→com.netflix.zuul.filters.ZuulFilter
- Direction
- zuul.message uses zuul.filters, so a change to zuul.filters can break zuul.message, while a change to zuul.message can't break zuul.filters.
- Position
- Below the diagonal: zuul.message uses a module listed above it, which is the healthy direction.
29→27 zuul.message uses zuul.context✕
- Connections
- 2 pairs of types, where a type in zuul.message uses a type in zuul.context.
- The types involved
com.netflix.zuul.message.ZuulMessage→com.netflix.zuul.context.SessionContextcom.netflix.zuul.message.ZuulMessageImpl→com.netflix.zuul.context.SessionContext
- Direction
- zuul.message uses zuul.context, so a change to zuul.context can break zuul.message, while a change to zuul.message can't break zuul.context.
- Position
- Below the diagonal: zuul.message uses a module listed above it, which is the healthy direction.
30→10 zuul.netty.insights uses zuul.message.http✕
- Connections
- 1 pair of types, where a type in zuul.netty.insights uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.netty.insights.PassportLoggingHandler→com.netflix.zuul.message.http.HttpRequestMessage
- Direction
- zuul.netty.insights uses zuul.message.http, so a change to zuul.message.http can break zuul.netty.insights, while a change to zuul.netty.insights can't break zuul.message.http.
- Position
- Below the diagonal: zuul.netty.insights uses a module listed above it, which is the healthy direction.
30→12 zuul.netty.insights uses zuul.passport✕
- Connections
- 6 pairs of types, where a type in zuul.netty.insights uses a type in zuul.passport.
- The types involved
com.netflix.zuul.netty.insights.PassportStateHttpClientHandler→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.netty.insights.PassportStateHttpServerHandler→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.netty.insights.PassportStateListener→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.netty.insights.PassportStateListener→com.netflix.zuul.passport.PassportStatecom.netflix.zuul.netty.insights.PassportStateOriginHandler→com.netflix.zuul.passport.CurrentPassportcom.netflix.zuul.netty.insights.ServerStateHandler→com.netflix.zuul.passport.CurrentPassport
- Direction
- zuul.netty.insights uses zuul.passport, so a change to zuul.passport can break zuul.netty.insights, while a change to zuul.netty.insights can't break zuul.passport.
- Position
- Below the diagonal: zuul.netty.insights uses a module listed above it, which is the healthy direction.
30→27 zuul.netty.insights uses zuul.context✕
- Connections
- 1 pair of types, where a type in zuul.netty.insights uses a type in zuul.context.
- The types involved
com.netflix.zuul.netty.insights.PassportLoggingHandler→com.netflix.zuul.context.SessionContext
- Direction
- zuul.netty.insights uses zuul.context, so a change to zuul.context can break zuul.netty.insights, while a change to zuul.netty.insights can't break zuul.context.
- Position
- Below the diagonal: zuul.netty.insights uses a module listed above it, which is the healthy direction.
31→12 netty.common uses zuul.passport✕
- Connections
- 1 pair of types, where a type in netty.common uses a type in zuul.passport.
- The types involved
com.netflix.netty.common.HttpLifecycleChannelHandler→com.netflix.zuul.passport.PassportState
- Direction
- netty.common uses zuul.passport, so a change to zuul.passport can break netty.common, while a change to netty.common can't break zuul.passport.
- Position
- Below the diagonal: netty.common uses a module listed above it, which is the healthy direction.
31→29 netty.common uses zuul.message✕
- Connections
- 1 pair of types, where a type in netty.common uses a type in zuul.message.
- The types involved
com.netflix.netty.common.ByteBufUtil→com.netflix.zuul.message.ZuulMessage
- Direction
- netty.common uses zuul.message, so a change to zuul.message can break netty.common, while a change to netty.common can't break zuul.message.
- Position
- Below the diagonal: netty.common uses a module listed above it, which is the healthy direction.
32→10 zuul.filters.http uses zuul.message.http✕
- Connections
- 4 pairs of types, where a type in zuul.filters.http uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.filters.http.HttpOutboundFilter→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.filters.http.HttpSyncEndpoint→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.filters.http.HttpSyncEndpoint→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.filters.http.ResponseState→com.netflix.zuul.message.http.HttpResponseMessage
- Direction
- zuul.filters.http uses zuul.message.http, so a change to zuul.message.http can break zuul.filters.http, while a change to zuul.filters.http can't break zuul.message.http.
- Position
- Below the diagonal: zuul.filters.http uses a module listed above it, which is the healthy direction.
32→20 zuul.filters.http uses zuul.filters✕
- Connections
- 10 pairs of types, where a type in zuul.filters.http uses a type in zuul.filters.
- The types involved
com.netflix.zuul.filters.http.HttpInboundFilter→com.netflix.zuul.filters.BaseFiltercom.netflix.zuul.filters.http.HttpInboundFilter→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.filters.http.HttpInboundSyncFilter→com.netflix.zuul.filters.BaseSyncFiltercom.netflix.zuul.filters.http.HttpInboundSyncFilter→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.filters.http.HttpOutboundFilter→com.netflix.zuul.filters.BaseFiltercom.netflix.zuul.filters.http.HttpOutboundFilter→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.filters.http.HttpOutboundSyncFilter→com.netflix.zuul.filters.BaseSyncFiltercom.netflix.zuul.filters.http.HttpOutboundSyncFilter→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.filters.http.HttpSyncEndpoint→com.netflix.zuul.filters.Endpointcom.netflix.zuul.filters.http.HttpSyncEndpoint→com.netflix.zuul.filters.SyncZuulFilter
- Direction
- zuul.filters.http uses zuul.filters, so a change to zuul.filters can break zuul.filters.http, while a change to zuul.filters.http can't break zuul.filters.
- Position
- Below the diagonal: zuul.filters.http uses a module listed above it, which is the healthy direction.
32→27 zuul.filters.http uses zuul.context✕
- Connections
- 1 pair of types, where a type in zuul.filters.http uses a type in zuul.context.
- The types involved
com.netflix.zuul.filters.http.HttpSyncEndpoint→com.netflix.zuul.context.Key
- Direction
- zuul.filters.http uses zuul.context, so a change to zuul.context can break zuul.filters.http, while a change to zuul.filters.http can't break zuul.context.
- Position
- Below the diagonal: zuul.filters.http uses a module listed above it, which is the healthy direction.
32→29 zuul.filters.http uses zuul.message✕
- Connections
- 1 pair of types, where a type in zuul.filters.http uses a type in zuul.message.
- The types involved
com.netflix.zuul.filters.http.HttpSyncEndpoint→com.netflix.zuul.message.ZuulMessage
- Direction
- zuul.filters.http uses zuul.message, so a change to zuul.message can break zuul.filters.http, while a change to zuul.filters.http can't break zuul.message.
- Position
- Below the diagonal: zuul.filters.http uses a module listed above it, which is the healthy direction.
33→10 zuul.message.util uses zuul.message.http✕
- Connections
- 2 pairs of types, where a type in zuul.message.util uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.message.util.HttpRequestBuilder→com.netflix.zuul.message.http.HttpQueryParamscom.netflix.zuul.message.util.HttpRequestBuilder→com.netflix.zuul.message.http.HttpRequestMessage
- Direction
- zuul.message.util uses zuul.message.http, so a change to zuul.message.http can break zuul.message.util, while a change to zuul.message.util can't break zuul.message.http.
- Position
- Below the diagonal: zuul.message.util uses a module listed above it, which is the healthy direction.
33→27 zuul.message.util uses zuul.context✕
- Connections
- 1 pair of types, where a type in zuul.message.util uses a type in zuul.context.
- The types involved
com.netflix.zuul.message.util.HttpRequestBuilder→com.netflix.zuul.context.SessionContext
- Direction
- zuul.message.util uses zuul.context, so a change to zuul.context can break zuul.message.util, while a change to zuul.message.util can't break zuul.context.
- Position
- Below the diagonal: zuul.message.util uses a module listed above it, which is the healthy direction.
33→29 zuul.message.util uses zuul.message✕
- Connections
- 1 pair of types, where a type in zuul.message.util uses a type in zuul.message.
- The types involved
com.netflix.zuul.message.util.HttpRequestBuilder→com.netflix.zuul.message.Headers
- Direction
- zuul.message.util uses zuul.message, so a change to zuul.message can break zuul.message.util, while a change to zuul.message.util can't break zuul.message.
- Position
- Below the diagonal: zuul.message.util uses a module listed above it, which is the healthy direction.
34→10 zuul.netty.filter uses zuul.message.http✕
- Connections
- 6 pairs of types, where a type in zuul.netty.filter uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.netty.filter.1→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.netty.filter.1→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.netty.filter.ZuulEndPointRunner→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.netty.filter.ZuulEndPointRunner→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.netty.filter.ZuulFilterChainHandler→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.netty.filter.ZuulFilterChainHandler→com.netflix.zuul.message.http.HttpResponseMessage
- Direction
- zuul.netty.filter uses zuul.message.http, so a change to zuul.message.http can break zuul.netty.filter, while a change to zuul.netty.filter can't break zuul.message.http.
- Position
- Below the diagonal: zuul.netty.filter uses a module listed above it, which is the healthy direction.
34→14 zuul.netty.filter uses zuul✕
- Connections
- 6 pairs of types, where a type in zuul.netty.filter uses a type in zuul.
- The types involved
com.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.ExecutionStatuscom.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.FilterUsageNotifiercom.netflix.zuul.netty.filter.FilterConstraints→com.netflix.zuul.FilterConstraintcom.netflix.zuul.netty.filter.ZuulEndPointRunner→com.netflix.zuul.FilterLoadercom.netflix.zuul.netty.filter.ZuulEndPointRunner→com.netflix.zuul.FilterUsageNotifiercom.netflix.zuul.netty.filter.ZuulFilterChainRunner→com.netflix.zuul.FilterUsageNotifier
- Direction
- zuul.netty.filter uses zuul, so a change to zuul can break zuul.netty.filter, while a change to zuul.netty.filter can't break zuul.
- Position
- Below the diagonal: zuul.netty.filter uses a module listed above it, which is the healthy direction.
34→17 zuul.netty.filter uses zuul.stats.status✕
- Connections
- 1 pair of types, where a type in zuul.netty.filter uses a type in zuul.stats.status.
- The types involved
com.netflix.zuul.netty.filter.ZuulFilterChainHandler→com.netflix.zuul.stats.status.StatusCategory
- Direction
- zuul.netty.filter uses zuul.stats.status, so a change to zuul.stats.status can break zuul.netty.filter, while a change to zuul.netty.filter can't break zuul.stats.status.
- Position
- Below the diagonal: zuul.netty.filter uses a module listed above it, which is the healthy direction.
34→20 zuul.netty.filter uses zuul.filters✕
- Connections
- 8 pairs of types, where a type in zuul.netty.filter uses a type in zuul.filters.
- The types involved
com.netflix.zuul.netty.filter.1→com.netflix.zuul.filters.SyncZuulFilterAdaptercom.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.filters.FilterTypecom.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.filters.SyncZuulFiltercom.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.netty.filter.FilterConstraints→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.netty.filter.ZuulEndPointRunner→com.netflix.zuul.filters.Endpointcom.netflix.zuul.netty.filter.ZuulEndPointRunner→com.netflix.zuul.filters.ZuulFiltercom.netflix.zuul.netty.filter.ZuulFilterChainRunner→com.netflix.zuul.filters.ZuulFilter
- Direction
- zuul.netty.filter uses zuul.filters, so a change to zuul.filters can break zuul.netty.filter, while a change to zuul.netty.filter can't break zuul.filters.
- Position
- Below the diagonal: zuul.netty.filter uses a module listed above it, which is the healthy direction.
34→27 zuul.netty.filter uses zuul.context✕
- Connections
- 3 pairs of types, where a type in zuul.netty.filter uses a type in zuul.context.
- The types involved
com.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.context.Keycom.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.context.SessionContextcom.netflix.zuul.netty.filter.ZuulEndPointRunner→com.netflix.zuul.context.SessionContext
- Direction
- zuul.netty.filter uses zuul.context, so a change to zuul.context can break zuul.netty.filter, while a change to zuul.netty.filter can't break zuul.context.
- Position
- Below the diagonal: zuul.netty.filter uses a module listed above it, which is the healthy direction.
34→29 zuul.netty.filter uses zuul.message✕
- Connections
- 2 pairs of types, where a type in zuul.netty.filter uses a type in zuul.message.
- The types involved
com.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.message.ZuulMessagecom.netflix.zuul.netty.filter.FilterConstraints→com.netflix.zuul.message.ZuulMessage
- Direction
- zuul.netty.filter uses zuul.message, so a change to zuul.message can break zuul.netty.filter, while a change to zuul.netty.filter can't break zuul.message.
- Position
- Below the diagonal: zuul.netty.filter uses a module listed above it, which is the healthy direction.
34→38 zuul.netty.filter uses zuul.netty.server part of a loop✕
- Connections
- 1 pair of types, where a type in zuul.netty.filter uses a type in zuul.netty.server.
- The types involved
com.netflix.zuul.netty.filter.BaseZuulFilterRunner→com.netflix.zuul.netty.server.MethodBinding
- Direction
- zuul.netty.filter uses zuul.netty.server, so a change to zuul.netty.server can break zuul.netty.filter, while a change to zuul.netty.filter can't break zuul.netty.server.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→10 zuul.util uses zuul.message.http✕
- Connections
- 2 pairs of types, where a type in zuul.util uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.util.HttpUtils→com.netflix.zuul.message.http.HttpRequestInfocom.netflix.zuul.util.ProxyUtils→com.netflix.zuul.message.http.HttpRequestMessage
- Direction
- zuul.util uses zuul.message.http, so a change to zuul.message.http can break zuul.util, while a change to zuul.util can't break zuul.message.http.
- Position
- Below the diagonal: zuul.util uses a module listed above it, which is the healthy direction.
35→29 zuul.util uses zuul.message✕
- Connections
- 4 pairs of types, where a type in zuul.util uses a type in zuul.message.
- The types involved
com.netflix.zuul.util.HttpUtils→com.netflix.zuul.message.Headerscom.netflix.zuul.util.HttpUtils→com.netflix.zuul.message.ZuulMessagecom.netflix.zuul.util.ProxyUtils→com.netflix.zuul.message.HeaderNamecom.netflix.zuul.util.ProxyUtils→com.netflix.zuul.message.Headers
- Direction
- zuul.util uses zuul.message, so a change to zuul.message can break zuul.util, while a change to zuul.util can't break zuul.message.
- Position
- Below the diagonal: zuul.util uses a module listed above it, which is the healthy direction.
36→10 zuul.filters.common uses zuul.message.http✕
- Connections
- 1 pair of types, where a type in zuul.filters.common uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.filters.common.GZipResponseFilter→com.netflix.zuul.message.http.HttpResponseMessage
- Direction
- zuul.filters.common uses zuul.message.http, so a change to zuul.message.http can break zuul.filters.common, while a change to zuul.filters.common can't break zuul.message.http.
- Position
- Below the diagonal: zuul.filters.common uses a module listed above it, which is the healthy direction.
36→29 zuul.filters.common uses zuul.message✕
- Connections
- 1 pair of types, where a type in zuul.filters.common uses a type in zuul.message.
- The types involved
com.netflix.zuul.filters.common.GZipResponseFilter→com.netflix.zuul.message.ZuulMessage
- Direction
- zuul.filters.common uses zuul.message, so a change to zuul.message can break zuul.filters.common, while a change to zuul.filters.common can't break zuul.message.
- Position
- Below the diagonal: zuul.filters.common uses a module listed above it, which is the healthy direction.
36→32 zuul.filters.common uses zuul.filters.http✕
- Connections
- 1 pair of types, where a type in zuul.filters.common uses a type in zuul.filters.http.
- The types involved
com.netflix.zuul.filters.common.GZipResponseFilter→com.netflix.zuul.filters.http.HttpOutboundSyncFilter
- Direction
- zuul.filters.common uses zuul.filters.http, so a change to zuul.filters.http can break zuul.filters.common, while a change to zuul.filters.common can't break zuul.filters.http.
- Position
- Below the diagonal: zuul.filters.common uses a module listed above it, which is the healthy direction.
36→35 zuul.filters.common uses zuul.util✕
- Connections
- 1 pair of types, where a type in zuul.filters.common uses a type in zuul.util.
- The types involved
com.netflix.zuul.filters.common.GZipResponseFilter→com.netflix.zuul.util.Gzipper
- Direction
- zuul.filters.common uses zuul.util, so a change to zuul.util can break zuul.filters.common, while a change to zuul.filters.common can't break zuul.util.
- Position
- Below the diagonal: zuul.filters.common uses a module listed above it, which is the healthy direction.
37→1 zuul.filters.endpoint uses config✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in config.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.config.DynamicIntegerSetProperty
- Direction
- zuul.filters.endpoint uses config, so a change to config can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break config.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→9 zuul.filters.endpoint uses zuul.discovery✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in zuul.discovery.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.discovery.DiscoveryResult
- Direction
- zuul.filters.endpoint uses zuul.discovery, so a change to zuul.discovery can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.discovery.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→10 zuul.filters.endpoint uses zuul.message.http✕
- Connections
- 4 pairs of types, where a type in zuul.filters.endpoint uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.filters.endpoint.MissingEndpointHandlingFilter→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.filters.endpoint.MissingEndpointHandlingFilter→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.message.http.HttpResponseMessage
- Direction
- zuul.filters.endpoint uses zuul.message.http, so a change to zuul.message.http can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.message.http.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→12 zuul.filters.endpoint uses zuul.passport✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in zuul.passport.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.passport.CurrentPassport
- Direction
- zuul.filters.endpoint uses zuul.passport, so a change to zuul.passport can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.passport.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→16 zuul.filters.endpoint uses zuul.niws✕
- Connections
- 2 pairs of types, where a type in zuul.filters.endpoint uses a type in zuul.niws.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.niws.RequestAttemptcom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.niws.RequestAttempts
- Direction
- zuul.filters.endpoint uses zuul.niws, so a change to zuul.niws can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.niws.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→17 zuul.filters.endpoint uses zuul.stats.status✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in zuul.stats.status.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.stats.status.StatusCategory
- Direction
- zuul.filters.endpoint uses zuul.stats.status, so a change to zuul.stats.status can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.stats.status.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→20 zuul.filters.endpoint uses zuul.filters✕
- Connections
- 2 pairs of types, where a type in zuul.filters.endpoint uses a type in zuul.filters.
- The types involved
com.netflix.zuul.filters.endpoint.MissingEndpointHandlingFilter→com.netflix.zuul.filters.SyncZuulFilterAdaptercom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.filters.SyncZuulFilterAdapter
- Direction
- zuul.filters.endpoint uses zuul.filters, so a change to zuul.filters can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.filters.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→22 zuul.filters.endpoint uses zuul.exception✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in zuul.exception.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.exception.ErrorType
- Direction
- zuul.filters.endpoint uses zuul.exception, so a change to zuul.exception can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.exception.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→24 zuul.filters.endpoint uses zuul.netty✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in zuul.netty.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.netty.NettyRequestAttemptFactory
- Direction
- zuul.filters.endpoint uses zuul.netty, so a change to zuul.netty can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.netty.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→25 zuul.filters.endpoint uses zuul.netty.connectionpool✕
- Connections
- 2 pairs of types, where a type in zuul.filters.endpoint uses a type in zuul.netty.connectionpool.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.netty.connectionpool.PooledConnectioncom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.netty.connectionpool.RequestStat
- Direction
- zuul.filters.endpoint uses zuul.netty.connectionpool, so a change to zuul.netty.connectionpool can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.netty.connectionpool.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→26 zuul.filters.endpoint uses zuul.origins✕
- Connections
- 4 pairs of types, where a type in zuul.filters.endpoint uses a type in zuul.origins.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.origins.NettyOrigincom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.origins.Origincom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.origins.OriginManagercom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.origins.OriginName
- Direction
- zuul.filters.endpoint uses zuul.origins, so a change to zuul.origins can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.origins.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→27 zuul.filters.endpoint uses zuul.context✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in zuul.context.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.context.SessionContext
- Direction
- zuul.filters.endpoint uses zuul.context, so a change to zuul.context can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.context.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→28 zuul.filters.endpoint uses zuul.netty.timeouts✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in zuul.netty.timeouts.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.netty.timeouts.OriginTimeoutManager
- Direction
- zuul.filters.endpoint uses zuul.netty.timeouts, so a change to zuul.netty.timeouts can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.netty.timeouts.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→29 zuul.filters.endpoint uses zuul.message✕
- Connections
- 3 pairs of types, where a type in zuul.filters.endpoint uses a type in zuul.message.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.message.HeaderNamecom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.message.Headerscom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.message.ZuulMessage
- Direction
- zuul.filters.endpoint uses zuul.message, so a change to zuul.message can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.message.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→34 zuul.filters.endpoint uses zuul.netty.filter✕
- Connections
- 1 pair of types, where a type in zuul.filters.endpoint uses a type in zuul.netty.filter.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.netty.filter.FilterRunner
- Direction
- zuul.filters.endpoint uses zuul.netty.filter, so a change to zuul.netty.filter can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.netty.filter.
- Position
- Below the diagonal: zuul.filters.endpoint uses a module listed above it, which is the healthy direction.
37→38 zuul.filters.endpoint uses zuul.netty.server part of a loop✕
- Connections
- 2 pairs of types, where a type in zuul.filters.endpoint uses a type in zuul.netty.server.
- The types involved
com.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.netty.server.MethodBindingcom.netflix.zuul.filters.endpoint.ProxyEndpoint→com.netflix.zuul.netty.server.OriginResponseReceiver
- Direction
- zuul.filters.endpoint uses zuul.netty.server, so a change to zuul.netty.server can break zuul.filters.endpoint, while a change to zuul.filters.endpoint can't break zuul.netty.server.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→2 zuul.netty.server uses netty.common.accesslog✕
- Connections
- 3 pairs of types, where a type in zuul.netty.server uses a type in netty.common.accesslog.
- The types involved
com.netflix.zuul.netty.server.BaseServerStartup→com.netflix.netty.common.accesslog.AccessLogPublishercom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.netty.common.accesslog.AccessLogPublishercom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.netty.common.accesslog.AccessLogPublisher
- Direction
- zuul.netty.server uses netty.common.accesslog, so a change to netty.common.accesslog can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.accesslog.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→3 zuul.netty.server uses netty.common.close✕
- Connections
- 2 pairs of types, where a type in zuul.netty.server uses a type in netty.common.close.
- The types involved
com.netflix.zuul.netty.server.ClientConnectionsShutdown→com.netflix.netty.common.close.CloseReasoncom.netflix.zuul.netty.server.ClientConnectionsShutdown→com.netflix.netty.common.close.ConnectionCloseEvent
- Direction
- zuul.netty.server uses netty.common.close, so a change to netty.common.close can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.close.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→5 zuul.netty.server uses netty.common.metrics✕
- Connections
- 6 pairs of types, where a type in zuul.netty.server uses a type in netty.common.metrics.
- The types involved
com.netflix.zuul.netty.server.BaseServerStartup→com.netflix.netty.common.metrics.EventLoopGroupMetricscom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.netty.common.metrics.Connectionscom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.netty.common.metrics.HttpMetricsChannelHandlercom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.netty.common.metrics.HttpRequestscom.netflix.zuul.netty.server.Server→com.netflix.netty.common.metrics.EventLoopGroupMetricscom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.netty.common.metrics.EventLoopGroupMetrics
- Direction
- zuul.netty.server uses netty.common.metrics, so a change to netty.common.metrics can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.metrics.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→6 zuul.netty.server uses netty.common.ssl✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in netty.common.ssl.
- The types involved
com.netflix.zuul.netty.server.BaseServerStartup→com.netflix.netty.common.ssl.ServerSslConfig
- Direction
- zuul.netty.server uses netty.common.ssl, so a change to netty.common.ssl can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.ssl.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→7 zuul.netty.server uses netty.common.status✕
- Connections
- 3 pairs of types, where a type in zuul.netty.server uses a type in netty.common.status.
- The types involved
com.netflix.zuul.netty.server.BaseServerStartup→com.netflix.netty.common.status.ServerStatusManagercom.netflix.zuul.netty.server.Server→com.netflix.netty.common.status.ServerStatusManagercom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.netty.common.status.ServerStatusManager
- Direction
- zuul.netty.server uses netty.common.status, so a change to netty.common.status can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.status.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→10 zuul.netty.server uses zuul.message.http✕
- Connections
- 6 pairs of types, where a type in zuul.netty.server uses a type in zuul.message.http.
- The types involved
com.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.netty.server.ClientRequestReceiver→com.netflix.zuul.message.http.HttpQueryParamscom.netflix.zuul.netty.server.ClientRequestReceiver→com.netflix.zuul.message.http.HttpRequestMessagecom.netflix.zuul.netty.server.ClientRequestReceiver→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.netty.server.ClientResponseWriter→com.netflix.zuul.message.http.HttpResponseMessagecom.netflix.zuul.netty.server.OriginResponseReceiver→com.netflix.zuul.message.http.HttpRequestMessage
- Direction
- zuul.netty.server uses zuul.message.http, so a change to zuul.message.http can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.message.http.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→11 zuul.netty.server uses zuul.netty.ssl✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in zuul.netty.ssl.
- The types involved
com.netflix.zuul.netty.server.Http1MutualSslChannelInitializer→com.netflix.zuul.netty.ssl.SslContextFactory
- Direction
- zuul.netty.server uses zuul.netty.ssl, so a change to zuul.netty.ssl can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.netty.ssl.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→14 zuul.netty.server uses zuul✕
- Connections
- 11 pairs of types, where a type in zuul.netty.server uses a type in zuul.
- The types involved
com.netflix.zuul.netty.server.BaseServerStartup→com.netflix.zuul.FilterLoadercom.netflix.zuul.netty.server.BaseServerStartup→com.netflix.zuul.FilterUsageNotifiercom.netflix.zuul.netty.server.BaseServerStartup→com.netflix.zuul.RequestCompleteHandlercom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.FilterLoadercom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.FilterUsageNotifiercom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.RequestCompleteHandlercom.netflix.zuul.netty.server.ClientResponseWriter→com.netflix.zuul.RequestCompleteHandlercom.netflix.zuul.netty.server.Server→com.netflix.zuul.Attrscom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.zuul.FilterLoadercom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.zuul.FilterUsageNotifiercom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.zuul.RequestCompleteHandler
- Direction
- zuul.netty.server uses zuul, so a change to zuul can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→15 zuul.netty.server uses zuul.netty.server.push✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in zuul.netty.server.push.
- The types involved
com.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.zuul.netty.server.push.PushConnectionRegistry
- Direction
- zuul.netty.server uses zuul.netty.server.push, so a change to zuul.netty.server.push can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.netty.server.push.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→18 zuul.netty.server uses netty.common.proxyprotocol✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in netty.common.proxyprotocol.
- The types involved
com.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.netty.common.proxyprotocol.StripUntrustedProxyHeadersHandler
- Direction
- zuul.netty.server uses netty.common.proxyprotocol, so a change to netty.common.proxyprotocol can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.proxyprotocol.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→19 zuul.netty.server uses netty.common.throttle✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in netty.common.throttle.
- The types involved
com.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.netty.common.throttle.MaxInboundConnectionsHandler
- Direction
- zuul.netty.server uses netty.common.throttle, so a change to netty.common.throttle can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.throttle.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→20 zuul.netty.server uses zuul.filters✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in zuul.filters.
- The types involved
com.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.filters.ZuulFilter
- Direction
- zuul.netty.server uses zuul.filters, so a change to zuul.filters can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.filters.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→27 zuul.netty.server uses zuul.context✕
- Connections
- 4 pairs of types, where a type in zuul.netty.server uses a type in zuul.context.
- The types involved
com.netflix.zuul.netty.server.BaseServerStartup→com.netflix.zuul.context.SessionContextDecoratorcom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.context.SessionContextDecoratorcom.netflix.zuul.netty.server.ClientRequestReceiver→com.netflix.zuul.context.SessionContextDecoratorcom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.zuul.context.SessionContextDecorator
- Direction
- zuul.netty.server uses zuul.context, so a change to zuul.context can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.context.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→29 zuul.netty.server uses zuul.message✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in zuul.message.
- The types involved
com.netflix.zuul.netty.server.ClientRequestReceiver→com.netflix.zuul.message.Headers
- Direction
- zuul.netty.server uses zuul.message, so a change to zuul.message can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.message.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→30 zuul.netty.server uses zuul.netty.insights✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in zuul.netty.insights.
- The types involved
com.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.netty.insights.PassportLoggingHandler
- Direction
- zuul.netty.server uses zuul.netty.insights, so a change to zuul.netty.insights can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.netty.insights.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→31 zuul.netty.server uses netty.common✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in netty.common.
- The types involved
com.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.netty.common.SourceAddressChannelHandler
- Direction
- zuul.netty.server uses netty.common, so a change to netty.common can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→34 zuul.netty.server uses zuul.netty.filter✕
- Connections
- 5 pairs of types, where a type in zuul.netty.server uses a type in zuul.netty.filter.
- The types involved
com.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.netty.filter.FilterConstraintscom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.netty.filter.FilterRunnercom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.netty.filter.ZuulEndPointRunnercom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.zuul.netty.filter.ZuulFilterChainRunnercom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.zuul.netty.filter.FilterConstraints
- Direction
- zuul.netty.server uses zuul.netty.filter, so a change to zuul.netty.filter can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.netty.filter.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→37 zuul.netty.server uses zuul.filters.endpoint✕
- Connections
- 1 pair of types, where a type in zuul.netty.server uses a type in zuul.filters.endpoint.
- The types involved
com.netflix.zuul.netty.server.OriginResponseReceiver→com.netflix.zuul.filters.endpoint.ProxyEndpoint
- Direction
- zuul.netty.server uses zuul.filters.endpoint, so a change to zuul.filters.endpoint can break zuul.netty.server, while a change to zuul.netty.server can't break zuul.filters.endpoint.
- Position
- Below the diagonal: zuul.netty.server uses a module listed above it, which is the healthy direction.
38→39 zuul.netty.server uses netty.common.channel.config part of a loop✕
- Connections
- 5 pairs of types, where a type in zuul.netty.server uses a type in netty.common.channel.config.
- The types involved
com.netflix.zuul.netty.server.BaseServerStartup→com.netflix.netty.common.channel.config.ChannelConfigcom.netflix.zuul.netty.server.BaseZuulChannelInitializer→com.netflix.netty.common.channel.config.ChannelConfigcom.netflix.zuul.netty.server.Http1MutualSslChannelInitializer→com.netflix.netty.common.channel.config.ChannelConfigcom.netflix.zuul.netty.server.ZuulDependencyKeys→com.netflix.netty.common.channel.config.ChannelConfigKeycom.netflix.zuul.netty.server.ZuulServerChannelInitializer→com.netflix.netty.common.channel.config.ChannelConfig
- Direction
- zuul.netty.server uses netty.common.channel.config, so a change to netty.common.channel.config can break zuul.netty.server, while a change to zuul.netty.server can't break netty.common.channel.config.
- 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.
39→6 netty.common.channel.config uses netty.common.ssl✕
- Connections
- 1 pair of types, where a type in netty.common.channel.config uses a type in netty.common.ssl.
- The types involved
com.netflix.netty.common.channel.config.CommonChannelConfigKeys→com.netflix.netty.common.ssl.ServerSslConfig
- Direction
- netty.common.channel.config uses netty.common.ssl, so a change to netty.common.ssl can break netty.common.channel.config, while a change to netty.common.channel.config can't break netty.common.ssl.
- Position
- Below the diagonal: netty.common.channel.config uses a module listed above it, which is the healthy direction.
39→11 netty.common.channel.config uses zuul.netty.ssl✕
- Connections
- 1 pair of types, where a type in netty.common.channel.config uses a type in zuul.netty.ssl.
- The types involved
com.netflix.netty.common.channel.config.CommonChannelConfigKeys→com.netflix.zuul.netty.ssl.SslContextFactory
- Direction
- netty.common.channel.config uses zuul.netty.ssl, so a change to zuul.netty.ssl can break netty.common.channel.config, while a change to netty.common.channel.config can't break zuul.netty.ssl.
- Position
- Below the diagonal: netty.common.channel.config uses a module listed above it, which is the healthy direction.
39→18 netty.common.channel.config uses netty.common.proxyprotocol✕
- Connections
- 1 pair of types, where a type in netty.common.channel.config uses a type in netty.common.proxyprotocol.
- The types involved
com.netflix.netty.common.channel.config.CommonChannelConfigKeys→com.netflix.netty.common.proxyprotocol.AllowWhen
- Direction
- netty.common.channel.config uses netty.common.proxyprotocol, so a change to netty.common.proxyprotocol can break netty.common.channel.config, while a change to netty.common.channel.config can't break netty.common.proxyprotocol.
- Position
- Below the diagonal: netty.common.channel.config uses a module listed above it, which is the healthy direction.
39→38 netty.common.channel.config uses zuul.netty.server✕
- Connections
- 1 pair of types, where a type in netty.common.channel.config uses a type in zuul.netty.server.
- The types involved
com.netflix.netty.common.channel.config.CommonChannelConfigKeys→com.netflix.zuul.netty.server.ServerTimeout
- Direction
- netty.common.channel.config uses zuul.netty.server, so a change to zuul.netty.server can break netty.common.channel.config, while a change to netty.common.channel.config can't break zuul.netty.server.
- Position
- Below the diagonal: netty.common.channel.config uses a module listed above it, which is the healthy direction.
40→3 zuul.netty.server.http2 uses netty.common.close✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.http2 uses a type in netty.common.close.
- The types involved
com.netflix.zuul.netty.server.http2.Http2StreamInitializer→com.netflix.netty.common.close.Http2ConnectionExpiryHandler
- Direction
- zuul.netty.server.http2 uses netty.common.close, so a change to netty.common.close can break zuul.netty.server.http2, while a change to zuul.netty.server.http2 can't break netty.common.close.
- Position
- Below the diagonal: zuul.netty.server.http2 uses a module listed above it, which is the healthy direction.
40→4 zuul.netty.server.http2 uses netty.common.http2✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.http2 uses a type in netty.common.http2.
- The types involved
com.netflix.zuul.netty.server.http2.Http2OrHttpHandler→com.netflix.netty.common.http2.DynamicHttp2FrameLogger
- Direction
- zuul.netty.server.http2 uses netty.common.http2, so a change to netty.common.http2 can break zuul.netty.server.http2, while a change to zuul.netty.server.http2 can't break netty.common.http2.
- Position
- Below the diagonal: zuul.netty.server.http2 uses a module listed above it, which is the healthy direction.
40→5 zuul.netty.server.http2 uses netty.common.metrics✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.http2 uses a type in netty.common.metrics.
- The types involved
com.netflix.zuul.netty.server.http2.Http2StreamInitializer→com.netflix.netty.common.metrics.Http2MetricsChannelHandlers
- Direction
- zuul.netty.server.http2 uses netty.common.metrics, so a change to netty.common.metrics can break zuul.netty.server.http2, while a change to zuul.netty.server.http2 can't break netty.common.metrics.
- Position
- Below the diagonal: zuul.netty.server.http2 uses a module listed above it, which is the healthy direction.
40→6 zuul.netty.server.http2 uses netty.common.ssl✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.http2 uses a type in netty.common.ssl.
- The types involved
com.netflix.zuul.netty.server.http2.Http2SslChannelInitializer→com.netflix.netty.common.ssl.ServerSslConfig
- Direction
- zuul.netty.server.http2 uses netty.common.ssl, so a change to netty.common.ssl can break zuul.netty.server.http2, while a change to zuul.netty.server.http2 can't break netty.common.ssl.
- Position
- Below the diagonal: zuul.netty.server.http2 uses a module listed above it, which is the healthy direction.
40→11 zuul.netty.server.http2 uses zuul.netty.ssl✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.http2 uses a type in zuul.netty.ssl.
- The types involved
com.netflix.zuul.netty.server.http2.Http2Configuration→com.netflix.zuul.netty.ssl.SslContextFactory
- Direction
- zuul.netty.server.http2 uses zuul.netty.ssl, so a change to zuul.netty.ssl can break zuul.netty.server.http2, while a change to zuul.netty.server.http2 can't break zuul.netty.ssl.
- Position
- Below the diagonal: zuul.netty.server.http2 uses a module listed above it, which is the healthy direction.
40→31 zuul.netty.server.http2 uses netty.common✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.http2 uses a type in netty.common.
- The types involved
com.netflix.zuul.netty.server.http2.Http2SslChannelInitializer→com.netflix.netty.common.SwallowSomeHttp2ExceptionsHandler
- Direction
- zuul.netty.server.http2 uses netty.common, so a change to netty.common can break zuul.netty.server.http2, while a change to zuul.netty.server.http2 can't break netty.common.
- Position
- Below the diagonal: zuul.netty.server.http2 uses a module listed above it, which is the healthy direction.
40→38 zuul.netty.server.http2 uses zuul.netty.server✕
- Connections
- 1 pair of types, where a type in zuul.netty.server.http2 uses a type in zuul.netty.server.
- The types involved
com.netflix.zuul.netty.server.http2.Http2SslChannelInitializer→com.netflix.zuul.netty.server.BaseZuulChannelInitializer
- Direction
- zuul.netty.server.http2 uses zuul.netty.server, so a change to zuul.netty.server can break zuul.netty.server.http2, while a change to zuul.netty.server.http2 can't break zuul.netty.server.
- Position
- Below the diagonal: zuul.netty.server.http2 uses a module listed above it, which is the healthy direction.
40→39 zuul.netty.server.http2 uses netty.common.channel.config✕
- Connections
- 2 pairs of types, where a type in zuul.netty.server.http2 uses a type in netty.common.channel.config.
- The types involved
com.netflix.zuul.netty.server.http2.Http2OrHttpHandler→com.netflix.netty.common.channel.config.ChannelConfigcom.netflix.zuul.netty.server.http2.Http2SslChannelInitializer→com.netflix.netty.common.channel.config.ChannelConfig
- Direction
- zuul.netty.server.http2 uses netty.common.channel.config, so a change to netty.common.channel.config can break zuul.netty.server.http2, while a change to zuul.netty.server.http2 can't break netty.common.channel.config.
- Position
- Below the diagonal: zuul.netty.server.http2 uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 17 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +8.2 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. | +8.2 pts | Low | ADR Quality |
| 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. | +7.4 pts | Medium | Architecture documentation |
| Resolve the 63 Orphaned file finding(s) in Knowledge Freshness — start with CurrentPassport.java, RequestAttempt.java, BasicNettyOrigin.java. | +5.3 pts | Medium | Knowledge Freshness |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +3.8 pts | Medium | Documentation (README) |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +3.3 pts | Medium | Deployment & Rollback |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.9 pts | Medium | Security & performance tooling |
| Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor). | +2.0 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| zuul-core/src/main/java/com/netflix/zuul/message/http/HttpRequestMessageImpl.java | 5.5 | Mixed | God Classes: TooManyMethods: HttpRequestMessageImpl |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| zuul-core/src/main/java/com/netflix/zuul/netty/server/ssl/SslHandshakeInfoHandler.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/zuul/netty/server/ClientResponseWriter.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/zuul/niws/RequestAttempt.java | 6.0 | Mixed | Explicit Debt: HackComment |
| zuul-core/src/main/java/com/netflix/zuul/filters/endpoint/ProxyEndpoint.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/netty/common/proxyprotocol/HAProxyMessageChannelHandler.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/zuul/monitoring/ConnCounter.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseServerStartup.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/zuul/netty/server/http2/Http2OrHttpHandler.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/zuul/message/http/HttpResponseMessageImpl.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/netty/common/throttle/RejectionUtils.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/main/java/com/netflix/netty/common/SourceAddressChannelHandler.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| zuul-core/src/test/java/com/netflix/netty/common/proxyprotocol/ElbProxyProtocolChannelHandlerTest.java | 6.9 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 50 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 50 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 196 of 343 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (zuul-discovery/build.gradle), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `zuul-core/src/main/java/com/netflix/netty/common/close/BaseConnectionCloseHandler.java`, `zuul-core/src/main/java/com/netflix/zuul/netty/filter/ZuulEndPointRunner.java`, `zuul-core/src/main/java/com/netflix/zuul/netty/filter/ZuulFilterChainRunner.java` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is an unrecognised JSR-330 (javax.inject / jakarta.inject) container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SslHandshakeInfoHandler.userEventTriggered at 26. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Decoder.apply at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: zuul-core/src/main/java/com/netflix/zuul/netty/server/SocketAddressProperty.java (Decoder.apply at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SslHandshakeInfoHandler.userEventTriggered (cyclomatic 26), AccessLogPublisher.log (cyclomatic 21), ZuulFilterChainRunner.filter (cyclomatic 18). — 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 4 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
13 method(s) exceeded the cognitive complexity threshold of 15; the worst was SslHandshakeInfoHandler.userEventTriggered at 56.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with SslHandshakeInfoHandler.userEventTriggered (cognitive 56), ZuulFilterChainRunner.filter (cognitive 31), ClientRequestReceiver.userEventTriggered (cognitive 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 7.6 to about 8.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
11 god class(es) detected.
What to do
- Resolve the 8 TooManyMethods finding(s) in God Classes — start with ProxyEndpoint.java, HttpRequestMessageImpl.java, SessionContext.java. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with ProxyEndpoint.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with SslHandshakeInfoHandler.java. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. A further 21 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 3 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with BaseConnectionCloseHandler.java, ServerSslConfig.java, ErrorStatsData.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with EventLoopGroupMetrics.java, Header.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with ZuulToNettyHttpHeaders.java, SourceAddressChannelHandler.java. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
5 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 85 classes have LCOM4 above 3.
D10 · Test Quality
2 skipped (2 with a documented reason), 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 686 tests.
What to do
- Resolve the 1 No assertions finding(s) in Test Quality — start with BaseZuulFilterRunnerTest.java. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 187 artifact(s) resolved, 187 of them gradable against Maven Central, and 135 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets. 3 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
0 of 25 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 6 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 4 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is zuul-core/src/jmh/java/com/netflix/zuul/netty/HeaderHandoffBenchmark.java. Counted over 135 of the 263 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
34 deducted task-comment markers across 26407 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.
What to do
- Resolve the 32 TodoComment finding(s) in Explicit Debt — start with BaseServerStartup.java (4), ElbProxyProtocolChannelHandlerTest.java (3), BaseZuulChannelInitializer.java (2). — One of this dimension's main actionable groups (32 warning-level).
- Resolve the 2 HackComment finding(s) in Explicit Debt — start with RequestAttempt.java (2). — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 1 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 4 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
49 % of calls cross a namespace and 21 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D29 · Static Analysis (SAST)
17 finding(s): 0 critical, 17 high, 0 medium, 0 low. 16 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 4 file(s) — `gradlew` (line 74, line 178), `zuul-core/src/main/java/com/netflix/netty/common/close/BaseConnectionCloseHandler.java` (line 71, line 74), `zuul-core/src/main/java/com/netflix/zuul/netty/filter/ZuulEndPointRunner.java` (line 133, line 180), `zuul-core/src/main/java/com/netflix/zuul/netty/filter/ZuulFilterChainRunner.java` (line 167) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 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 16 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 (16 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
63 of 135 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is zuul-core/src/main/java/com/netflix/zuul/passport/CurrentPassport.java. Counted over 135 of the 263 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 63 Orphaned file finding(s) in Knowledge Freshness — start with CurrentPassport.java, RequestAttempt.java, BasicNettyOrigin.java. — One of this dimension's main actionable groups (63 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: BaseServerStartup.java↔HttpHeadersTimeoutHandler.java 70%; ZuulDependencyKeys.java↔HttpHeadersTimeoutHandler.java 70%; HttpRequestMessageImpl.java↔HttpResponseMessageImpl.java 67%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with HttpRequestMessageImpl.java (2), BaseServerStartup.java, ZuulDependencyKeys.java. — One of this dimension's main actionable groups (4 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 47 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
- `ServerStartup` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (clientChannels; e.g. `clientChannels` in `chooseAddrsAndChannels` at line 99). — zuul-integration-test/src/test/java/com/netflix/zuul/integration/server/ServerStartup.java:63
What to do
- Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `HttpRequestInfo` declares 19 abstract methods: `getClientIp`, `getHeaders`, `getInfoForLogging`, `getMaxBodySize`, `getMethod`, `getOriginalHost`, `getOriginalPort`, `getOriginalProtocol`, `getOriginalScheme`, `getPath`, `getPathAndQuery`, `getPort`, `getProtocol`, `getQueryParams`, `getScheme`, `getServerName`, `parseCookies`, `reParseCookies`, `reconstructURI`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — zuul-core/src/main/java/com/netflix/zuul/message/http/HttpRequestInfo.java:28
- `ZuulMessage` declares 20 abstract methods: `bufferBodyContents`, `clone`, `disposeBufferedBody`, `finishBufferedBodyIfIncomplete`, `getBody`, `getBodyAsText`, `getBodyContents`, `getBodyLength`, `getContext`, `getHeaders`, `getInfoForLogging`, `getMaxBodySize`, `hasBody`, `hasCompleteBody`, `resetBodyReader`, `runBufferedBodyContentThroughFilter`, `setBody`, `setBodyAsText`, `setHasBody`, `setHeaders`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — zuul-core/src/main/java/com/netflix/zuul/message/ZuulMessage.java:28
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×3) — zuul-core/src/test/java/com/netflix/netty/common/proxyprotocol/ElbProxyProtocolChannelHandlerTest.java:171, zuul-core/src/test/java/com/netflix/zuul/netty/server/IoUringTest.java:63, zuul-integration-test/src/test/java/com/netflix/zuul/integration/BaseIntegrationTest.java:511
What to do
- Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (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 7 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:2
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
P6 · Release Hygiene
- The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
What to do
- Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
PF1 · Benchmark discipline
X14 · Bypassable address classification
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — zuul-core/src/main/java/com/netflix/zuul/message/http/HttpQueryParams.java:76, zuul-core/src/main/java/com/netflix/zuul/message/http/HttpQueryParams.java:93, zuul-core/src/main/java/com/netflix/netty/common/metrics/InstrumentedResourceLeakDetector.java:74
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
X5 · Nullable reference types
- 0/52 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 66% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 82% | Strong | Solid. |
| Maturity | 49% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by P3, P4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, 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
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (44 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- 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 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X26 Unsynchronised callback handoff — 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 106 finding(s)
- TodoComment zuul-discovery/src/main/java/com/netflix/zuul/resolver/Resolver.java:35
- TodoComment zuul-discovery/src/main/java/com/netflix/zuul/discovery/DynamicServerResolver.java:106
- TodoComment zuul-discovery/src/main/java/com/netflix/zuul/discovery/ResolverResult.java:27
- TodoComment zuul-core/src/test/java/com/netflix/zuul/netty/connectionpool/DefaultClientChannelManagerTest.java:187
- TodoComment zuul-core/src/test/java/com/netflix/netty/common/proxyprotocol/ElbProxyProtocolChannelHandlerTest.java:248
- TodoComment zuul-core/src/test/java/com/netflix/netty/common/proxyprotocol/ElbProxyProtocolChannelHandlerTest.java:284
- TodoComment zuul-core/src/test/java/com/netflix/netty/common/proxyprotocol/ElbProxyProtocolChannelHandlerTest.java:349
- TodoComment zuul-core/src/main/java/com/netflix/zuul/util/HttpUtils.java:117
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/ssl/BaseSslContextFactory.java:122
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseZuulChannelInitializer.java:140
- TodoComment zuul-core/src/main/java/com/netflix/zuul/context/ZuulSessionContextDecorator.java:63
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseServerStartup.java:128
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseServerStartup.java:345
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseServerStartup.java:355
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseServerStartup.java:365
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseZuulChannelInitializer.java:390
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/ClientResponseWriter.java:201
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/ssl/SslHandshakeInfoHandler.java:242
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/psk/ZuulPskServer.java:116
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/http2/Http2ContentLengthEnforcingHandler.java:92
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/server/http2/Http2OrHttpHandler.java:126
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/connectionpool/ConnectionPoolConfigImpl.java:40
- TodoComment zuul-core/src/main/java/com/netflix/zuul/netty/connectionpool/DefaultClientChannelManager.java:229
- TodoComment zuul-core/src/main/java/com/netflix/zuul/monitoring/ConnCounter.java:96
- TodoComment zuul-core/src/main/java/com/netflix/zuul/monitoring/ConnTimer.java:52
- TooManyMethods: ProxyEndpoint zuul-core/src/main/java/com/netflix/zuul/filters/endpoint/ProxyEndpoint.java:113
- TooManyMethods: HttpRequestMessageImpl zuul-core/src/main/java/com/netflix/zuul/message/http/HttpRequestMessageImpl.java:51
- TooManyMethods: SessionContext zuul-core/src/main/java/com/netflix/zuul/context/SessionContext.java:44
- TooManyMethods: RequestAttempt zuul-core/src/main/java/com/netflix/zuul/niws/RequestAttempt.java:40
- TooManyMethods: HttpResponseMessageImpl zuul-core/src/main/java/com/netflix/zuul/message/http/HttpResponseMessageImpl.java:37
- TooManyMethods: DiscoveryResult zuul-discovery/src/main/java/com/netflix/zuul/discovery/DiscoveryResult.java:37
- TooManyMethods: ZuulToNettyHttpHeaders zuul-core/src/main/java/com/netflix/zuul/netty/ZuulToNettyHttpHeaders.java:42
- TooManyMethods: CurrentPassport zuul-core/src/main/java/com/netflix/zuul/passport/CurrentPassport.java:44
- Change coupling: BaseServerStartup.java ↔ HttpHeadersTimeoutHandler.java zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseServerStartup.java:1
- Change coupling: ZuulDependencyKeys.java ↔ HttpHeadersTimeoutHandler.java zuul-core/src/main/java/com/netflix/zuul/netty/server/ZuulDependencyKeys.java:1
- Change coupling: HttpRequestMessageImpl.java ↔ HttpResponseMessageImpl.java zuul-core/src/main/java/com/netflix/zuul/message/http/HttpRequestMessageImpl.java:1
- Change coupling: HttpRequestMessageImpl.java ↔ PushAuthHandler.java zuul-core/src/main/java/com/netflix/zuul/message/http/HttpRequestMessageImpl.java:1
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (12 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/close/BaseConnectionCloseHandler.java:120
- Edited copy of a member (12 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/ssl/ServerSslConfig.java:102
- Edited copy of a member (12 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/stats/ErrorStatsData.java:42
- Swallowed exception (empty catch) zuul-core/src/main/java/com/netflix/zuul/message/http/HttpQueryParams.java:76
- Swallowed exception (empty catch) zuul-core/src/main/java/com/netflix/zuul/message/http/HttpQueryParams.java:93
- Swallowed exception (empty catch) zuul-core/src/main/java/com/netflix/netty/common/metrics/InstrumentedResourceLeakDetector.java:74
- HackComment zuul-core/src/main/java/com/netflix/zuul/niws/RequestAttempt.java:96
- HackComment zuul-core/src/main/java/com/netflix/zuul/niws/RequestAttempt.java:148
- REDACTED
- REDACTED
- Edited copy of a member (7 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/metrics/EventLoopGroupMetrics.java:46
- Edited copy of a member (7 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/message/Header.java:26
- Edited copy of a member (10 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/netty/ZuulToNettyHttpHeaders.java:100
- Edited copy of a member (10 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/SourceAddressChannelHandler.java:160
- Edited copy of a member (9 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/util/VipUtils.java:20
- Edited copy of a member (9 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/Attrs.java:63
- Stateful singleton: ServerStartup zuul-integration-test/src/test/java/com/netflix/zuul/integration/server/ServerStartup.java:63
- SslHandshakeInfoHandler.userEventTriggered (cyclomatic 26) zuul-core/src/main/java/com/netflix/zuul/netty/server/ssl/SslHandshakeInfoHandler.java:98
- AccessLogPublisher.log (cyclomatic 21) zuul-core/src/main/java/com/netflix/netty/common/accesslog/AccessLogPublisher.java:56
- ZuulFilterChainRunner.filter (cyclomatic 18) zuul-core/src/main/java/com/netflix/zuul/netty/filter/ZuulFilterChainRunner.java:72
- ClientRequestReceiver.userEventTriggered (cyclomatic 16) zuul-core/src/main/java/com/netflix/zuul/netty/server/ClientRequestReceiver.java:231
- No assertions: onCompleteThrows zuul-core/src/test/java/com/netflix/zuul/netty/filter/BaseZuulFilterRunnerTest.java:145
- SslHandshakeInfoHandler.userEventTriggered (cognitive 56) zuul-core/src/main/java/com/netflix/zuul/netty/server/ssl/SslHandshakeInfoHandler.java:98
- ZuulFilterChainRunner.filter (cognitive 31) zuul-core/src/main/java/com/netflix/zuul/netty/filter/ZuulFilterChainRunner.java:72
- ClientRequestReceiver.userEventTriggered (cognitive 31) zuul-core/src/main/java/com/netflix/zuul/netty/server/ClientRequestReceiver.java:231
- ClientResponseWriter.channelRead (cognitive 23) zuul-core/src/main/java/com/netflix/zuul/netty/server/ClientResponseWriter.java:90
- ClientResponseWriter.userEventTriggered (cognitive 22) zuul-core/src/main/java/com/netflix/zuul/netty/server/ClientResponseWriter.java:211
- RequestAttempt.setException (cognitive 22) zuul-core/src/main/java/com/netflix/zuul/niws/RequestAttempt.java:305
- Http2OrHttpHandler.userEventTriggered (cognitive 21) zuul-core/src/main/java/com/netflix/zuul/netty/server/http2/Http2OrHttpHandler.java:99
- PushMessageSender.channelRead0 (cognitive 21) zuul-core/src/main/java/com/netflix/zuul/netty/server/push/PushMessageSender.java:81
- AccessLogPublisher.log (cognitive 20) zuul-core/src/main/java/com/netflix/netty/common/accesslog/AccessLogPublisher.java:56
- PassportLoggingHandler.logPassport (cognitive 20) zuul-core/src/main/java/com/netflix/zuul/netty/insights/PassportLoggingHandler.java:77
- ZuulResponseFilter.apply (cognitive 17) zuul-sample/src/main/java/com/netflix/zuul/sample/filters/outbound/ZuulResponseFilter.java:64
- OriginResponseReceiver.userEventTriggered (cognitive 16) zuul-core/src/main/java/com/netflix/zuul/netty/server/OriginResponseReceiver.java:117
- CurrentPassport.parseFromToString (cognitive 16) zuul-core/src/main/java/com/netflix/zuul/passport/CurrentPassport.java:389
- FileTooLong: endpoint/ProxyEndpoint.java zuul-core/src/main/java/com/netflix/zuul/filters/endpoint/ProxyEndpoint.java
- MethodTooLong: SslHandshakeInfoHandler.userEventTriggered zuul-core/src/main/java/com/netflix/zuul/netty/server/ssl/SslHandshakeInfoHandler.java:98
- ClassTooLong: HttpRequestMessageImpl zuul-core/src/main/java/com/netflix/zuul/message/http/HttpRequestMessageImpl.java:51
- REDACTED
- Edited copy of a member (28 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/proxyprotocol/HAProxyMessageChannelHandler.java:81
- Edited copy of a member (26 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/netty/filter/BaseZuulFilterRunner.java:137
- Edited copy of a member (17 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/message/http/HttpQueryParams.java:183
- Edited copy of a member (21 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/throttle/RejectionUtils.java:68
- Edited copy of a member (23 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/netty/server/http2/Http2Configuration.java:28
- Edited copies of one member (3 members, 13+ corresponding lines) zuul-core/src/main/java/com/netflix/zuul/passport/CurrentPassport.java:233
- Edited copy of a member (11 corresponding lines) zuul-core/src/main/java/com/netflix/zuul/monitoring/ConnCounter.java:76
- Edited copy of a member (18 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/metrics/HttpBodySizeRecordingChannelHandler.java:62
- Edited copies of one member (3 members, 16+ corresponding lines) zuul-core/src/main/java/com/netflix/zuul/netty/server/Server.java:479
- Edited copy of a member (15 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/SslExceptionsHandler.java:44
- Edited copy of a member (8 corresponding lines) zuul-core/src/main/java/com/netflix/netty/common/close/BaseConnectionCloseHandler.java:134
- Edited copy of a member (5 corresponding lines) zuul-sample/src/main/java/com/netflix/zuul/sample/push/SampleSSEPushChannelInitializer.java:39
- Duplicated block (24 lines × 2) zuul-core/src/main/java/com/netflix/zuul/netty/server/BaseServerStartup.java:161
- Duplicated block (19 lines × 2) zuul-core/src/main/java/com/netflix/zuul/netty/filter/BaseZuulFilterRunner.java:144
- Duplicated block (10–12 lines × 2) zuul-core/src/main/java/com/netflix/zuul/netty/server/ClientRequestReceiver.java:452
- Duplicated block (11 lines × 2) zuul-sample/src/main/java/com/netflix/zuul/sample/SampleServerStartup.java:223
- Duplicated block (9 lines × 2) zuul-core/src/main/java/com/netflix/zuul/message/http/HttpQueryParams.java:193
- Duplicated block (7 lines × 2) zuul-core/src/main/java/com/netflix/zuul/monitoring/ConnCounter.java:68
- Duplicated block (5 lines × 2) zuul-core/src/main/java/com/netflix/zuul/monitoring/ConnCounter.java:100
- No deployment automation
Minor — 82 finding(s)
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/passport/CurrentPassport.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/niws/RequestAttempt.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/origins/BasicNettyOrigin.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/server/psk/ZuulPskServer.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/server/push/PushMessageSender.java:1
- Orphaned file zuul-discovery/src/main/java/com/netflix/zuul/discovery/DiscoveryResult.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/insights/PassportLoggingHandler.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/connectionpool/PooledConnection.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/netty/common/proxyprotocol/HAProxyMessageChannelHandler.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/StaticFilterLoader.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/server/SocketAddressProperty.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/origins/OriginName.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/filters/common/GZipResponseFilter.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/timeouts/HttpHeadersTimeoutHandler.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/message/http/HttpHeaderNames.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/netty/common/metrics/Http2MetricsChannelHandlers.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/netty/common/accesslog/AccessLogChannelHandler.java:1
- Orphaned file zuul-core/src/jmh/java/com/netflix/zuul/message/HeadersBenchmark.java:1
- Orphaned file zuul-processor/src/main/java/com/netflix/zuul/filters/processor/FilterProcessor.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/server/push/PushAuthHandler.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/insights/ServerStateHandler.java:1
- Orphaned file zuul-discovery/src/main/java/com/netflix/zuul/discovery/DynamicServerResolver.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/message/ZuulMessage.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/netty/server/push/PushProtocol.java:1
- Orphaned file zuul-core/src/main/java/com/netflix/zuul/monitoring/ConnTimer.java:1
- Disabled test zuul-core/src/test/java/com/netflix/netty/common/proxyprotocol/ElbProxyProtocolChannelHandlerTest.java:171
- Disabled test zuul-core/src/test/java/com/netflix/zuul/netty/server/IoUringTest.java:63
- Disabled test zuul-integration-test/src/test/java/com/netflix/zuul/integration/BaseIntegrationTest.java:511
- Fat interface: HttpRequestInfo (19 abstract methods) zuul-core/src/main/java/com/netflix/zuul/message/http/HttpRequestInfo.java:28
- Fat interface: ZuulMessage (20 abstract methods) zuul-core/src/main/java/com/netflix/zuul/message/ZuulMessage.java:28
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Documentation: no build, run or usage example README.md:1
- No ADRs found zuul-integration-test/build.gradle:2
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:2
- Changelog looks stale/thin
- Duplicated predicate zuul-core/src/main/java/com/netflix/zuul/netty/server/push/PushClientProtocolHandler.java:31
- Java packages are not null-marked everywhere
Minor — 137 finding(s)
- Outdated (compile): org.projectlombok:lombok
- Outdated (compile): com.uber.nullaway:nullaway
- Outdated (compile): org.checkerframework:dataflow-nullaway
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.guava:guava
- Outdated (compile): org.jspecify:jspecify
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.errorprone:error_prone_core
- Outdated (compile): com.google.errorprone:error_prone_annotation
- Outdated (compile): com.google.errorprone:error_prone_check_api
- Outdated (compile): io.github.eisop:dataflow-errorprone
- Outdated (compile): io.github.java-diff-utils:java-diff-utils
- Outdated (compile): com.google.auto.value:auto-value-annotations
- Outdated (compile): com.github.ben-manes.caffeine:caffeine
- Outdated (compile): com.google.googlejavaformat:google-java-format
- Outdated (compile): org.pcollections:pcollections
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): com.google.auto.service:auto-service-annotations
- Outdated (compile): org.slf4j:slf4j-api
- Outdated (compile): com.fasterxml.jackson.core:jackson-databind
- Outdated (compile): com.netflix.ribbon:ribbon-core
- Outdated (compile): com.netflix.ribbon:ribbon-archaius
- Outdated (compile): io.netty:netty-bom
- Outdated (compile): com.fasterxml.jackson.core:jackson-annotations
- Outdated (compile): com.fasterxml.jackson.core:jackson-core
- Skipped (documented): detectsSplitPpv1Message zuul-core/src/test/java/com/netflix/netty/common/proxyprotocol/ElbProxyProtocolChannelHandlerTest.java:173
- Skipped (documented): ipv6AddressScopeNameRemoved zuul-core/src/test/java/com/netflix/netty/common/SourceAddressChannelHandlerTest.java:88
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-417a0597ec1a4d4c8ab3149d89f013f1/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-417a0597ec1a4d4c8ab3149d89f013f1/tree.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `zuul-core/src/main/java/com/netflix/netty/common/close/BaseConnectionCloseHandler.java`, `zuul-core/src/main/java/com/netflix/zuul/netty/filter/ZuulEndPointRunner.java`, `zuul-core/src/main/java/com/netflix/zuul/netty/filter/ZuulFilterChainRunner.java` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |