Executive summary
twitter/finatra falls short of our standard for production because 83 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 63 out of 100 and is rated Adequate, and all four of its critical findings are security problems in the build pipeline.
Maturity, at 56, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Having someone learn and document the 83 files no active contributor knows comes next, also worth about 7. Raising Maturity to 70 would lift the score to about 69.
Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 21,757 lines, about €65,000 to rebuild.
If Maturity rose from 56 to 70, the lowest score rated Strong, the score would rise from 63 to about 69.
New since the last survey: 9 findings
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) http-core/src/main/scala/com/twitter/finatra/http/jsonpatch/JsonPatchOperator.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) validation/src/main/scala/com/twitter/finatra/validation/constraints/CountryCodeConstraintValidator.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) http-core/src/main/scala/com/twitter/finatra/http/marshalling/MessageBodyManager.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) inject/inject-slf4j/src/main/scala/com/twitter/inject/Logging.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) thrift/src/main/scala/com/twitter/finatra/thrift/filters/ExceptionMappingFilter.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) validation/src/main/scala/com/twitter/finatra/validation/constraints/AssertFalseConstraintValidator.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) examples/injectable-twitter-server/java/src/main/java/com/twitter/finatra/example/Publisher.java
- Code Duplication · Edited copy of a member (5 corresponding lines) examples/injectable-twitter-server/java/src/main/java/com/twitter/finatra/example/Publisher.java
Fixed since the last survey: 1 finding
- Secrets (history) · Secret: twitter-api-key doc/src/sphinx/user-guide/validation/index.rst
Rebuild cost: about €65,000 · Estimate
| Cost to rebuild | €22,000 to €110,000, for 359 to 1,138 hours of work, about 0.4 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.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 21,757 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 ch.qos.logback.core | 2 com.twitter.finatra.filters | 3 com.twitter.finatra.http.contexts | 4 com.twitter.finatra.http.fileupload | 5 com.twitter.finatra.http.internal.routing | 6 com.twitter.finatra.thrift.exceptions | 7 com.twitter.finatra.utils | 8 com.twitter.finatra.validation | 9 com.twitter.inject | 10 com.twitter.inject.exceptions | 11 com.twitter.inject.thrift | 12 com.twitter.finatra.http.exceptions | 13 com.twitter.finatra.http.filters | 14 com.twitter.finatra.http.marshalling | 15 com.twitter.finatra.http.request | 16 com.twitter.finatra.http.routing | 17 com.twitter.finatra.modules | 18 com.twitter.finatra.mustache.marshalling | 19 com.twitter.finatra.mustache.modules | 20 com.twitter.finatra.thrift.modules | 21 com.twitter.finatra.thrift.routing | 22 com.twitter.inject.app.internal | 23 com.twitter.inject.modules | 24 com.twitter.finatra.http.jsonpatch | 25 com.twitter.finatra.http.marshalling.MessageBodyManager | 26 com.twitter.finatra.http.marshalling.WriterResponse | 27 com.twitter.finatra.http.marshalling.modules | 28 com.twitter.finatra.http.modules | 29 com.twitter.finatra.http.response | 30 com.twitter.finatra.httpclient.modules | 31 com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder | 32 com.twitter.finatra.mysql.client.modules | 33 com.twitter.inject.app | 34 com.twitter.inject.thrift.modules | 35 com.twitter.finatra.http.internal.exceptions | 36 com.twitter.finatra.http.internal.exceptions.json | 37 com.twitter.finatra.http.marshalling.response | 38 com.twitter.inject.server | 39 com.twitter.finatra.http | 40 com.twitter.finatra.thrift |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ch.qos.logback.core | ||||||||||||||||||||||||||||||||||||||||
| 2 com.twitter.finatra.filters | ||||||||||||||||||||||||||||||||||||||||
| 3 com.twitter.finatra.http.contexts | ||||||||||||||||||||||||||||||||||||||||
| 4 com.twitter.finatra.http.fileupload | ||||||||||||||||||||||||||||||||||||||||
| 5 com.twitter.finatra.http.internal.routing | ||||||||||||||||||||||||||||||||||||||||
| 6 com.twitter.finatra.thrift.exceptions | ||||||||||||||||||||||||||||||||||||||||
| 7 com.twitter.finatra.utils | ||||||||||||||||||||||||||||||||||||||||
| 8 com.twitter.finatra.validation | ||||||||||||||||||||||||||||||||||||||||
| 9 com.twitter.inject | ||||||||||||||||||||||||||||||||||||||||
| 10 com.twitter.inject.exceptions | ||||||||||||||||||||||||||||||||||||||||
| 11 com.twitter.inject.thrift | ||||||||||||||||||||||||||||||||||||||||
| 12 com.twitter.finatra.http.exceptions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 com.twitter.finatra.http.filters | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 com.twitter.finatra.http.marshalling | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 com.twitter.finatra.http.request | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 com.twitter.finatra.http.routing | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 com.twitter.finatra.modules | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 com.twitter.finatra.mustache.marshalling | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 com.twitter.finatra.mustache.modules | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 com.twitter.finatra.thrift.modules | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 com.twitter.finatra.thrift.routing | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 com.twitter.inject.app.internal | 6 | |||||||||||||||||||||||||||||||||||||||
| 23 com.twitter.inject.modules | 6 | |||||||||||||||||||||||||||||||||||||||
| 24 com.twitter.finatra.http.jsonpatch | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 com.twitter.finatra.http.marshalling.MessageBodyManager | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 26 com.twitter.finatra.http.marshalling.WriterResponse | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 com.twitter.finatra.http.marshalling.modules | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 com.twitter.finatra.http.modules | 6 | 3 | ||||||||||||||||||||||||||||||||||||||
| 29 com.twitter.finatra.http.response | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 30 com.twitter.finatra.httpclient.modules | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 com.twitter.finatra.mysql.client.modules | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 com.twitter.inject.app | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 com.twitter.inject.thrift.modules | 10 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 com.twitter.finatra.http.internal.exceptions | 4 | 7 | ||||||||||||||||||||||||||||||||||||||
| 36 com.twitter.finatra.http.internal.exceptions.json | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 com.twitter.finatra.http.marshalling.response | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 com.twitter.inject.server | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 com.twitter.finatra.http | 1 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 40 com.twitter.finatra.thrift | 1 | 1 | 3 | 2 |
12→3 com.twitter.finatra.http.exceptions uses com.twitter.finatra.http.contexts✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.exceptions uses a type in com.twitter.finatra.http.contexts.
- The types involved
com.twitter.finatra.http.exceptions.ExceptionManager→com.twitter.finatra.http.contexts.RouteInfo
- Direction
- com.twitter.finatra.http.exceptions uses com.twitter.finatra.http.contexts, so a change to com.twitter.finatra.http.contexts can break com.twitter.finatra.http.exceptions, while a change to com.twitter.finatra.http.exceptions can't break com.twitter.finatra.http.contexts.
- Position
- Below the diagonal: com.twitter.finatra.http.exceptions uses a module listed above it, which is the healthy direction.
12→10 com.twitter.finatra.http.exceptions uses com.twitter.inject.exceptions✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.exceptions uses a type in com.twitter.inject.exceptions.
- The types involved
com.twitter.finatra.http.exceptions.HttpResponseException→com.twitter.inject.exceptions.NonRetryableException
- Direction
- com.twitter.finatra.http.exceptions uses com.twitter.inject.exceptions, so a change to com.twitter.inject.exceptions can break com.twitter.finatra.http.exceptions, while a change to com.twitter.finatra.http.exceptions can't break com.twitter.inject.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.http.exceptions uses a module listed above it, which is the healthy direction.
13→2 com.twitter.finatra.http.filters uses com.twitter.finatra.filters✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.filters uses a type in com.twitter.finatra.filters.
- The types involved
com.twitter.finatra.http.filters.CommonFilters→com.twitter.finatra.filters.MergedFilter
- Direction
- com.twitter.finatra.http.filters uses com.twitter.finatra.filters, so a change to com.twitter.finatra.filters can break com.twitter.finatra.http.filters, while a change to com.twitter.finatra.http.filters can't break com.twitter.finatra.filters.
- Position
- Below the diagonal: com.twitter.finatra.http.filters uses a module listed above it, which is the healthy direction.
14→9 com.twitter.finatra.http.marshalling uses com.twitter.inject✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.marshalling uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.http.marshalling.MessageBodyManager→com.twitter.inject.Injector
- Direction
- com.twitter.finatra.http.marshalling uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.http.marshalling, while a change to com.twitter.finatra.http.marshalling can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.http.marshalling uses a module listed above it, which is the healthy direction.
15→4 com.twitter.finatra.http.request uses com.twitter.finatra.http.fileupload✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.request uses a type in com.twitter.finatra.http.fileupload.
- The types involved
com.twitter.finatra.http.request.RequestUtils→com.twitter.finatra.http.fileupload.MultipartItem
- Direction
- com.twitter.finatra.http.request uses com.twitter.finatra.http.fileupload, so a change to com.twitter.finatra.http.fileupload can break com.twitter.finatra.http.request, while a change to com.twitter.finatra.http.request can't break com.twitter.finatra.http.fileupload.
- Position
- Below the diagonal: com.twitter.finatra.http.request uses a module listed above it, which is the healthy direction.
16→5 com.twitter.finatra.http.routing uses com.twitter.finatra.http.internal.routing✕
- Connections
- 3 pairs of types, where a type in com.twitter.finatra.http.routing uses a type in com.twitter.finatra.http.internal.routing.
- The types involved
com.twitter.finatra.http.routing.AdminHttpRouter→com.twitter.finatra.http.internal.routing.Routecom.twitter.finatra.http.routing.Registrar→com.twitter.finatra.http.internal.routing.Routecom.twitter.finatra.http.routing.RoutesByType→com.twitter.finatra.http.internal.routing.Route
- Direction
- com.twitter.finatra.http.routing uses com.twitter.finatra.http.internal.routing, so a change to com.twitter.finatra.http.internal.routing can break com.twitter.finatra.http.routing, while a change to com.twitter.finatra.http.routing can't break com.twitter.finatra.http.internal.routing.
- Position
- Below the diagonal: com.twitter.finatra.http.routing uses a module listed above it, which is the healthy direction.
17→7 com.twitter.finatra.modules uses com.twitter.finatra.utils✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.modules uses a type in com.twitter.finatra.utils.
- The types involved
com.twitter.finatra.modules.CredentialsModule→com.twitter.finatra.utils.Credentialscom.twitter.finatra.modules.FileResolverModule→com.twitter.finatra.utils.FileResolver
- Direction
- com.twitter.finatra.modules uses com.twitter.finatra.utils, so a change to com.twitter.finatra.utils can break com.twitter.finatra.modules, while a change to com.twitter.finatra.modules can't break com.twitter.finatra.utils.
- Position
- Below the diagonal: com.twitter.finatra.modules uses a module listed above it, which is the healthy direction.
17→9 com.twitter.finatra.modules uses com.twitter.inject✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.modules.CredentialsModule→com.twitter.inject.TwitterModulecom.twitter.finatra.modules.FileResolverModule→com.twitter.inject.TwitterModule
- Direction
- com.twitter.finatra.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.modules, while a change to com.twitter.finatra.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.modules uses a module listed above it, which is the healthy direction.
18→7 com.twitter.finatra.mustache.marshalling uses com.twitter.finatra.utils✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.mustache.marshalling uses a type in com.twitter.finatra.utils.
- The types involved
com.twitter.finatra.mustache.marshalling.LocalFilesystemMustacheFactory→com.twitter.finatra.utils.FileResolvercom.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder→com.twitter.finatra.utils.FileResolver
- Direction
- com.twitter.finatra.mustache.marshalling uses com.twitter.finatra.utils, so a change to com.twitter.finatra.utils can break com.twitter.finatra.mustache.marshalling, while a change to com.twitter.finatra.mustache.marshalling can't break com.twitter.finatra.utils.
- Position
- Below the diagonal: com.twitter.finatra.mustache.marshalling uses a module listed above it, which is the healthy direction.
19→7 com.twitter.finatra.mustache.modules uses com.twitter.finatra.utils✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.mustache.modules uses a type in com.twitter.finatra.utils.
- The types involved
com.twitter.finatra.mustache.modules.MustacheFactoryModule→com.twitter.finatra.utils.FileResolver
- Direction
- com.twitter.finatra.mustache.modules uses com.twitter.finatra.utils, so a change to com.twitter.finatra.utils can break com.twitter.finatra.mustache.modules, while a change to com.twitter.finatra.mustache.modules can't break com.twitter.finatra.utils.
- Position
- Below the diagonal: com.twitter.finatra.mustache.modules uses a module listed above it, which is the healthy direction.
19→9 com.twitter.finatra.mustache.modules uses com.twitter.inject✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.mustache.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.mustache.modules.MustacheFactoryModule→com.twitter.inject.TwitterModulecom.twitter.finatra.mustache.modules.MustacheFlagsModule→com.twitter.inject.TwitterModule
- Direction
- com.twitter.finatra.mustache.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.mustache.modules, while a change to com.twitter.finatra.mustache.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.mustache.modules uses a module listed above it, which is the healthy direction.
20→6 com.twitter.finatra.thrift.modules uses com.twitter.finatra.thrift.exceptions✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.thrift.modules uses a type in com.twitter.finatra.thrift.exceptions.
- The types involved
com.twitter.finatra.thrift.modules.ExceptionManagerModule→com.twitter.finatra.thrift.exceptions.ExceptionManager
- Direction
- com.twitter.finatra.thrift.modules uses com.twitter.finatra.thrift.exceptions, so a change to com.twitter.finatra.thrift.exceptions can break com.twitter.finatra.thrift.modules, while a change to com.twitter.finatra.thrift.modules can't break com.twitter.finatra.thrift.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.thrift.modules uses a module listed above it, which is the healthy direction.
20→9 com.twitter.finatra.thrift.modules uses com.twitter.inject✕
- Connections
- 3 pairs of types, where a type in com.twitter.finatra.thrift.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.thrift.modules.ExceptionManagerModule→com.twitter.inject.Injectorcom.twitter.finatra.thrift.modules.ExceptionManagerModule→com.twitter.inject.TwitterModulecom.twitter.finatra.thrift.modules.ThriftResponseClassifierModule→com.twitter.inject.TwitterModule
- Direction
- com.twitter.finatra.thrift.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.thrift.modules, while a change to com.twitter.finatra.thrift.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.thrift.modules uses a module listed above it, which is the healthy direction.
21→6 com.twitter.finatra.thrift.routing uses com.twitter.finatra.thrift.exceptions✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.thrift.routing uses a type in com.twitter.finatra.thrift.exceptions.
- The types involved
com.twitter.finatra.thrift.routing.BaseThriftRouter→com.twitter.finatra.thrift.exceptions.ExceptionMapper
- Direction
- com.twitter.finatra.thrift.routing uses com.twitter.finatra.thrift.exceptions, so a change to com.twitter.finatra.thrift.exceptions can break com.twitter.finatra.thrift.routing, while a change to com.twitter.finatra.thrift.routing can't break com.twitter.finatra.thrift.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.thrift.routing uses a module listed above it, which is the healthy direction.
22→9 com.twitter.inject.app.internal uses com.twitter.inject✕
- Connections
- 6 pairs of types, where a type in com.twitter.inject.app.internal uses a type in com.twitter.inject.
- The types involved
com.twitter.inject.app.internal.ConsoleWriterModule→com.twitter.inject.TwitterModulecom.twitter.inject.app.internal.FlagsModule→com.twitter.inject.Loggingcom.twitter.inject.app.internal.InstalledModules→com.twitter.inject.Injectorcom.twitter.inject.app.internal.InstalledModules→com.twitter.inject.Loggingcom.twitter.inject.app.internal.InstalledModules→com.twitter.inject.TwitterModuleLifecyclecom.twitter.inject.app.internal.TwitterTypeConvertersModule→com.twitter.inject.TwitterModule
- Direction
- com.twitter.inject.app.internal uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.inject.app.internal, while a change to com.twitter.inject.app.internal can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.inject.app.internal uses a module listed above it, which is the healthy direction.
23→9 com.twitter.inject.modules uses com.twitter.inject✕
- Connections
- 6 pairs of types, where a type in com.twitter.inject.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.inject.modules.StackClientModuleTrait→com.twitter.inject.Injectorcom.twitter.inject.modules.StackClientModuleTrait→com.twitter.inject.TwitterModulecom.twitter.inject.modules.StackTransformerModule→com.twitter.inject.StackTransformercom.twitter.inject.modules.StackTransformerModule→com.twitter.inject.TwitterModulecom.twitter.inject.modules.StatsReceiverModule→com.twitter.inject.TwitterModulecom.twitter.inject.modules.TracerModule→com.twitter.inject.TwitterModule
- Direction
- com.twitter.inject.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.inject.modules, while a change to com.twitter.inject.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.inject.modules uses a module listed above it, which is the healthy direction.
24→12 com.twitter.finatra.http.jsonpatch uses com.twitter.finatra.http.exceptions✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.jsonpatch uses a type in com.twitter.finatra.http.exceptions.
- The types involved
com.twitter.finatra.http.jsonpatch.JsonPatchExceptionMapper→com.twitter.finatra.http.exceptions.ExceptionMapper
- Direction
- com.twitter.finatra.http.jsonpatch uses com.twitter.finatra.http.exceptions, so a change to com.twitter.finatra.http.exceptions can break com.twitter.finatra.http.jsonpatch, while a change to com.twitter.finatra.http.jsonpatch can't break com.twitter.finatra.http.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.http.jsonpatch uses a module listed above it, which is the healthy direction.
24→14 com.twitter.finatra.http.jsonpatch uses com.twitter.finatra.http.marshalling✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.jsonpatch uses a type in com.twitter.finatra.http.marshalling.
- The types involved
com.twitter.finatra.http.jsonpatch.JsonPatchMessageBodyReader→com.twitter.finatra.http.marshalling.MessageBodyReader
- Direction
- com.twitter.finatra.http.jsonpatch uses com.twitter.finatra.http.marshalling, so a change to com.twitter.finatra.http.marshalling can break com.twitter.finatra.http.jsonpatch, while a change to com.twitter.finatra.http.jsonpatch can't break com.twitter.finatra.http.marshalling.
- Position
- Below the diagonal: com.twitter.finatra.http.jsonpatch uses a module listed above it, which is the healthy direction.
25→9 com.twitter.finatra.http.marshalling.MessageBodyManager uses com.twitter.inject✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.marshalling.MessageBodyManager uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.http.marshalling.MessageBodyManager.Builder→com.twitter.inject.Injector
- Direction
- com.twitter.finatra.http.marshalling.MessageBodyManager uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.http.marshalling.MessageBodyManager, while a change to com.twitter.finatra.http.marshalling.MessageBodyManager can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.http.marshalling.MessageBodyManager uses a module listed above it, which is the healthy direction.
25→14 com.twitter.finatra.http.marshalling.MessageBodyManager uses com.twitter.finatra.http.marshalling✕
- Connections
- 5 pairs of types, where a type in com.twitter.finatra.http.marshalling.MessageBodyManager uses a type in com.twitter.finatra.http.marshalling.
- The types involved
com.twitter.finatra.http.marshalling.MessageBodyManager.Builder→com.twitter.finatra.http.marshalling.DefaultMessageBodyReadercom.twitter.finatra.http.marshalling.MessageBodyManager.Builder→com.twitter.finatra.http.marshalling.DefaultMessageBodyWritercom.twitter.finatra.http.marshalling.MessageBodyManager.Builder→com.twitter.finatra.http.marshalling.MessageBodyManagercom.twitter.finatra.http.marshalling.MessageBodyManager.Builder→com.twitter.finatra.http.marshalling.MessageBodyReadercom.twitter.finatra.http.marshalling.MessageBodyManager.Builder→com.twitter.finatra.http.marshalling.MessageBodyWriter
- Direction
- com.twitter.finatra.http.marshalling.MessageBodyManager uses com.twitter.finatra.http.marshalling, so a change to com.twitter.finatra.http.marshalling can break com.twitter.finatra.http.marshalling.MessageBodyManager, while a change to com.twitter.finatra.http.marshalling.MessageBodyManager can't break com.twitter.finatra.http.marshalling.
- Position
- Below the diagonal: com.twitter.finatra.http.marshalling.MessageBodyManager uses a module listed above it, which is the healthy direction.
26→14 com.twitter.finatra.http.marshalling.WriterResponse uses com.twitter.finatra.http.marshalling✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.http.marshalling.WriterResponse uses a type in com.twitter.finatra.http.marshalling.
- The types involved
com.twitter.finatra.http.marshalling.WriterResponse.EmptyResponse→com.twitter.finatra.http.marshalling.WriterResponsecom.twitter.finatra.http.marshalling.WriterResponse.Response→com.twitter.finatra.http.marshalling.WriterResponse
- Direction
- com.twitter.finatra.http.marshalling.WriterResponse uses com.twitter.finatra.http.marshalling, so a change to com.twitter.finatra.http.marshalling can break com.twitter.finatra.http.marshalling.WriterResponse, while a change to com.twitter.finatra.http.marshalling.WriterResponse can't break com.twitter.finatra.http.marshalling.
- Position
- Below the diagonal: com.twitter.finatra.http.marshalling.WriterResponse uses a module listed above it, which is the healthy direction.
27→7 com.twitter.finatra.http.marshalling.modules uses com.twitter.finatra.utils✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.marshalling.modules uses a type in com.twitter.finatra.utils.
- The types involved
com.twitter.finatra.http.marshalling.modules.MessageBodyManagerModule→com.twitter.finatra.utils.FileResolver
- Direction
- com.twitter.finatra.http.marshalling.modules uses com.twitter.finatra.utils, so a change to com.twitter.finatra.utils can break com.twitter.finatra.http.marshalling.modules, while a change to com.twitter.finatra.http.marshalling.modules can't break com.twitter.finatra.utils.
- Position
- Below the diagonal: com.twitter.finatra.http.marshalling.modules uses a module listed above it, which is the healthy direction.
27→9 com.twitter.finatra.http.marshalling.modules uses com.twitter.inject✕
- Connections
- 3 pairs of types, where a type in com.twitter.finatra.http.marshalling.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.http.marshalling.modules.MessageBodyFlagsModule→com.twitter.inject.TwitterModulecom.twitter.finatra.http.marshalling.modules.MessageBodyManagerModule→com.twitter.inject.Injectorcom.twitter.finatra.http.marshalling.modules.MessageBodyManagerModule→com.twitter.inject.TwitterModule
- Direction
- com.twitter.finatra.http.marshalling.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.http.marshalling.modules, while a change to com.twitter.finatra.http.marshalling.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.http.marshalling.modules uses a module listed above it, which is the healthy direction.
27→14 com.twitter.finatra.http.marshalling.modules uses com.twitter.finatra.http.marshalling✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.http.marshalling.modules uses a type in com.twitter.finatra.http.marshalling.
- The types involved
com.twitter.finatra.http.marshalling.modules.MessageBodyManagerModule→com.twitter.finatra.http.marshalling.DefaultMessageBodyReadercom.twitter.finatra.http.marshalling.modules.MessageBodyManagerModule→com.twitter.finatra.http.marshalling.DefaultMessageBodyWriter
- Direction
- com.twitter.finatra.http.marshalling.modules uses com.twitter.finatra.http.marshalling, so a change to com.twitter.finatra.http.marshalling can break com.twitter.finatra.http.marshalling.modules, while a change to com.twitter.finatra.http.marshalling.modules can't break com.twitter.finatra.http.marshalling.
- Position
- Below the diagonal: com.twitter.finatra.http.marshalling.modules uses a module listed above it, which is the healthy direction.
28→9 com.twitter.finatra.http.modules uses com.twitter.inject✕
- Connections
- 6 pairs of types, where a type in com.twitter.finatra.http.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.http.modules.AccessLogModule→com.twitter.inject.TwitterModulecom.twitter.finatra.http.modules.ExceptionManagerModule→com.twitter.inject.Injectorcom.twitter.finatra.http.modules.ExceptionManagerModule→com.twitter.inject.TwitterModulecom.twitter.finatra.http.modules.HttpResponseClassifierModule→com.twitter.inject.TwitterModulecom.twitter.finatra.http.modules.MustacheModule→com.twitter.inject.Injectorcom.twitter.finatra.http.modules.MustacheModule→com.twitter.inject.TwitterModule
- Direction
- com.twitter.finatra.http.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.http.modules, while a change to com.twitter.finatra.http.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.http.modules uses a module listed above it, which is the healthy direction.
28→12 com.twitter.finatra.http.modules uses com.twitter.finatra.http.exceptions✕
- Connections
- 3 pairs of types, where a type in com.twitter.finatra.http.modules uses a type in com.twitter.finatra.http.exceptions.
- The types involved
com.twitter.finatra.http.modules.ExceptionManagerModule→com.twitter.finatra.http.exceptions.ExceptionManagercom.twitter.finatra.http.modules.HttpResponseExceptionMapper→com.twitter.finatra.http.exceptions.ExceptionMappercom.twitter.finatra.http.modules.HttpResponseExceptionMapper→com.twitter.finatra.http.exceptions.HttpResponseException
- Direction
- com.twitter.finatra.http.modules uses com.twitter.finatra.http.exceptions, so a change to com.twitter.finatra.http.exceptions can break com.twitter.finatra.http.modules, while a change to com.twitter.finatra.http.modules can't break com.twitter.finatra.http.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.http.modules uses a module listed above it, which is the healthy direction.
29→7 com.twitter.finatra.http.response uses com.twitter.finatra.utils✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.response uses a type in com.twitter.finatra.utils.
- The types involved
com.twitter.finatra.http.response.EnrichedResponseImpl→com.twitter.finatra.utils.FileResolver
- Direction
- com.twitter.finatra.http.response uses com.twitter.finatra.utils, so a change to com.twitter.finatra.utils can break com.twitter.finatra.http.response, while a change to com.twitter.finatra.http.response can't break com.twitter.finatra.utils.
- Position
- Below the diagonal: com.twitter.finatra.http.response uses a module listed above it, which is the healthy direction.
29→10 com.twitter.finatra.http.response uses com.twitter.inject.exceptions✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.http.response uses a type in com.twitter.inject.exceptions.
- The types involved
com.twitter.finatra.http.response.EnrichedResponse→com.twitter.inject.exceptions.DetailedNonRetryableSourcedExceptioncom.twitter.finatra.http.response.EnrichedResponseImpl→com.twitter.inject.exceptions.DetailedNonRetryableSourcedException
- Direction
- com.twitter.finatra.http.response uses com.twitter.inject.exceptions, so a change to com.twitter.inject.exceptions can break com.twitter.finatra.http.response, while a change to com.twitter.finatra.http.response can't break com.twitter.inject.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.http.response uses a module listed above it, which is the healthy direction.
29→12 com.twitter.finatra.http.response uses com.twitter.finatra.http.exceptions✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.http.response uses a type in com.twitter.finatra.http.exceptions.
- The types involved
com.twitter.finatra.http.response.EnrichedResponse→com.twitter.finatra.http.exceptions.HttpResponseExceptioncom.twitter.finatra.http.response.EnrichedResponseImpl→com.twitter.finatra.http.exceptions.HttpResponseException
- Direction
- com.twitter.finatra.http.response uses com.twitter.finatra.http.exceptions, so a change to com.twitter.finatra.http.exceptions can break com.twitter.finatra.http.response, while a change to com.twitter.finatra.http.response can't break com.twitter.finatra.http.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.http.response uses a module listed above it, which is the healthy direction.
29→14 com.twitter.finatra.http.response uses com.twitter.finatra.http.marshalling✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.http.response uses a type in com.twitter.finatra.http.marshalling.
- The types involved
com.twitter.finatra.http.response.EnrichedResponseImpl→com.twitter.finatra.http.marshalling.MessageBodyManagercom.twitter.finatra.http.response.EnrichedResponseImpl→com.twitter.finatra.http.marshalling.WriterResponse
- Direction
- com.twitter.finatra.http.response uses com.twitter.finatra.http.marshalling, so a change to com.twitter.finatra.http.marshalling can break com.twitter.finatra.http.response, while a change to com.twitter.finatra.http.response can't break com.twitter.finatra.http.marshalling.
- Position
- Below the diagonal: com.twitter.finatra.http.response uses a module listed above it, which is the healthy direction.
30→9 com.twitter.finatra.httpclient.modules uses com.twitter.inject✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.httpclient.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.httpclient.modules.HttpClientModuleTrait→com.twitter.inject.Injector
- Direction
- com.twitter.finatra.httpclient.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.httpclient.modules, while a change to com.twitter.finatra.httpclient.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.httpclient.modules uses a module listed above it, which is the healthy direction.
30→23 com.twitter.finatra.httpclient.modules uses com.twitter.inject.modules✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.httpclient.modules uses a type in com.twitter.inject.modules.
- The types involved
com.twitter.finatra.httpclient.modules.HttpClientModuleTrait→com.twitter.inject.modules.StackClientModuleTrait
- Direction
- com.twitter.finatra.httpclient.modules uses com.twitter.inject.modules, so a change to com.twitter.inject.modules can break com.twitter.finatra.httpclient.modules, while a change to com.twitter.finatra.httpclient.modules can't break com.twitter.inject.modules.
- Position
- Below the diagonal: com.twitter.finatra.httpclient.modules uses a module listed above it, which is the healthy direction.
31→7 com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder uses com.twitter.finatra.utils✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder uses a type in com.twitter.finatra.utils.
- The types involved
com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder.LocalFilesystemMustacheFactoryImpl→com.twitter.finatra.utils.FileResolver
- Direction
- com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder uses com.twitter.finatra.utils, so a change to com.twitter.finatra.utils can break com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder, while a change to com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder can't break com.twitter.finatra.utils.
- Position
- Below the diagonal: com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder uses a module listed above it, which is the healthy direction.
31→18 com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder uses com.twitter.finatra.mustache.marshalling✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder uses a type in com.twitter.finatra.mustache.marshalling.
- The types involved
com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder.LocalFilesystemMustacheFactoryImpl→com.twitter.finatra.mustache.marshalling.LocalFilesystemMustacheFactory
- Direction
- com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder uses com.twitter.finatra.mustache.marshalling, so a change to com.twitter.finatra.mustache.marshalling can break com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder, while a change to com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder can't break com.twitter.finatra.mustache.marshalling.
- Position
- Below the diagonal: com.twitter.finatra.mustache.marshalling.MustacheFactoryBuilder uses a module listed above it, which is the healthy direction.
32→9 com.twitter.finatra.mysql.client.modules uses com.twitter.inject✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.mysql.client.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.mysql.client.modules.MysqlClientModuleTrait→com.twitter.inject.Injector
- Direction
- com.twitter.finatra.mysql.client.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.mysql.client.modules, while a change to com.twitter.finatra.mysql.client.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.mysql.client.modules uses a module listed above it, which is the healthy direction.
32→23 com.twitter.finatra.mysql.client.modules uses com.twitter.inject.modules✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.mysql.client.modules uses a type in com.twitter.inject.modules.
- The types involved
com.twitter.finatra.mysql.client.modules.MysqlClientModuleTrait→com.twitter.inject.modules.StackClientModuleTrait
- Direction
- com.twitter.finatra.mysql.client.modules uses com.twitter.inject.modules, so a change to com.twitter.inject.modules can break com.twitter.finatra.mysql.client.modules, while a change to com.twitter.finatra.mysql.client.modules can't break com.twitter.inject.modules.
- Position
- Below the diagonal: com.twitter.finatra.mysql.client.modules uses a module listed above it, which is the healthy direction.
33→9 com.twitter.inject.app uses com.twitter.inject✕
- Connections
- 2 pairs of types, where a type in com.twitter.inject.app uses a type in com.twitter.inject.
- The types involved
com.twitter.inject.app.App→com.twitter.inject.Injectorcom.twitter.inject.app.App→com.twitter.inject.Logging
- Direction
- com.twitter.inject.app uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.inject.app, while a change to com.twitter.inject.app can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.inject.app uses a module listed above it, which is the healthy direction.
33→22 com.twitter.inject.app uses com.twitter.inject.app.internal✕
- Connections
- 2 pairs of types, where a type in com.twitter.inject.app uses a type in com.twitter.inject.app.internal.
- The types involved
com.twitter.inject.app.App→com.twitter.inject.app.internal.InstalledModulescom.twitter.inject.app.App→com.twitter.inject.app.internal.Modules
- Direction
- com.twitter.inject.app uses com.twitter.inject.app.internal, so a change to com.twitter.inject.app.internal can break com.twitter.inject.app, while a change to com.twitter.inject.app can't break com.twitter.inject.app.internal.
- Position
- Below the diagonal: com.twitter.inject.app uses a module listed above it, which is the healthy direction.
34→9 com.twitter.inject.thrift.modules uses com.twitter.inject✕
- Connections
- 10 pairs of types, where a type in com.twitter.inject.thrift.modules uses a type in com.twitter.inject.
- The types involved
com.twitter.inject.thrift.modules.AndThenServiceModule→com.twitter.inject.TwitterModulecom.twitter.inject.thrift.modules.DarkTrafficFilterModuleTrait→com.twitter.inject.Injectorcom.twitter.inject.thrift.modules.JavaDarkTrafficFilterModule→com.twitter.inject.Injectorcom.twitter.inject.thrift.modules.ReqRepDarkTrafficFilterModule→com.twitter.inject.Injectorcom.twitter.inject.thrift.modules.ThriftClientModule→com.twitter.inject.Injectorcom.twitter.inject.thrift.modules.ThriftClientModule→com.twitter.inject.TwitterModulecom.twitter.inject.thrift.modules.ThriftClientModuleTrait→com.twitter.inject.Injectorcom.twitter.inject.thrift.modules.ThriftClientModuleTrait→com.twitter.inject.Loggingcom.twitter.inject.thrift.modules.ThriftMethodBuilderClientModule→com.twitter.inject.Injectorcom.twitter.inject.thrift.modules.ThriftMethodBuilderClientModule→com.twitter.inject.TwitterModule
- Direction
- com.twitter.inject.thrift.modules uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.inject.thrift.modules, while a change to com.twitter.inject.thrift.modules can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.inject.thrift.modules uses a module listed above it, which is the healthy direction.
34→11 com.twitter.inject.thrift.modules uses com.twitter.inject.thrift✕
- Connections
- 1 pair of types, where a type in com.twitter.inject.thrift.modules uses a type in com.twitter.inject.thrift.
- The types involved
com.twitter.inject.thrift.modules.ThriftMethodBuilderClientModule→com.twitter.inject.thrift.ThriftMethodBuilderFactory
- Direction
- com.twitter.inject.thrift.modules uses com.twitter.inject.thrift, so a change to com.twitter.inject.thrift can break com.twitter.inject.thrift.modules, while a change to com.twitter.inject.thrift.modules can't break com.twitter.inject.thrift.
- Position
- Below the diagonal: com.twitter.inject.thrift.modules uses a module listed above it, which is the healthy direction.
34→23 com.twitter.inject.thrift.modules uses com.twitter.inject.modules✕
- Connections
- 1 pair of types, where a type in com.twitter.inject.thrift.modules uses a type in com.twitter.inject.modules.
- The types involved
com.twitter.inject.thrift.modules.ThriftClientModuleTrait→com.twitter.inject.modules.StackClientModuleTrait
- Direction
- com.twitter.inject.thrift.modules uses com.twitter.inject.modules, so a change to com.twitter.inject.modules can break com.twitter.inject.thrift.modules, while a change to com.twitter.inject.thrift.modules can't break com.twitter.inject.modules.
- Position
- Below the diagonal: com.twitter.inject.thrift.modules uses a module listed above it, which is the healthy direction.
35→12 com.twitter.finatra.http.internal.exceptions uses com.twitter.finatra.http.exceptions✕
- Connections
- 4 pairs of types, where a type in com.twitter.finatra.http.internal.exceptions uses a type in com.twitter.finatra.http.exceptions.
- The types involved
com.twitter.finatra.http.internal.exceptions.AbstractFrameworkExceptionMapper→com.twitter.finatra.http.exceptions.ExceptionMappercom.twitter.finatra.http.internal.exceptions.HttpExceptionMapper→com.twitter.finatra.http.exceptions.HttpExceptioncom.twitter.finatra.http.internal.exceptions.HttpNackExceptionMapper→com.twitter.finatra.http.exceptions.HttpNackExceptioncom.twitter.finatra.http.internal.exceptions.HttpResponseExceptionMapper→com.twitter.finatra.http.exceptions.HttpResponseException
- Direction
- com.twitter.finatra.http.internal.exceptions uses com.twitter.finatra.http.exceptions, so a change to com.twitter.finatra.http.exceptions can break com.twitter.finatra.http.internal.exceptions, while a change to com.twitter.finatra.http.internal.exceptions can't break com.twitter.finatra.http.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.http.internal.exceptions uses a module listed above it, which is the healthy direction.
35→29 com.twitter.finatra.http.internal.exceptions uses com.twitter.finatra.http.response✕
- Connections
- 7 pairs of types, where a type in com.twitter.finatra.http.internal.exceptions uses a type in com.twitter.finatra.http.response.
- The types involved
com.twitter.finatra.http.internal.exceptions.AbstractFrameworkExceptionMapper→com.twitter.finatra.http.response.ResponseBuildercom.twitter.finatra.http.internal.exceptions.CancelledRequestExceptionMapper→com.twitter.finatra.http.response.ResponseBuildercom.twitter.finatra.http.internal.exceptions.HttpExceptionMapper→com.twitter.finatra.http.response.ResponseBuildercom.twitter.finatra.http.internal.exceptions.HttpNackExceptionMapper→com.twitter.finatra.http.response.ResponseBuildercom.twitter.finatra.http.internal.exceptions.HttpResponseExceptionMapper→com.twitter.finatra.http.response.ResponseBuildercom.twitter.finatra.http.internal.exceptions.ThriftExceptionMapper→com.twitter.finatra.http.response.ResponseBuildercom.twitter.finatra.http.internal.exceptions.ThrowableExceptionMapper→com.twitter.finatra.http.response.ResponseBuilder
- Direction
- com.twitter.finatra.http.internal.exceptions uses com.twitter.finatra.http.response, so a change to com.twitter.finatra.http.response can break com.twitter.finatra.http.internal.exceptions, while a change to com.twitter.finatra.http.internal.exceptions can't break com.twitter.finatra.http.response.
- Position
- Below the diagonal: com.twitter.finatra.http.internal.exceptions uses a module listed above it, which is the healthy direction.
36→12 com.twitter.finatra.http.internal.exceptions.json uses com.twitter.finatra.http.exceptions✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.internal.exceptions.json uses a type in com.twitter.finatra.http.exceptions.
- The types involved
com.twitter.finatra.http.internal.exceptions.json.CaseClassExceptionMapper→com.twitter.finatra.http.exceptions.ExceptionMapper
- Direction
- com.twitter.finatra.http.internal.exceptions.json uses com.twitter.finatra.http.exceptions, so a change to com.twitter.finatra.http.exceptions can break com.twitter.finatra.http.internal.exceptions.json, while a change to com.twitter.finatra.http.internal.exceptions.json can't break com.twitter.finatra.http.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.http.internal.exceptions.json uses a module listed above it, which is the healthy direction.
36→29 com.twitter.finatra.http.internal.exceptions.json uses com.twitter.finatra.http.response✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.internal.exceptions.json uses a type in com.twitter.finatra.http.response.
- The types involved
com.twitter.finatra.http.internal.exceptions.json.CaseClassExceptionMapper→com.twitter.finatra.http.response.ErrorsResponse
- Direction
- com.twitter.finatra.http.internal.exceptions.json uses com.twitter.finatra.http.response, so a change to com.twitter.finatra.http.response can break com.twitter.finatra.http.internal.exceptions.json, while a change to com.twitter.finatra.http.internal.exceptions.json can't break com.twitter.finatra.http.response.
- Position
- Below the diagonal: com.twitter.finatra.http.internal.exceptions.json uses a module listed above it, which is the healthy direction.
37→29 com.twitter.finatra.http.marshalling.response uses com.twitter.finatra.http.response✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http.marshalling.response uses a type in com.twitter.finatra.http.response.
- The types involved
com.twitter.finatra.http.marshalling.response.RichEnrichedResponse→com.twitter.finatra.http.response.EnrichedResponse
- Direction
- com.twitter.finatra.http.marshalling.response uses com.twitter.finatra.http.response, so a change to com.twitter.finatra.http.response can break com.twitter.finatra.http.marshalling.response, while a change to com.twitter.finatra.http.marshalling.response can't break com.twitter.finatra.http.response.
- Position
- Below the diagonal: com.twitter.finatra.http.marshalling.response uses a module listed above it, which is the healthy direction.
38→9 com.twitter.inject.server uses com.twitter.inject✕
- Connections
- 1 pair of types, where a type in com.twitter.inject.server uses a type in com.twitter.inject.
- The types involved
com.twitter.inject.server.Awaiter→com.twitter.inject.Logging
- Direction
- com.twitter.inject.server uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.inject.server, while a change to com.twitter.inject.server can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.inject.server uses a module listed above it, which is the healthy direction.
38→33 com.twitter.inject.server uses com.twitter.inject.app✕
- Connections
- 2 pairs of types, where a type in com.twitter.inject.server uses a type in com.twitter.inject.app.
- The types involved
com.twitter.inject.server.AbstractTwitterServer→com.twitter.inject.app.AbstractAppcom.twitter.inject.server.TwitterServer→com.twitter.inject.app.App
- Direction
- com.twitter.inject.server uses com.twitter.inject.app, so a change to com.twitter.inject.app can break com.twitter.inject.server, while a change to com.twitter.inject.server can't break com.twitter.inject.app.
- Position
- Below the diagonal: com.twitter.inject.server uses a module listed above it, which is the healthy direction.
39→5 com.twitter.finatra.http uses com.twitter.finatra.http.internal.routing✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http uses a type in com.twitter.finatra.http.internal.routing.
- The types involved
com.twitter.finatra.http.RouteBuilder→com.twitter.finatra.http.internal.routing.CallbackConverter
- Direction
- com.twitter.finatra.http uses com.twitter.finatra.http.internal.routing, so a change to com.twitter.finatra.http.internal.routing can break com.twitter.finatra.http, while a change to com.twitter.finatra.http can't break com.twitter.finatra.http.internal.routing.
- Position
- Below the diagonal: com.twitter.finatra.http uses a module listed above it, which is the healthy direction.
39→9 com.twitter.finatra.http uses com.twitter.inject✕
- Connections
- 3 pairs of types, where a type in com.twitter.finatra.http uses a type in com.twitter.inject.
- The types involved
com.twitter.finatra.http.FilteredDSL→com.twitter.inject.Injectorcom.twitter.finatra.http.RouteBuilder→com.twitter.inject.Injectorcom.twitter.finatra.http.RouteContext→com.twitter.inject.Injector
- Direction
- com.twitter.finatra.http uses com.twitter.inject, so a change to com.twitter.inject can break com.twitter.finatra.http, while a change to com.twitter.finatra.http can't break com.twitter.inject.
- Position
- Below the diagonal: com.twitter.finatra.http uses a module listed above it, which is the healthy direction.
39→16 com.twitter.finatra.http uses com.twitter.finatra.http.routing✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http uses a type in com.twitter.finatra.http.routing.
- The types involved
com.twitter.finatra.http.HttpServer→com.twitter.finatra.http.routing.HttpRouter
- Direction
- com.twitter.finatra.http uses com.twitter.finatra.http.routing, so a change to com.twitter.finatra.http.routing can break com.twitter.finatra.http, while a change to com.twitter.finatra.http can't break com.twitter.finatra.http.routing.
- Position
- Below the diagonal: com.twitter.finatra.http uses a module listed above it, which is the healthy direction.
39→29 com.twitter.finatra.http uses com.twitter.finatra.http.response✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.http uses a type in com.twitter.finatra.http.response.
- The types involved
com.twitter.finatra.http.Controller→com.twitter.finatra.http.response.ResponseBuilder
- Direction
- com.twitter.finatra.http uses com.twitter.finatra.http.response, so a change to com.twitter.finatra.http.response can break com.twitter.finatra.http, while a change to com.twitter.finatra.http can't break com.twitter.finatra.http.response.
- Position
- Below the diagonal: com.twitter.finatra.http uses a module listed above it, which is the healthy direction.
39→38 com.twitter.finatra.http uses com.twitter.inject.server✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.http uses a type in com.twitter.inject.server.
- The types involved
com.twitter.finatra.http.AbstractHttpServer→com.twitter.inject.server.AbstractTwitterServercom.twitter.finatra.http.AbstractHttpServerTrait→com.twitter.inject.server.AbstractTwitterServer
- Direction
- com.twitter.finatra.http uses com.twitter.inject.server, so a change to com.twitter.inject.server can break com.twitter.finatra.http, while a change to com.twitter.finatra.http can't break com.twitter.inject.server.
- Position
- Below the diagonal: com.twitter.finatra.http uses a module listed above it, which is the healthy direction.
40→11 com.twitter.finatra.thrift uses com.twitter.inject.thrift✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.thrift uses a type in com.twitter.inject.thrift.
- The types involved
com.twitter.finatra.thrift.ThriftClientExceptionMapper→com.twitter.inject.thrift.ThriftClientException
- Direction
- com.twitter.finatra.thrift uses com.twitter.inject.thrift, so a change to com.twitter.inject.thrift can break com.twitter.finatra.thrift, while a change to com.twitter.finatra.thrift can't break com.twitter.inject.thrift.
- Position
- Below the diagonal: com.twitter.finatra.thrift uses a module listed above it, which is the healthy direction.
40→12 com.twitter.finatra.thrift uses com.twitter.finatra.http.exceptions✕
- Connections
- 1 pair of types, where a type in com.twitter.finatra.thrift uses a type in com.twitter.finatra.http.exceptions.
- The types involved
com.twitter.finatra.thrift.ThriftClientExceptionMapper→com.twitter.finatra.http.exceptions.ExceptionMapper
- Direction
- com.twitter.finatra.thrift uses com.twitter.finatra.http.exceptions, so a change to com.twitter.finatra.http.exceptions can break com.twitter.finatra.thrift, while a change to com.twitter.finatra.thrift can't break com.twitter.finatra.http.exceptions.
- Position
- Below the diagonal: com.twitter.finatra.thrift uses a module listed above it, which is the healthy direction.
40→21 com.twitter.finatra.thrift uses com.twitter.finatra.thrift.routing✕
- Connections
- 3 pairs of types, where a type in com.twitter.finatra.thrift uses a type in com.twitter.finatra.thrift.routing.
- The types involved
com.twitter.finatra.thrift.AbstractThriftServer→com.twitter.finatra.thrift.routing.JavaThriftRoutercom.twitter.finatra.thrift.AbstractThriftServer→com.twitter.finatra.thrift.routing.ThriftRoutercom.twitter.finatra.thrift.ThriftServer→com.twitter.finatra.thrift.routing.ThriftRouter
- Direction
- com.twitter.finatra.thrift uses com.twitter.finatra.thrift.routing, so a change to com.twitter.finatra.thrift.routing can break com.twitter.finatra.thrift, while a change to com.twitter.finatra.thrift can't break com.twitter.finatra.thrift.routing.
- Position
- Below the diagonal: com.twitter.finatra.thrift uses a module listed above it, which is the healthy direction.
40→38 com.twitter.finatra.thrift uses com.twitter.inject.server✕
- Connections
- 2 pairs of types, where a type in com.twitter.finatra.thrift uses a type in com.twitter.inject.server.
- The types involved
com.twitter.finatra.thrift.AbstractThriftServer→com.twitter.inject.server.AbstractTwitterServercom.twitter.finatra.thrift.AbstractThriftServerTrait→com.twitter.inject.server.AbstractTwitterServer
- Direction
- com.twitter.finatra.thrift uses com.twitter.inject.server, so a change to com.twitter.inject.server can break com.twitter.finatra.thrift, while a change to com.twitter.finatra.thrift can't break com.twitter.inject.server.
- Position
- Below the diagonal: com.twitter.finatra.thrift 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 | 7 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.sbt; Resolve the 83 Orphaned file finding(s) in Knowledge Freshness — start with servers.scala (2), StatsFilter.scala (2), ExceptionManager.scala (2); 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 No ADRs found finding(s) in ADR Quality — start with build.sbt. | +6.9 pts | Low | ADR Quality |
| Resolve the 83 Orphaned file finding(s) in Knowledge Freshness — start with servers.scala (2), StatsFilter.scala (2), ExceptionManager.scala (2). | +6.6 pts | Medium | Knowledge Freshness |
| 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. | +6.5 pts | Medium | Architecture documentation |
| Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. | +2.0 pts | Medium | Web-Security Posture |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +1.6 pts | Medium | Security & performance tooling |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.2 pts | Medium | Nullable reference types |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with build.sbt, EnrichedResponse.scala, HttpRouter.scala. | +0.5 pts | Low | Knowledge Freshness |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +0.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala | 5.6 | Mixed | God Classes: TooManyMethods: HttpRouter |
| mysql-client/src/test/scala/com/twitter/finatra/mysql/EmbeddedMysqlServer.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| http-server/src/main/scala/com/twitter/finatra/http/internal/routing/Trie.scala | 7.4 | Mixed | Cyclomatic Complexity: Trie.findNonConstantRoute (cyclomatic 19) |
| examples/injectable-twitter-server/java/src/main/java/com/twitter/finatra/example/Publisher.java | 7.4 | Mixed | Code Duplication: Edited copy of a member (15 corresponding lines) |
| doc/src/sphinx/exts/includecode.py | 7.8 | Mixed | Cyclomatic Complexity: IncludeCode.run (cyclomatic 31) |
| http-core/src/main/scala/com/twitter/finatra/http/marshalling/MessageBodyManager.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| validation/src/main/java/com/twitter/finatra/validation/constraints/NotEmpty.java | 8.2 | Near-clean | Explicit Debt: TodoComment |
| jackson/src/main/scala/com/twitter/finatra/jackson/streaming/ByteBufferUtils.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| jackson/src/main/scala/com/twitter/finatra/jackson/caseclass/DefaultAnnotationIntrospector.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| inject/inject-utils/src/main/scala/com/twitter/inject/conversions/map.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| http-server/src/test/scala/com/twitter/finatra/http/EmbeddedHttpServer.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| http-server/src/test/scala/com/twitter/finatra/http/tests/request/MultiParamsTest.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| http-core/src/main/scala/com/twitter/finatra/http/fileupload/MultipartItem.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| http-core/src/main/scala/com/twitter/finatra/http/marshalling/MessageInjectableValues.scala | 8.5 | Near-clean | Cognitive Complexity: MessageInjectableValues.handle (cognitive 17) |
| http-server/src/main/scala/com/twitter/finatra/http/RouteDSL.scala | 8.5 | Near-clean | God Classes: TooManyMethods: RouteDSL |
| http-core/src/main/scala/com/twitter/finatra/http/response/ResponseBuilder.scala | 8.5 | Near-clean | God Classes: TooManyMethods: ResponseBuilder |
| mysql-client/src/main/scala/com/twitter/finatra/mysql/util/DAOFieldExtractors.scala | 8.5 | Near-clean | God Classes: TooManyMethods: DAOFieldExtractors |
| http-core/src/main/scala/com/twitter/finatra/http/response/EnrichedResponse.scala | 8.5 | Near-clean | God Classes: TooManyMethods: EnrichedResponse |
| http-core/src/main/scala/com/twitter/finatra/http/jsonpatch/JsonPatchOperator.scala | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 13+ corresponding lines) |
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 48 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 48 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, 145 of 157 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 (.scala, .java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala, .java) and this repository declares an sbt build (repository root, 436 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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: 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.
- D26 Project Cohesion — 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. `(repository root)` (21757 LoC, 459 module-visible types across 104 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- 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 Guice and scala-guice, 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was IncludeCode.run at 31.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with IncludeCode.run (cyclomatic 31), Trie.findNonConstantRoute (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts 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
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was IncludeCode.run at 48.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with IncludeCode.run (cognitive 48), Trie.findNonConstantRoute (cognitive 46), Trie.appendHelper (cognitive 19). — 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 Cognitive Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with RouteDSL.scala, ResponseBuilder.scala, HttpRouter.scala. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
11 duplicated block group(s) detected. 2.0 % of the production lines (439 of 21,757) are in a reported copy. A further 11 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 4 of the 22 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with CountryCodeConstraintValidator.scala, MessageBodyManager.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with Logging.scala, AssertFalseConstraintValidator.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with TraceIdMDCFilter.scala, HttpClient.scala. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
26 production modules (sbt), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 3 module(s) off the main sequence.
What to do
- Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Unstable project injectThriftClient finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 46 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with HttpRouter.scala. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
2 outdated direct sbt declarations. An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 3 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 3 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 43 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 60 of the 317 production source files in this repository: 231 are under the ~2,400-byte size floor this dimension measures over, and the remaining 26 have no attributable history left to measure.
D17 · Explicit Debt
10 deducted task-comment markers across 21757 LoC (0.0/KLoC) → score 9.9. 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 10 TodoComment finding(s) in Explicit Debt — start with EmbeddedMysqlServer.scala (3), NotEmpty.java, ByteBufferUtils.scala. — One of this dimension's main actionable groups (10 warning-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.sbt. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 4 high, 3 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `doc/src/sphinx/_themes/flask/layout.html` (lines 1–4, line 6, lines 19–21, …), `doc/src/sphinx/_themes/flask_small/layout.html` (lines 1–4, line 6, lines 12–16, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
86 of 86 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is build.sbt. Counted over 86 of the 317 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 83 Orphaned file finding(s) in Knowledge Freshness — start with servers.scala (2), StatsFilter.scala (2), ExceptionManager.scala (2). — One of this dimension's main actionable groups (83 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with build.sbt, EnrichedResponse.scala, HttpRouter.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 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
- `HttpRouter` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (maxRequestForwardingDepth, globalFilter, globalBeforeRouteMatchingFilter, routes; e.g. `maxRequestForwardingDepth` in `withMaxRequestForwardingDepth` at line 92). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:47
- `ThriftRouter` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (filters, underlying, routes; e.g. `filters` in `filter` at line 251). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — thrift/src/main/scala/com/twitter/finatra/thrift/routing/routers.scala:161
- `JavaThriftRouter` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (filters, serviceCreator; e.g. `filters` in `filter` at line 451). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — thrift/src/main/scala/com/twitter/finatra/thrift/routing/routers.scala:383
What to do
- Scala: keep controllers and singletons stateless — per-request data in locals, shared data in a store — or hold the state in a thread-safe type (TrieMap, AtomicInteger/AtomicReference, a cats-effect Ref) or update it under `synchronized { }`; a flag that is only ever overwritten can be a `@volatile var`.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
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
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:17
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmarks/src/test/scala/com/twitter/finatra/http/benchmarks/ControllerBenchmark.scala
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — inject/inject-utils/src/main/scala/com/twitter/inject/conversions/bytearray.scala:14
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: inject/inject-server/src/main/scala/com/twitter/inject/server/TwitterServer.scala:29 — `TwitterServer`.
- This repository's Scala server sets cookies (http-core/src/main/scala/com/twitter/finatra/http/response/EnrichedResponse.scala:450 — `addCookie`) and no `httpOnly`, `secure` or `sameSite` flag is switched on anywhere, nor are its cookies Play's, which are HttpOnly by default. (−1.5 on this card.)
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Flag the cookies the server sets: `HttpCookie(…, secure = true, httpOnly = true)` with `.withSameSite(…)` in akka/pekko-http, `ResponseCookie(…, secure = true, httpOnly = true, sameSite = Some(SameSite.Lax))` in http4s, or Play's `play.http.session.secure = true` — on every session and auth cookie.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
X5 · Nullable reference types
- No build over this repository's 277 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 78% | Strong | Solid. |
| Maturity | 56% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Adequate | Acceptable, with room to improve. |
| Performance | 91% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~35319 lines of test source are present (.scala, .java) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (4043 declarations, no unit with a dominant convention).
- 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, .py, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 70 value object(s); a Domain/Aggregates/ValueObjects layer
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala, Java and Python were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 4 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 56 finding(s)
- TodoComment validation/src/main/java/com/twitter/finatra/validation/constraints/NotEmpty.java:31
- TodoComment mysql-client/src/test/scala/com/twitter/finatra/mysql/EmbeddedMysqlServer.scala:28
- TodoComment mysql-client/src/test/scala/com/twitter/finatra/mysql/EmbeddedMysqlServer.scala:48
- TodoComment mysql-client/src/test/scala/com/twitter/finatra/mysql/EmbeddedMysqlServer.scala:75
- TodoComment jackson/src/main/scala/com/twitter/finatra/jackson/streaming/ByteBufferUtils.scala:18
- TodoComment jackson/src/main/scala/com/twitter/finatra/jackson/caseclass/DefaultAnnotationIntrospector.scala:19
- TodoComment inject/inject-utils/src/main/scala/com/twitter/inject/conversions/map.scala:35
- TodoComment http-server/src/test/scala/com/twitter/finatra/http/EmbeddedHttpServer.scala:1141
- TodoComment http-server/src/test/scala/com/twitter/finatra/http/tests/request/MultiParamsTest.scala:239
- TodoComment http-core/src/main/scala/com/twitter/finatra/http/fileupload/MultipartItem.scala:6
- TooManyMethods: RouteDSL http-server/src/main/scala/com/twitter/finatra/http/RouteDSL.scala:95
- TooManyMethods: ResponseBuilder http-core/src/main/scala/com/twitter/finatra/http/response/ResponseBuilder.scala:28
- TooManyMethods: HttpRouter http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:47
- TooManyMethods: DAOFieldExtractors mysql-client/src/main/scala/com/twitter/finatra/mysql/util/DAOFieldExtractors.scala:33
- TooManyMethods: EnrichedResponse http-core/src/main/scala/com/twitter/finatra/http/response/EnrichedResponse.scala:34
- Stateful singleton: HttpRouter http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:47
- Stateful singleton: ThriftRouter thrift/src/main/scala/com/twitter/finatra/thrift/routing/routers.scala:161
- Stateful singleton: JavaThriftRouter thrift/src/main/scala/com/twitter/finatra/thrift/routing/routers.scala:383
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: injectDtab
- Off the main sequence: injectMdc
- Off the main sequence: injectUtils
- Edited copy of a member (10 corresponding lines) validation/src/main/scala/com/twitter/finatra/validation/constraints/CountryCodeConstraintValidator.scala:15
- Edited copy of a member (10 corresponding lines) http-core/src/main/scala/com/twitter/finatra/http/marshalling/MessageBodyManager.scala:125
- Edited copy of a member (12 corresponding lines) inject/inject-slf4j/src/main/scala/com/twitter/inject/Logging.scala:55
- Edited copy of a member (12 corresponding lines) validation/src/main/scala/com/twitter/finatra/validation/constraints/AssertFalseConstraintValidator.scala:14
- Duplicated block (8 lines × 2) http-server/src/main/scala/com/twitter/finatra/http/filters/TraceIdMDCFilter.scala:21
- Duplicated block (8 lines × 2) http-client/src/main/scala/com/twitter/finatra/httpclient/HttpClient.scala:78
- Duplicated block (10 lines × 2) examples/injectable-twitter-server/scala/src/main/scala/com/twitter/finatra/example/Publisher.scala:23
- Duplicated block (10 lines × 2) examples/injectable-twitter-server/java/src/main/java/com/twitter/finatra/example/Publisher.java:41
- IncludeCode.run (cyclomatic 31) doc/src/sphinx/exts/includecode.py:32
- Trie.findNonConstantRoute (cyclomatic 19) http-server/src/main/scala/com/twitter/finatra/http/internal/routing/Trie.scala:55
- IncludeCode.run (cognitive 48) doc/src/sphinx/exts/includecode.py:32
- Trie.findNonConstantRoute (cognitive 46) http-server/src/main/scala/com/twitter/finatra/http/internal/routing/Trie.scala:55
- Trie.appendHelper (cognitive 19) http-server/src/main/scala/com/twitter/finatra/http/internal/routing/Trie.scala:130
- MessageInjectableValues.handle (cognitive 17) http-core/src/main/scala/com/twitter/finatra/http/marshalling/MessageInjectableValues.scala:110
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:388
- Members sharing a duplicated core (4 members, 50+ identical tokens) http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:460
- Edited copies of one member (3 members, 13+ corresponding lines) http-core/src/main/scala/com/twitter/finatra/http/jsonpatch/JsonPatchOperator.scala:189
- Edited copy of a member (8 corresponding lines) http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:106
- Edited copy of a member (6 corresponding lines) thrift/src/main/scala/com/twitter/finatra/thrift/filters/ExceptionMappingFilter.scala:19
- Duplicated block (14–19 lines × 2) validation/src/main/scala/com/twitter/finatra/validation/constraints/MaxConstraintValidator.scala:24
- Duplicated block (8–10 lines × 2) http-server/src/main/scala/com/twitter/finatra/http/filters/AccessLoggingFilter.scala:52
- Duplicated block (8–9 lines × 4) http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:460
- Duplicated block (9 lines × 2) http-core/src/main/scala/com/twitter/finatra/http/marshalling/MessageBodyManager.scala:95
- Duplicated block (8 lines × 5) http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:388
- Duplicated block (23 lines × 2) http-core/src/main/scala/com/twitter/finatra/http/response/HttpResponseClassifier.scala:29
- Duplicated block (6 lines × 2) http-client/src/main/scala/com/twitter/finatra/httpclient/RequestBuilder.scala:98
- Edited copy of a member (15 corresponding lines) examples/injectable-twitter-server/java/src/main/java/com/twitter/finatra/example/Publisher.java:75
- Edited copy of a member (5 corresponding lines) examples/injectable-twitter-server/java/src/main/java/com/twitter/finatra/example/Publisher.java:34
- Unstable project injectThriftClient
- Low cohesion: HttpRouter (LCOM4 4) http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:47
- Weak hash algorithm inject/inject-utils/src/main/scala/com/twitter/inject/conversions/bytearray.scala:14
Minor — 95 finding(s)
- Orphaned file http-server/src/main/scala/com/twitter/finatra/http/servers.scala:1
- Orphaned file thrift/src/main/scala/com/twitter/finatra/thrift/routing/routers.scala:1
- Orphaned file http-core/src/main/scala/com/twitter/finatra/http/marshalling/MessageBodyManager.scala:1
- Orphaned file http-core/src/main/scala/com/twitter/finatra/http/marshalling/MessageInjectableValues.scala:1
- Orphaned file inject/inject-core/src/main/scala/com/twitter/inject/TwitterModule.scala:1
- Orphaned file http-server/src/main/scala/com/twitter/finatra/http/RouteDSL.scala:1
- Orphaned file thrift/src/main/scala/com/twitter/finatra/thrift/servers.scala:1
- Orphaned file inject/inject-server/src/main/scala/com/twitter/inject/server/TwitterServer.scala:1
- Orphaned file http-server/src/main/scala/com/twitter/finatra/http/internal/routing/CallbackConverter.scala:1
- Orphaned file inject/inject-modules/src/main/scala/com/twitter/inject/modules/StackClientModuleTrait.scala:1
- Orphaned file http-core/src/main/scala/com/twitter/finatra/http/response/ResponseBuilder.scala:1
- Orphaned file http-core/src/main/scala/com/twitter/finatra/http/jsonpatch/JsonPatchOperator.scala:1
- Orphaned file http-server/src/main/scala/com/twitter/finatra/http/filters/StatsFilter.scala:1
- Orphaned file inject/inject-thrift-client/src/main/scala/com/twitter/inject/thrift/ThriftMethodBuilder.scala:1
- Orphaned file jackson/src/main/scala/com/twitter/finatra/jackson/modules/ScalaObjectMapperModule.scala:1
- Orphaned file inject/inject-app/src/main/scala/com/twitter/inject/app/App.scala:1
- Orphaned file mysql-client/src/main/scala/com/twitter/finatra/mysql/util/DAOFieldExtractors.scala:1
- Orphaned file thrift/src/main/scala/com/twitter/finatra/thrift/filters/StatsFilter.scala:1
- Orphaned file http-core/src/main/scala/com/twitter/finatra/http/request/MediaRange.scala:1
- Orphaned file inject/inject-app/src/main/scala/com/twitter/inject/app/internal/FlagsModule.scala:1
- Orphaned file http-server/src/main/scala/com/twitter/finatra/http/internal/routing/Trie.scala:1
- Orphaned file http-server/src/main/scala/com/twitter/finatra/http/filters/HttpResponseFilter.scala:1
- Orphaned file inject/inject-core/src/main/scala/com/twitter/inject/Injector.scala:1
- Orphaned file jackson/src/main/scala/com/twitter/finatra/jackson/caseclass/DefaultAnnotationIntrospector.scala:1
- Orphaned file inject/inject-thrift-client/src/main/scala/com/twitter/inject/thrift/modules/ThriftMethodBuilderClientModule.scala:1
- Most significant orphaned file build.sbt:1
- Most significant orphaned file http-core/src/main/scala/com/twitter/finatra/http/response/EnrichedResponse.scala:1
- Most significant orphaned file http-server/src/main/scala/com/twitter/finatra/http/routing/HttpRouter.scala:1
- No ADRs found build.sbt:1055
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:17
- Benchmarks don't track allocations benchmarks/src/test/scala/com/twitter/finatra/http/benchmarks/ControllerBenchmark.scala
- No security response headers detected
- Secure cookie flags not detected
- Scala's null is not held to the type system everywhere
Minor — 2 finding(s)
- Outdated: com.twitter:joauth
- Outdated: org.scala-lang.modules:scala-collection-compat_2.13
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-83af1910c0fa48ab9f974b8f527defbe/history.json --exit-code 0 --source . | 1 | 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-83af1910c0fa48ab9f974b8f527defbe/tree.json --exit-code 0 --source . | 1 | 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 . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d0558763094440d9aa76739ad612be8b | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d0558763094440d9aa76739ad612be8b | 0 | artifacts/raw/osv-scanner.json |