Executive summary
envimate/httpmate falls short of our standard for production because 106 files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 59 out of 100 and is rated Adequate, and all three of its critical findings are security problems in the packages it uses.
Maturity, at 49, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 7 points. Having someone learn and document the 106 files no active contributor knows comes next, worth about 10 points. Raising Maturity to 70 would lift the score to about 65.
Three known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk.
The product code is 20,266 lines, about €38,000 to rebuild.
If Maturity rose from 49 to 70, the lowest score rated Strong, the score would rise from 59 to about 65.
Rebuild cost: about €38,000 · Estimate
| Cost to rebuild | €13,000 to €64,000, for 212 to 671 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. 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: 20,266 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 client.body.multipart | 2 filtermap | 3 http | 4 http.headers | 5 path | 6 chains.rules | 7 client.issuer | 8 chains | 9 client.issuer.real | 10 backchannel | 11 client.clientbuilder | 12 closing | 13 cors.domain | 14 generator | 15 logger | 16 mapmate | 17 multipart | 18 security.config | 19 cors | 20 generator.builder | 21 handler | 22 handler.http | 23 events | 24 events.mapper | 25 exceptions | 26 multipart.handler | 27 security.authentication | 28 security.authorization | 29 com.envimate.httpmate | 30 events.processors | 31 security.basicauth | 32 security.filtering | 33 awslambda | 34 client | 35 security | 36 websockets.registry | 37 client.issuer.bypass | 38 websockets | 39 servletwithwebsockets | 40 websocketsevents |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 client.body.multipart | ||||||||||||||||||||||||||||||||||||||||
| 2 filtermap | ||||||||||||||||||||||||||||||||||||||||
| 3 http | ||||||||||||||||||||||||||||||||||||||||
| 4 http.headers | ||||||||||||||||||||||||||||||||||||||||
| 5 path | ||||||||||||||||||||||||||||||||||||||||
| 6 chains.rules | 6 | |||||||||||||||||||||||||||||||||||||||
| 7 client.issuer | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 chains | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 client.issuer.real | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 10 backchannel | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 client.clientbuilder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 closing | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 cors.domain | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 14 generator | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 15 logger | 5 | |||||||||||||||||||||||||||||||||||||||
| 16 mapmate | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 17 multipart | 2 | 7 | ||||||||||||||||||||||||||||||||||||||
| 18 security.config | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 cors | 1 | 10 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 generator.builder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 handler | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 handler.http | 4 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 23 events | 9 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 events.mapper | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 exceptions | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 multipart.handler | 3 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 27 security.authentication | 6 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 28 security.authorization | 7 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 com.envimate.httpmate | 1 | 4 | 1 | 1 | 18 | 2 | 2 | 2 | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||
| 30 events.processors | 13 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 security.basicauth | 2 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 32 security.filtering | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 awslambda | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 client | 1 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 security | 9 | 1 | 2 | 2 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 36 websockets.registry | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 client.issuer.bypass | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 websockets | 1 | 18 | 3 | |||||||||||||||||||||||||||||||||||||
| 39 servletwithwebsockets | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 websocketsevents | 5 | 1 | 2 | 4 |
6→8 chains.rules uses chains part of a loop✕
- Connections
- 6 pairs of types, where a type in chains.rules uses a type in chains.
- The types involved
com.envimate.httpmate.chains.rules.Action→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.chains.rules.Consume→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.chains.rules.Drop→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.chains.rules.Jump→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.chains.rules.Rule→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.chains.rules.Rule→com.envimate.httpmate.chains.ModuleIdentifier
- Direction
- chains.rules uses chains, so a change to chains can break chains.rules, while a change to chains.rules can't break chains.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→34 client.issuer uses client part of a loop✕
- Connections
- 2 pairs of types, where a type in client.issuer uses a type in client.
- The types involved
com.envimate.httpmate.client.issuer.Issuer→com.envimate.httpmate.client.HttpClientRequestcom.envimate.httpmate.client.issuer.Issuer→com.envimate.httpmate.client.RawClientResponse
- Direction
- client.issuer uses client, so a change to client can break client.issuer, while a change to client.issuer can't break client.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→6 chains uses chains.rules✕
- Connections
- 7 pairs of types, where a type in chains uses a type in chains.rules.
- The types involved
com.envimate.httpmate.chains.Chain→com.envimate.httpmate.chains.rules.Actioncom.envimate.httpmate.chains.Chain→com.envimate.httpmate.chains.rules.Rulecom.envimate.httpmate.chains.ChainExtender→com.envimate.httpmate.chains.rules.Actioncom.envimate.httpmate.chains.ChainRegistry→com.envimate.httpmate.chains.rules.Actioncom.envimate.httpmate.chains.ChainRegistry→com.envimate.httpmate.chains.rules.Rulecom.envimate.httpmate.chains.GraphCreator→com.envimate.httpmate.chains.rules.Actioncom.envimate.httpmate.chains.GraphCreator→com.envimate.httpmate.chains.rules.Rule
- Direction
- chains uses chains.rules, so a change to chains.rules can break chains, while a change to chains can't break chains.rules.
- Position
- Below the diagonal: chains uses a module listed above it, which is the healthy direction.
8→29 chains uses com.envimate.httpmate part of a loop✕
- Connections
- 1 pair of types, where a type in chains uses a type in com.envimate.httpmate.
- The types involved
com.envimate.httpmate.chains.DependencyRegistry→com.envimate.httpmate.MetricsProvider
- Direction
- chains uses com.envimate.httpmate, so a change to com.envimate.httpmate can break chains, while a change to chains can't break com.envimate.httpmate.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→7 client.issuer.real uses client.issuer✕
- Connections
- 1 pair of types, where a type in client.issuer.real uses a type in client.issuer.
- The types involved
com.envimate.httpmate.client.issuer.real.RealIssuer→com.envimate.httpmate.client.issuer.Issuer
- Direction
- client.issuer.real uses client.issuer, so a change to client.issuer can break client.issuer.real, while a change to client.issuer.real can't break client.issuer.
- Position
- Below the diagonal: client.issuer.real uses a module listed above it, which is the healthy direction.
9→34 client.issuer.real uses client part of a loop✕
- Connections
- 5 pairs of types, where a type in client.issuer.real uses a type in client.
- The types involved
com.envimate.httpmate.client.issuer.real.Endpoint→com.envimate.httpmate.client.BasePathcom.envimate.httpmate.client.issuer.real.Endpoint→com.envimate.httpmate.client.RequestPathcom.envimate.httpmate.client.issuer.real.RealIssuer→com.envimate.httpmate.client.BasePathcom.envimate.httpmate.client.issuer.real.RealIssuer→com.envimate.httpmate.client.HttpClientRequestcom.envimate.httpmate.client.issuer.real.RealIssuer→com.envimate.httpmate.client.RawClientResponse
- Direction
- client.issuer.real uses client, so a change to client can break client.issuer.real, while a change to client.issuer.real can't break client.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→8 backchannel uses chains✕
- Connections
- 1 pair of types, where a type in backchannel uses a type in chains.
- The types involved
com.envimate.httpmate.backchannel.BackChannelFactory→com.envimate.httpmate.chains.MetaDataKey
- Direction
- backchannel uses chains, so a change to chains can break backchannel, while a change to backchannel can't break chains.
- Position
- Below the diagonal: backchannel uses a module listed above it, which is the healthy direction.
11→9 client.clientbuilder uses client.issuer.real✕
- Connections
- 1 pair of types, where a type in client.clientbuilder uses a type in client.issuer.real.
- The types involved
com.envimate.httpmate.client.clientbuilder.ProtocolStage→com.envimate.httpmate.client.issuer.real.Protocol
- Direction
- client.clientbuilder uses client.issuer.real, so a change to client.issuer.real can break client.clientbuilder, while a change to client.clientbuilder can't break client.issuer.real.
- Position
- Below the diagonal: client.clientbuilder uses a module listed above it, which is the healthy direction.
11→34 client.clientbuilder uses client part of a loop✕
- Connections
- 1 pair of types, where a type in client.clientbuilder uses a type in client.
- The types involved
com.envimate.httpmate.client.clientbuilder.ProtocolStage→com.envimate.httpmate.client.HttpMateClientBuilder
- Direction
- client.clientbuilder uses client, so a change to client can break client.clientbuilder, while a change to client.clientbuilder can't break client.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→8 closing uses chains✕
- Connections
- 1 pair of types, where a type in closing uses a type in chains.
- The types involved
com.envimate.httpmate.closing.ClosingActions→com.envimate.httpmate.chains.MetaDataKey
- Direction
- closing uses chains, so a change to chains can break closing, while a change to closing can't break chains.
- Position
- Below the diagonal: closing uses a module listed above it, which is the healthy direction.
13→3 cors.domain uses http✕
- Connections
- 1 pair of types, where a type in cors.domain uses a type in http.
- The types involved
com.envimate.httpmate.cors.domain.RequestedMethod→com.envimate.httpmate.http.HttpRequestMethod
- Direction
- cors.domain uses http, so a change to http can break cors.domain, while a change to cors.domain can't break http.
- Position
- Below the diagonal: cors.domain uses a module listed above it, which is the healthy direction.
13→8 cors.domain uses chains✕
- Connections
- 3 pairs of types, where a type in cors.domain uses a type in chains.
- The types involved
com.envimate.httpmate.cors.domain.Origin→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.cors.domain.RequestedHeaders→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.cors.domain.RequestedMethod→com.envimate.httpmate.chains.MetaData
- Direction
- cors.domain uses chains, so a change to chains can break cors.domain, while a change to cors.domain can't break chains.
- Position
- Below the diagonal: cors.domain uses a module listed above it, which is the healthy direction.
14→3 generator uses http✕
- Connections
- 1 pair of types, where a type in generator uses a type in http.
- The types involved
com.envimate.httpmate.generator.PathAndMethodGenerationCondition→com.envimate.httpmate.http.HttpRequestMethod
- Direction
- generator uses http, so a change to http can break generator, while a change to generator can't break http.
- Position
- Below the diagonal: generator uses a module listed above it, which is the healthy direction.
14→5 generator uses path✕
- Connections
- 1 pair of types, where a type in generator uses a type in path.
- The types involved
com.envimate.httpmate.generator.PathAndMethodGenerationCondition→com.envimate.httpmate.path.PathTemplate
- Direction
- generator uses path, so a change to path can break generator, while a change to generator can't break path.
- Position
- Below the diagonal: generator uses a module listed above it, which is the healthy direction.
14→8 generator uses chains✕
- Connections
- 4 pairs of types, where a type in generator uses a type in chains.
- The types involved
com.envimate.httpmate.generator.GenerationCondition→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.generator.Generator→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.generator.Generators→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.generator.PathAndMethodGenerationCondition→com.envimate.httpmate.chains.MetaData
- Direction
- generator uses chains, so a change to chains can break generator, while a change to generator can't break chains.
- Position
- Below the diagonal: generator uses a module listed above it, which is the healthy direction.
15→8 logger uses chains✕
- Connections
- 5 pairs of types, where a type in logger uses a type in chains.
- The types involved
com.envimate.httpmate.logger.LogMessage→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.logger.Logger→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.logger.LoggerConfigurators→com.envimate.httpmate.chains.Configuratorcom.envimate.httpmate.logger.SetLoggerProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.logger.SetLoggerProcessor→com.envimate.httpmate.chains.Processor
- Direction
- logger uses chains, so a change to chains can break logger, while a change to logger can't break chains.
- Position
- Below the diagonal: logger uses a module listed above it, which is the healthy direction.
16→4 mapmate uses http.headers✕
- Connections
- 2 pairs of types, where a type in mapmate uses a type in http.headers.
- The types involved
com.envimate.httpmate.mapmate.MapMateIntegrationBuilder→com.envimate.httpmate.http.headers.ContentTypecom.envimate.httpmate.mapmate.MapMateSerializerAndDeserializer→com.envimate.httpmate.http.headers.ContentType
- Direction
- mapmate uses http.headers, so a change to http.headers can break mapmate, while a change to mapmate can't break http.headers.
- Position
- Below the diagonal: mapmate uses a module listed above it, which is the healthy direction.
16→8 mapmate uses chains✕
- Connections
- 3 pairs of types, where a type in mapmate uses a type in chains.
- The types involved
com.envimate.httpmate.mapmate.MapMateIntegrationBuilder→com.envimate.httpmate.chains.ConfiguratorBuildercom.envimate.httpmate.mapmate.MapMateSerializerAndDeserializer→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.mapmate.MapMateSerializerAndDeserializer→com.envimate.httpmate.chains.DependencyRegistry
- Direction
- mapmate uses chains, so a change to chains can break mapmate, while a change to mapmate can't break chains.
- Position
- Below the diagonal: mapmate uses a module listed above it, which is the healthy direction.
17→4 multipart uses http.headers✕
- Connections
- 2 pairs of types, where a type in multipart uses a type in http.headers.
- The types involved
com.envimate.httpmate.multipart.MultipartModule→com.envimate.httpmate.http.headers.ContentTypecom.envimate.httpmate.multipart.MultipartParser→com.envimate.httpmate.http.headers.ContentType
- Direction
- multipart uses http.headers, so a change to http.headers can break multipart, while a change to multipart can't break http.headers.
- Position
- Below the diagonal: multipart uses a module listed above it, which is the healthy direction.
17→8 multipart uses chains✕
- Connections
- 7 pairs of types, where a type in multipart uses a type in chains.
- The types involved
com.envimate.httpmate.multipart.MultipartChainKeys→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.multipart.MultipartConfigurators→com.envimate.httpmate.chains.Configuratorcom.envimate.httpmate.multipart.MultipartModule→com.envimate.httpmate.chains.ChainExtendercom.envimate.httpmate.multipart.MultipartModule→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.multipart.MultipartModule→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.multipart.MultipartProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.multipart.MultipartProcessor→com.envimate.httpmate.chains.Processor
- Direction
- multipart uses chains, so a change to chains can break multipart, while a change to multipart can't break chains.
- Position
- Below the diagonal: multipart uses a module listed above it, which is the healthy direction.
18→8 security.config uses chains✕
- Connections
- 3 pairs of types, where a type in security.config uses a type in chains.
- The types involved
com.envimate.httpmate.security.config.PhaseConfigurator→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.security.config.SecurityConfigurator→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.security.config.SecurityConfigurator→com.envimate.httpmate.chains.Configurator
- Direction
- security.config uses chains, so a change to chains can break security.config, while a change to security.config can't break chains.
- Position
- Below the diagonal: security.config uses a module listed above it, which is the healthy direction.
18→35 security.config uses security part of a loop✕
- Connections
- 1 pair of types, where a type in security.config uses a type in security.
- The types involved
com.envimate.httpmate.security.config.FilterConfigurator→com.envimate.httpmate.security.Filter
- Direction
- security.config uses security, so a change to security can break security.config, while a change to security.config can't break security.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→3 cors uses http✕
- Connections
- 1 pair of types, where a type in cors uses a type in http.
- The types involved
com.envimate.httpmate.cors.CorsConfigurator→com.envimate.httpmate.http.HttpRequestMethod
- Direction
- cors uses http, so a change to http can break cors, while a change to cors can't break http.
- Position
- Below the diagonal: cors uses a module listed above it, which is the healthy direction.
19→8 cors uses chains✕
- Connections
- 10 pairs of types, where a type in cors uses a type in chains.
- The types involved
com.envimate.httpmate.cors.CorsConfigurator→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.cors.CorsConfigurator→com.envimate.httpmate.chains.Configuratorcom.envimate.httpmate.cors.CorsConfigurator→com.envimate.httpmate.chains.DependencyRegistrycom.envimate.httpmate.cors.CorsModule→com.envimate.httpmate.chains.ChainExtendercom.envimate.httpmate.cors.CorsModule→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.cors.CorsModule→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.cors.PreflightRequestProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.cors.PreflightRequestProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.cors.SimpleCrossOriginRequestProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.cors.SimpleCrossOriginRequestProcessor→com.envimate.httpmate.chains.Processor
- Direction
- cors uses chains, so a change to chains can break cors, while a change to cors can't break chains.
- Position
- Below the diagonal: cors uses a module listed above it, which is the healthy direction.
19→13 cors uses cors.domain✕
- Connections
- 2 pairs of types, where a type in cors uses a type in cors.domain.
- The types involved
com.envimate.httpmate.cors.CorsConfigurator→com.envimate.httpmate.cors.domain.ExposedHeaderscom.envimate.httpmate.cors.CorsConfigurator→com.envimate.httpmate.cors.domain.MaxAge
- Direction
- cors uses cors.domain, so a change to cors.domain can break cors, while a change to cors can't break cors.domain.
- Position
- Below the diagonal: cors uses a module listed above it, which is the healthy direction.
20→3 generator.builder uses http✕
- Connections
- 1 pair of types, where a type in generator.builder uses a type in http.
- The types involved
com.envimate.httpmate.generator.builder.MethodStage→com.envimate.httpmate.http.HttpRequestMethod
- Direction
- generator.builder uses http, so a change to http can break generator.builder, while a change to generator.builder can't break http.
- Position
- Below the diagonal: generator.builder uses a module listed above it, which is the healthy direction.
20→14 generator.builder uses generator✕
- Connections
- 1 pair of types, where a type in generator.builder uses a type in generator.
- The types involved
com.envimate.httpmate.generator.builder.ConditionStage→com.envimate.httpmate.generator.GenerationCondition
- Direction
- generator.builder uses generator, so a change to generator can break generator.builder, while a change to generator.builder can't break generator.
- Position
- Below the diagonal: generator.builder uses a module listed above it, which is the healthy direction.
21→8 handler uses chains✕
- Connections
- 6 pairs of types, where a type in handler uses a type in chains.
- The types involved
com.envimate.httpmate.handler.DetermineHandlerProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.handler.DetermineHandlerProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.handler.Handler→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.handler.InvokeHandlerProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.handler.InvokeHandlerProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.handler.NoHandlerFoundException→com.envimate.httpmate.chains.MetaData
- Direction
- handler uses chains, so a change to chains can break handler, while a change to handler can't break chains.
- Position
- Below the diagonal: handler uses a module listed above it, which is the healthy direction.
21→14 handler uses generator✕
- Connections
- 1 pair of types, where a type in handler uses a type in generator.
- The types involved
com.envimate.httpmate.handler.DetermineHandlerProcessor→com.envimate.httpmate.generator.Generators
- Direction
- handler uses generator, so a change to generator can break handler, while a change to handler can't break generator.
- Position
- Below the diagonal: handler uses a module listed above it, which is the healthy direction.
22→3 handler.http uses http✕
- Connections
- 4 pairs of types, where a type in handler.http uses a type in http.
- The types involved
com.envimate.httpmate.handler.http.HttpRequest→com.envimate.httpmate.http.Headerscom.envimate.httpmate.handler.http.HttpRequest→com.envimate.httpmate.http.HttpRequestMethodcom.envimate.httpmate.handler.http.HttpRequest→com.envimate.httpmate.http.PathParameterscom.envimate.httpmate.handler.http.HttpRequest→com.envimate.httpmate.http.QueryParameters
- Direction
- handler.http uses http, so a change to http can break handler.http, while a change to handler.http can't break http.
- Position
- Below the diagonal: handler.http uses a module listed above it, which is the healthy direction.
22→4 handler.http uses http.headers✕
- Connections
- 1 pair of types, where a type in handler.http uses a type in http.headers.
- The types involved
com.envimate.httpmate.handler.http.HttpResponse→com.envimate.httpmate.http.headers.ContentType
- Direction
- handler.http uses http.headers, so a change to http.headers can break handler.http, while a change to handler.http can't break http.headers.
- Position
- Below the diagonal: handler.http uses a module listed above it, which is the healthy direction.
22→5 handler.http uses path✕
- Connections
- 1 pair of types, where a type in handler.http uses a type in path.
- The types involved
com.envimate.httpmate.handler.http.HttpRequest→com.envimate.httpmate.path.Path
- Direction
- handler.http uses path, so a change to path can break handler.http, while a change to handler.http can't break path.
- Position
- Below the diagonal: handler.http uses a module listed above it, which is the healthy direction.
22→8 handler.http uses chains✕
- Connections
- 3 pairs of types, where a type in handler.http uses a type in chains.
- The types involved
com.envimate.httpmate.handler.http.HttpHandler→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.handler.http.HttpRequest→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.handler.http.HttpResponse→com.envimate.httpmate.chains.MetaData
- Direction
- handler.http uses chains, so a change to chains can break handler.http, while a change to handler.http can't break chains.
- Position
- Below the diagonal: handler.http uses a module listed above it, which is the healthy direction.
22→21 handler.http uses handler✕
- Connections
- 1 pair of types, where a type in handler.http uses a type in handler.
- The types involved
com.envimate.httpmate.handler.http.HttpHandler→com.envimate.httpmate.handler.Handler
- Direction
- handler.http uses handler, so a change to handler can break handler.http, while a change to handler.http can't break handler.
- Position
- Below the diagonal: handler.http uses a module listed above it, which is the healthy direction.
23→8 events uses chains✕
- Connections
- 9 pairs of types, where a type in events uses a type in chains.
- The types involved
com.envimate.httpmate.events.EventConfigurators→com.envimate.httpmate.chains.Configuratorcom.envimate.httpmate.events.EventsChains→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.events.ExternalEventMapping→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.events.ExternalEventMapping→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.ExternalEventMapping→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.events.RequestMapEnricher→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.RequestMapEnricher→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.events.ResponseMapExtractor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.ResponseMapExtractor→com.envimate.httpmate.chains.Processor
- Direction
- events uses chains, so a change to chains can break events, while a change to events can't break chains.
- Position
- Below the diagonal: events uses a module listed above it, which is the healthy direction.
23→14 events uses generator✕
- Connections
- 2 pairs of types, where a type in events uses a type in generator.
- The types involved
com.envimate.httpmate.events.EventModule→com.envimate.httpmate.generator.GenerationConditioncom.envimate.httpmate.events.EventModule→com.envimate.httpmate.generator.Generator
- Direction
- events uses generator, so a change to generator can break events, while a change to events can't break generator.
- Position
- Below the diagonal: events uses a module listed above it, which is the healthy direction.
23→22 events uses handler.http✕
- Connections
- 2 pairs of types, where a type in events uses a type in handler.http.
- The types involved
com.envimate.httpmate.events.RequestMapEnricher→com.envimate.httpmate.handler.http.HttpRequestcom.envimate.httpmate.events.ResponseMapExtractor→com.envimate.httpmate.handler.http.HttpResponse
- Direction
- events uses handler.http, so a change to handler.http can break events, while a change to events can't break handler.http.
- Position
- Below the diagonal: events uses a module listed above it, which is the healthy direction.
24→8 events.mapper uses chains✕
- Connections
- 3 pairs of types, where a type in events.mapper uses a type in chains.
- The types involved
com.envimate.httpmate.events.mapper.EventToResponseMapper→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.mapper.HttpRequestToEventMapper→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.mapper.RequestToEventMapper→com.envimate.httpmate.chains.MetaData
- Direction
- events.mapper uses chains, so a change to chains can break events.mapper, while a change to events.mapper can't break chains.
- Position
- Below the diagonal: events.mapper uses a module listed above it, which is the healthy direction.
24→22 events.mapper uses handler.http✕
- Connections
- 1 pair of types, where a type in events.mapper uses a type in handler.http.
- The types involved
com.envimate.httpmate.events.mapper.HttpRequestToEventMapper→com.envimate.httpmate.handler.http.HttpRequest
- Direction
- events.mapper uses handler.http, so a change to handler.http can break events.mapper, while a change to events.mapper can't break handler.http.
- Position
- Below the diagonal: events.mapper uses a module listed above it, which is the healthy direction.
25→2 exceptions uses filtermap✕
- Connections
- 1 pair of types, where a type in exceptions uses a type in filtermap.
- The types involved
com.envimate.httpmate.exceptions.ExceptionSerializer→com.envimate.httpmate.filtermap.FilterMap
- Direction
- exceptions uses filtermap, so a change to filtermap can break exceptions, while a change to exceptions can't break filtermap.
- Position
- Below the diagonal: exceptions uses a module listed above it, which is the healthy direction.
25→8 exceptions uses chains✕
- Connections
- 5 pairs of types, where a type in exceptions uses a type in chains.
- The types involved
com.envimate.httpmate.exceptions.DefaultExceptionMapper→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.exceptions.ExceptionConfigurators→com.envimate.httpmate.chains.Configuratorcom.envimate.httpmate.exceptions.ExceptionMapper→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.exceptions.ExceptionSerializer→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.exceptions.HttpExceptionMapper→com.envimate.httpmate.chains.MetaData
- Direction
- exceptions uses chains, so a change to chains can break exceptions, while a change to exceptions can't break chains.
- Position
- Below the diagonal: exceptions uses a module listed above it, which is the healthy direction.
25→22 exceptions uses handler.http✕
- Connections
- 1 pair of types, where a type in exceptions uses a type in handler.http.
- The types involved
com.envimate.httpmate.exceptions.HttpExceptionMapper→com.envimate.httpmate.handler.http.HttpResponse
- Direction
- exceptions uses handler.http, so a change to handler.http can break exceptions, while a change to exceptions can't break handler.http.
- Position
- Below the diagonal: exceptions uses a module listed above it, which is the healthy direction.
26→3 multipart.handler uses http✕
- Connections
- 3 pairs of types, where a type in multipart.handler uses a type in http.
- The types involved
com.envimate.httpmate.multipart.handler.MultipartRequest→com.envimate.httpmate.http.Headerscom.envimate.httpmate.multipart.handler.MultipartRequest→com.envimate.httpmate.http.PathParameterscom.envimate.httpmate.multipart.handler.MultipartRequest→com.envimate.httpmate.http.QueryParameters
- Direction
- multipart.handler uses http, so a change to http can break multipart.handler, while a change to multipart.handler can't break http.
- Position
- Below the diagonal: multipart.handler uses a module listed above it, which is the healthy direction.
26→5 multipart.handler uses path✕
- Connections
- 1 pair of types, where a type in multipart.handler uses a type in path.
- The types involved
com.envimate.httpmate.multipart.handler.MultipartRequest→com.envimate.httpmate.path.Path
- Direction
- multipart.handler uses path, so a change to path can break multipart.handler, while a change to multipart.handler can't break path.
- Position
- Below the diagonal: multipart.handler uses a module listed above it, which is the healthy direction.
26→17 multipart.handler uses multipart✕
- Connections
- 1 pair of types, where a type in multipart.handler uses a type in multipart.
- The types involved
com.envimate.httpmate.multipart.handler.MultipartRequest→com.envimate.httpmate.multipart.MultipartIteratorBody
- Direction
- multipart.handler uses multipart, so a change to multipart can break multipart.handler, while a change to multipart.handler can't break multipart.
- Position
- Below the diagonal: multipart.handler uses a module listed above it, which is the healthy direction.
26→22 multipart.handler uses handler.http✕
- Connections
- 4 pairs of types, where a type in multipart.handler uses a type in handler.http.
- The types involved
com.envimate.httpmate.multipart.handler.MultipartHandler→com.envimate.httpmate.handler.http.HttpHandlercom.envimate.httpmate.multipart.handler.MultipartHandler→com.envimate.httpmate.handler.http.HttpRequestcom.envimate.httpmate.multipart.handler.MultipartHandler→com.envimate.httpmate.handler.http.HttpResponsecom.envimate.httpmate.multipart.handler.MultipartRequest→com.envimate.httpmate.handler.http.HttpRequest
- Direction
- multipart.handler uses handler.http, so a change to handler.http can break multipart.handler, while a change to multipart.handler can't break handler.http.
- Position
- Below the diagonal: multipart.handler uses a module listed above it, which is the healthy direction.
27→8 security.authentication uses chains✕
- Connections
- 6 pairs of types, where a type in security.authentication uses a type in chains.
- The types involved
com.envimate.httpmate.security.authentication.AuthenticatorConfigurator→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.security.authentication.AuthenticatorConfigurator→com.envimate.httpmate.chains.DependencyRegistrycom.envimate.httpmate.security.authentication.AuthenticatorConfigurator→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.security.authentication.AuthenticatorProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.security.authentication.AuthenticatorProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.security.authentication.CouldNotAuthenticateException→com.envimate.httpmate.chains.MetaData
- Direction
- security.authentication uses chains, so a change to chains can break security.authentication, while a change to security.authentication can't break chains.
- Position
- Below the diagonal: security.authentication uses a module listed above it, which is the healthy direction.
27→18 security.authentication uses security.config✕
- Connections
- 1 pair of types, where a type in security.authentication uses a type in security.config.
- The types involved
com.envimate.httpmate.security.authentication.AuthenticatorConfigurator→com.envimate.httpmate.security.config.SecurityConfigurator
- Direction
- security.authentication uses security.config, so a change to security.config can break security.authentication, while a change to security.authentication can't break security.config.
- Position
- Below the diagonal: security.authentication uses a module listed above it, which is the healthy direction.
27→22 security.authentication uses handler.http✕
- Connections
- 1 pair of types, where a type in security.authentication uses a type in handler.http.
- The types involved
com.envimate.httpmate.security.authentication.AuthenticatorConfigurator→com.envimate.httpmate.handler.http.HttpHandler
- Direction
- security.authentication uses handler.http, so a change to handler.http can break security.authentication, while a change to security.authentication can't break handler.http.
- Position
- Below the diagonal: security.authentication uses a module listed above it, which is the healthy direction.
27→35 security.authentication uses security part of a loop✕
- Connections
- 3 pairs of types, where a type in security.authentication uses a type in security.
- The types involved
com.envimate.httpmate.security.authentication.AuthenticatorConfigurator→com.envimate.httpmate.security.Filtercom.envimate.httpmate.security.authentication.AuthenticatorConfigurator→com.envimate.httpmate.security.SimpleSecurityConfiguratorcom.envimate.httpmate.security.authentication.AuthenticatorProcessor→com.envimate.httpmate.security.Filter
- Direction
- security.authentication uses security, so a change to security can break security.authentication, while a change to security.authentication can't break security.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→8 security.authorization uses chains✕
- Connections
- 7 pairs of types, where a type in security.authorization uses a type in chains.
- The types involved
com.envimate.httpmate.security.authorization.Authorizer→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.security.authorization.AuthorizerConfigurator→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.security.authorization.AuthorizerConfigurator→com.envimate.httpmate.chains.DependencyRegistrycom.envimate.httpmate.security.authorization.AuthorizerProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.security.authorization.AuthorizerProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.security.authorization.HttpAuthorizer→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.security.authorization.NotAuthorizedException→com.envimate.httpmate.chains.MetaData
- Direction
- security.authorization uses chains, so a change to chains can break security.authorization, while a change to security.authorization can't break chains.
- Position
- Below the diagonal: security.authorization uses a module listed above it, which is the healthy direction.
28→18 security.authorization uses security.config✕
- Connections
- 1 pair of types, where a type in security.authorization uses a type in security.config.
- The types involved
com.envimate.httpmate.security.authorization.AuthorizerConfigurator→com.envimate.httpmate.security.config.SecurityConfigurator
- Direction
- security.authorization uses security.config, so a change to security.config can break security.authorization, while a change to security.authorization can't break security.config.
- Position
- Below the diagonal: security.authorization uses a module listed above it, which is the healthy direction.
28→22 security.authorization uses handler.http✕
- Connections
- 2 pairs of types, where a type in security.authorization uses a type in handler.http.
- The types involved
com.envimate.httpmate.security.authorization.AuthorizerConfigurator→com.envimate.httpmate.handler.http.HttpHandlercom.envimate.httpmate.security.authorization.HttpAuthorizer→com.envimate.httpmate.handler.http.HttpRequest
- Direction
- security.authorization uses handler.http, so a change to handler.http can break security.authorization, while a change to security.authorization can't break handler.http.
- Position
- Below the diagonal: security.authorization uses a module listed above it, which is the healthy direction.
28→35 security.authorization uses security part of a loop✕
- Connections
- 2 pairs of types, where a type in security.authorization uses a type in security.
- The types involved
com.envimate.httpmate.security.authorization.AuthorizerConfigurator→com.envimate.httpmate.security.Filtercom.envimate.httpmate.security.authorization.AuthorizerConfigurator→com.envimate.httpmate.security.SimpleSecurityConfigurator
- Direction
- security.authorization uses security, so a change to security can break security.authorization, while a change to security.authorization can't break security.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→2 com.envimate.httpmate uses filtermap✕
- Connections
- 1 pair of types, where a type in com.envimate.httpmate uses a type in filtermap.
- The types involved
com.envimate.httpmate.CoreModule→com.envimate.httpmate.filtermap.FilterMapBuilder
- Direction
- com.envimate.httpmate uses filtermap, so a change to filtermap can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break filtermap.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→3 com.envimate.httpmate uses http✕
- Connections
- 4 pairs of types, where a type in com.envimate.httpmate uses a type in http.
- The types involved
com.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.http.Headerscom.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.http.HttpRequestMethodcom.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.http.PathParameterscom.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.http.QueryParameters
- Direction
- com.envimate.httpmate uses http, so a change to http can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break http.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→4 com.envimate.httpmate uses http.headers✕
- Connections
- 1 pair of types, where a type in com.envimate.httpmate uses a type in http.headers.
- The types involved
com.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.http.headers.ContentType
- Direction
- com.envimate.httpmate uses http.headers, so a change to http.headers can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break http.headers.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→5 com.envimate.httpmate uses path✕
- Connections
- 1 pair of types, where a type in com.envimate.httpmate uses a type in path.
- The types involved
com.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.path.Path
- Direction
- com.envimate.httpmate uses path, so a change to path can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break path.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→8 com.envimate.httpmate uses chains✕
- Connections
- 18 pairs of types, where a type in com.envimate.httpmate uses a type in chains.
- The types involved
com.envimate.httpmate.Configurators→com.envimate.httpmate.chains.Configuratorcom.envimate.httpmate.CoreModule→com.envimate.httpmate.chains.ChainExtendercom.envimate.httpmate.CoreModule→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.CoreModule→com.envimate.httpmate.chains.DependencyRegistrycom.envimate.httpmate.CoreModule→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.HttpMate→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.HttpMate→com.envimate.httpmate.chains.ChainRegistrycom.envimate.httpmate.HttpMate→com.envimate.httpmate.chains.FinalConsumercom.envimate.httpmate.HttpMate→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.HttpMate→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.HttpMateBuilder→com.envimate.httpmate.chains.Configuratorcom.envimate.httpmate.HttpMateBuilder→com.envimate.httpmate.chains.ConfiguratorBuildercom.envimate.httpmate.HttpMateBuilder→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.HttpMateBuilder→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.HttpMateChains→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.MetricsProvider→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.MetricsProvider→com.envimate.httpmate.chains.MetaDataKey
- Direction
- com.envimate.httpmate uses chains, so a change to chains can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break chains.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→12 com.envimate.httpmate uses closing✕
- Connections
- 2 pairs of types, where a type in com.envimate.httpmate uses a type in closing.
- The types involved
com.envimate.httpmate.CoreModule→com.envimate.httpmate.closing.ClosingActioncom.envimate.httpmate.CoreModule→com.envimate.httpmate.closing.ClosingActions
- Direction
- com.envimate.httpmate uses closing, so a change to closing can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break closing.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→14 com.envimate.httpmate uses generator✕
- Connections
- 2 pairs of types, where a type in com.envimate.httpmate uses a type in generator.
- The types involved
com.envimate.httpmate.CoreModule→com.envimate.httpmate.generator.GenerationConditioncom.envimate.httpmate.CoreModule→com.envimate.httpmate.generator.Generator
- Direction
- com.envimate.httpmate uses generator, so a change to generator can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break generator.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→15 com.envimate.httpmate uses logger✕
- Connections
- 2 pairs of types, where a type in com.envimate.httpmate uses a type in logger.
- The types involved
com.envimate.httpmate.CoreModule→com.envimate.httpmate.logger.LoggerImplementationcom.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.logger.Logger
- Direction
- com.envimate.httpmate uses logger, so a change to logger can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break logger.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→20 com.envimate.httpmate uses generator.builder✕
- Connections
- 1 pair of types, where a type in com.envimate.httpmate uses a type in generator.builder.
- The types involved
com.envimate.httpmate.HttpMateBuilder→com.envimate.httpmate.generator.builder.ConditionStage
- Direction
- com.envimate.httpmate uses generator.builder, so a change to generator.builder can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break generator.builder.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→21 com.envimate.httpmate uses handler✕
- Connections
- 3 pairs of types, where a type in com.envimate.httpmate uses a type in handler.
- The types involved
com.envimate.httpmate.CoreModule→com.envimate.httpmate.handler.Handlercom.envimate.httpmate.HttpMateBuilder→com.envimate.httpmate.handler.Handlercom.envimate.httpmate.HttpMateChainKeys→com.envimate.httpmate.handler.Handler
- Direction
- com.envimate.httpmate uses handler, so a change to handler can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break handler.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→22 com.envimate.httpmate uses handler.http✕
- Connections
- 1 pair of types, where a type in com.envimate.httpmate uses a type in handler.http.
- The types involved
com.envimate.httpmate.HttpMateBuilder→com.envimate.httpmate.handler.http.HttpHandler
- Direction
- com.envimate.httpmate uses handler.http, so a change to handler.http can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break handler.http.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
29→25 com.envimate.httpmate uses exceptions✕
- Connections
- 1 pair of types, where a type in com.envimate.httpmate uses a type in exceptions.
- The types involved
com.envimate.httpmate.CoreModule→com.envimate.httpmate.exceptions.ExceptionMapper
- Direction
- com.envimate.httpmate uses exceptions, so a change to exceptions can break com.envimate.httpmate, while a change to com.envimate.httpmate can't break exceptions.
- Position
- Below the diagonal: com.envimate.httpmate uses a module listed above it, which is the healthy direction.
30→8 events.processors uses chains✕
- Connections
- 13 pairs of types, where a type in events.processors uses a type in chains.
- The types involved
com.envimate.httpmate.events.processors.DetermineEventProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.processors.DetermineEventProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.events.processors.DispatchEventProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.processors.DispatchEventProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.events.processors.HandleExternalEventProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.processors.HandleExternalEventProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.events.processors.MapToEventProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.processors.MapToEventProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.events.processors.NoEventTypeMappingForWebserviceRequestException→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.processors.SerializationProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.processors.SerializationProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.events.processors.UnwrapDispatchingExceptionProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.events.processors.UnwrapDispatchingExceptionProcessor→com.envimate.httpmate.chains.Processor
- Direction
- events.processors uses chains, so a change to chains can break events.processors, while a change to events.processors can't break chains.
- Position
- Below the diagonal: events.processors uses a module listed above it, which is the healthy direction.
30→14 events.processors uses generator✕
- Connections
- 1 pair of types, where a type in events.processors uses a type in generator.
- The types involved
com.envimate.httpmate.events.processors.DetermineEventProcessor→com.envimate.httpmate.generator.Generators
- Direction
- events.processors uses generator, so a change to generator can break events.processors, while a change to events.processors can't break generator.
- Position
- Below the diagonal: events.processors uses a module listed above it, which is the healthy direction.
30→23 events.processors uses events✕
- Connections
- 1 pair of types, where a type in events.processors uses a type in events.
- The types involved
com.envimate.httpmate.events.processors.HandleExternalEventProcessor→com.envimate.httpmate.events.ExternalEventMapping
- Direction
- events.processors uses events, so a change to events can break events.processors, while a change to events.processors can't break events.
- Position
- Below the diagonal: events.processors uses a module listed above it, which is the healthy direction.
30→24 events.processors uses events.mapper✕
- Connections
- 2 pairs of types, where a type in events.processors uses a type in events.mapper.
- The types involved
com.envimate.httpmate.events.processors.MapToEventProcessor→com.envimate.httpmate.events.mapper.RequestToEventMappercom.envimate.httpmate.events.processors.SerializationProcessor→com.envimate.httpmate.events.mapper.EventToResponseMapper
- Direction
- events.processors uses events.mapper, so a change to events.mapper can break events.processors, while a change to events.processors can't break events.mapper.
- Position
- Below the diagonal: events.processors uses a module listed above it, which is the healthy direction.
31→8 security.basicauth uses chains✕
- Connections
- 2 pairs of types, where a type in security.basicauth uses a type in chains.
- The types involved
com.envimate.httpmate.security.basicauth.BasicAuthConfigurator→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.security.basicauth.BasicAuthConfigurator→com.envimate.httpmate.chains.DependencyRegistry
- Direction
- security.basicauth uses chains, so a change to chains can break security.basicauth, while a change to security.basicauth can't break chains.
- Position
- Below the diagonal: security.basicauth uses a module listed above it, which is the healthy direction.
31→18 security.basicauth uses security.config✕
- Connections
- 1 pair of types, where a type in security.basicauth uses a type in security.config.
- The types involved
com.envimate.httpmate.security.basicauth.BasicAuthConfigurator→com.envimate.httpmate.security.config.SecurityConfigurator
- Direction
- security.basicauth uses security.config, so a change to security.config can break security.basicauth, while a change to security.basicauth can't break security.config.
- Position
- Below the diagonal: security.basicauth uses a module listed above it, which is the healthy direction.
31→22 security.basicauth uses handler.http✕
- Connections
- 1 pair of types, where a type in security.basicauth uses a type in handler.http.
- The types involved
com.envimate.httpmate.security.basicauth.BasicAuthAuthenticator→com.envimate.httpmate.handler.http.HttpRequest
- Direction
- security.basicauth uses handler.http, so a change to handler.http can break security.basicauth, while a change to security.basicauth can't break handler.http.
- Position
- Below the diagonal: security.basicauth uses a module listed above it, which is the healthy direction.
31→27 security.basicauth uses security.authentication✕
- Connections
- 2 pairs of types, where a type in security.basicauth uses a type in security.authentication.
- The types involved
com.envimate.httpmate.security.basicauth.BasicAuthAuthenticator→com.envimate.httpmate.security.authentication.Authenticatorcom.envimate.httpmate.security.basicauth.BasicAuthConfigurator→com.envimate.httpmate.security.authentication.AuthenticatorConfigurator
- Direction
- security.basicauth uses security.authentication, so a change to security.authentication can break security.basicauth, while a change to security.basicauth can't break security.authentication.
- Position
- Below the diagonal: security.basicauth uses a module listed above it, which is the healthy direction.
31→35 security.basicauth uses security part of a loop✕
- Connections
- 1 pair of types, where a type in security.basicauth uses a type in security.
- The types involved
com.envimate.httpmate.security.basicauth.BasicAuthConfigurator→com.envimate.httpmate.security.Filter
- Direction
- security.basicauth uses security, so a change to security can break security.basicauth, while a change to security.basicauth can't break security.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→8 security.filtering uses chains✕
- Connections
- 2 pairs of types, where a type in security.filtering uses a type in chains.
- The types involved
com.envimate.httpmate.security.filtering.FilterConfigurator→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.security.filtering.FilterConfigurator→com.envimate.httpmate.chains.DependencyRegistry
- Direction
- security.filtering uses chains, so a change to chains can break security.filtering, while a change to security.filtering can't break chains.
- Position
- Below the diagonal: security.filtering uses a module listed above it, which is the healthy direction.
32→18 security.filtering uses security.config✕
- Connections
- 1 pair of types, where a type in security.filtering uses a type in security.config.
- The types involved
com.envimate.httpmate.security.filtering.FilterConfigurator→com.envimate.httpmate.security.config.SecurityConfigurator
- Direction
- security.filtering uses security.config, so a change to security.config can break security.filtering, while a change to security.filtering can't break security.config.
- Position
- Below the diagonal: security.filtering uses a module listed above it, which is the healthy direction.
32→22 security.filtering uses handler.http✕
- Connections
- 1 pair of types, where a type in security.filtering uses a type in handler.http.
- The types involved
com.envimate.httpmate.security.filtering.FilterConfigurator→com.envimate.httpmate.handler.http.HttpHandler
- Direction
- security.filtering uses handler.http, so a change to handler.http can break security.filtering, while a change to security.filtering can't break handler.http.
- Position
- Below the diagonal: security.filtering uses a module listed above it, which is the healthy direction.
32→28 security.filtering uses security.authorization✕
- Connections
- 1 pair of types, where a type in security.filtering uses a type in security.authorization.
- The types involved
com.envimate.httpmate.security.filtering.FilterConfigurator→com.envimate.httpmate.security.authorization.AuthorizerConfigurator
- Direction
- security.filtering uses security.authorization, so a change to security.authorization can break security.filtering, while a change to security.filtering can't break security.authorization.
- Position
- Below the diagonal: security.filtering uses a module listed above it, which is the healthy direction.
32→35 security.filtering uses security part of a loop✕
- Connections
- 1 pair of types, where a type in security.filtering uses a type in security.
- The types involved
com.envimate.httpmate.security.filtering.FilterConfigurator→com.envimate.httpmate.security.Filter
- Direction
- security.filtering uses security, so a change to security can break security.filtering, while a change to security.filtering can't break security.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→8 awslambda uses chains✕
- Connections
- 1 pair of types, where a type in awslambda uses a type in chains.
- The types involved
com.envimate.httpmate.awslambda.AwsLambdaEndpoint→com.envimate.httpmate.chains.MetaDataKey
- Direction
- awslambda uses chains, so a change to chains can break awslambda, while a change to awslambda can't break chains.
- Position
- Below the diagonal: awslambda uses a module listed above it, which is the healthy direction.
33→15 awslambda uses logger✕
- Connections
- 3 pairs of types, where a type in awslambda uses a type in logger.
- The types involved
com.envimate.httpmate.awslambda.AwsLambdaEndpoint→com.envimate.httpmate.logger.LoggerImplementationcom.envimate.httpmate.awslambda.AwsLambdaLogger→com.envimate.httpmate.logger.LogMessagecom.envimate.httpmate.awslambda.AwsLambdaLogger→com.envimate.httpmate.logger.LoggerImplementation
- Direction
- awslambda uses logger, so a change to logger can break awslambda, while a change to awslambda can't break logger.
- Position
- Below the diagonal: awslambda uses a module listed above it, which is the healthy direction.
33→29 awslambda uses com.envimate.httpmate✕
- Connections
- 1 pair of types, where a type in awslambda uses a type in com.envimate.httpmate.
- The types involved
com.envimate.httpmate.awslambda.AwsLambdaEndpoint→com.envimate.httpmate.HttpMate
- Direction
- awslambda uses com.envimate.httpmate, so a change to com.envimate.httpmate can break awslambda, while a change to awslambda can't break com.envimate.httpmate.
- Position
- Below the diagonal: awslambda uses a module listed above it, which is the healthy direction.
34→1 client uses client.body.multipart✕
- Connections
- 1 pair of types, where a type in client uses a type in client.body.multipart.
- The types involved
com.envimate.httpmate.client.HttpClientRequestBuilder→com.envimate.httpmate.client.body.multipart.Part
- Direction
- client uses client.body.multipart, so a change to client.body.multipart can break client, while a change to client can't break client.body.multipart.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
34→2 client uses filtermap✕
- Connections
- 2 pairs of types, where a type in client uses a type in filtermap.
- The types involved
com.envimate.httpmate.client.HttpMateClient→com.envimate.httpmate.filtermap.FilterMapcom.envimate.httpmate.client.HttpMateClientBuilder→com.envimate.httpmate.filtermap.FilterMapBuilder
- Direction
- client uses filtermap, so a change to filtermap can break client, while a change to client can't break filtermap.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
34→7 client uses client.issuer✕
- Connections
- 2 pairs of types, where a type in client uses a type in client.issuer.
- The types involved
com.envimate.httpmate.client.HttpMateClient→com.envimate.httpmate.client.issuer.Issuercom.envimate.httpmate.client.HttpMateClientBuilder→com.envimate.httpmate.client.issuer.Issuer
- Direction
- client uses client.issuer, so a change to client.issuer can break client, while a change to client can't break client.issuer.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
34→11 client uses client.clientbuilder✕
- Connections
- 1 pair of types, where a type in client uses a type in client.clientbuilder.
- The types involved
com.envimate.httpmate.client.HttpMateClient→com.envimate.httpmate.client.clientbuilder.PortStage
- Direction
- client uses client.clientbuilder, so a change to client.clientbuilder can break client, while a change to client can't break client.clientbuilder.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
34→29 client uses com.envimate.httpmate✕
- Connections
- 1 pair of types, where a type in client uses a type in com.envimate.httpmate.
- The types involved
com.envimate.httpmate.client.HttpMateClient→com.envimate.httpmate.HttpMate
- Direction
- client uses com.envimate.httpmate, so a change to com.envimate.httpmate can break client, while a change to client can't break com.envimate.httpmate.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
35→8 security uses chains✕
- Connections
- 9 pairs of types, where a type in security uses a type in chains.
- The types involved
com.envimate.httpmate.security.SecurityModule→com.envimate.httpmate.chains.ChainExtendercom.envimate.httpmate.security.SecurityModule→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.security.SecurityModule→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.security.SecurityProcessor→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.security.SecurityProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.security.SecurityProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.security.SimpleSecurityConfigurator→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.security.SimpleSecurityConfigurator→com.envimate.httpmate.chains.DependencyRegistrycom.envimate.httpmate.security.SimpleSecurityConfigurator→com.envimate.httpmate.chains.Processor
- Direction
- security uses chains, so a change to chains can break security, while a change to security can't break chains.
- Position
- Below the diagonal: security uses a module listed above it, which is the healthy direction.
35→18 security uses security.config✕
- Connections
- 1 pair of types, where a type in security uses a type in security.config.
- The types involved
com.envimate.httpmate.security.SimpleSecurityConfigurator→com.envimate.httpmate.security.config.SecurityConfigurator
- Direction
- security uses security.config, so a change to security.config can break security, while a change to security can't break security.config.
- Position
- Below the diagonal: security uses a module listed above it, which is the healthy direction.
35→22 security uses handler.http✕
- Connections
- 2 pairs of types, where a type in security uses a type in handler.http.
- The types involved
com.envimate.httpmate.security.Filter→com.envimate.httpmate.handler.http.HttpRequestcom.envimate.httpmate.security.SecurityConfigurators→com.envimate.httpmate.handler.http.HttpRequest
- Direction
- security uses handler.http, so a change to handler.http can break security, while a change to security can't break handler.http.
- Position
- Below the diagonal: security uses a module listed above it, which is the healthy direction.
35→27 security uses security.authentication✕
- Connections
- 2 pairs of types, where a type in security uses a type in security.authentication.
- The types involved
com.envimate.httpmate.security.SecurityConfigurators→com.envimate.httpmate.security.authentication.Authenticatorcom.envimate.httpmate.security.SecurityConfigurators→com.envimate.httpmate.security.authentication.AuthenticatorConfigurator
- Direction
- security uses security.authentication, so a change to security.authentication can break security, while a change to security can't break security.authentication.
- Position
- Below the diagonal: security uses a module listed above it, which is the healthy direction.
35→28 security uses security.authorization✕
- Connections
- 2 pairs of types, where a type in security uses a type in security.authorization.
- The types involved
com.envimate.httpmate.security.SecurityConfigurators→com.envimate.httpmate.security.authorization.AuthorizerConfiguratorcom.envimate.httpmate.security.SecurityConfigurators→com.envimate.httpmate.security.authorization.HttpAuthorizer
- Direction
- security uses security.authorization, so a change to security.authorization can break security, while a change to security can't break security.authorization.
- Position
- Below the diagonal: security uses a module listed above it, which is the healthy direction.
35→31 security uses security.basicauth✕
- Connections
- 2 pairs of types, where a type in security uses a type in security.basicauth.
- The types involved
com.envimate.httpmate.security.SecurityConfigurators→com.envimate.httpmate.security.basicauth.BasicAuthAuthenticatorcom.envimate.httpmate.security.SecurityConfigurators→com.envimate.httpmate.security.basicauth.BasicAuthConfigurator
- Direction
- security uses security.basicauth, so a change to security.basicauth can break security, while a change to security can't break security.basicauth.
- Position
- Below the diagonal: security uses a module listed above it, which is the healthy direction.
35→32 security uses security.filtering✕
- Connections
- 1 pair of types, where a type in security uses a type in security.filtering.
- The types involved
com.envimate.httpmate.security.SecurityConfigurators→com.envimate.httpmate.security.filtering.FilterConfigurator
- Direction
- security uses security.filtering, so a change to security.filtering can break security, while a change to security can't break security.filtering.
- Position
- Below the diagonal: security uses a module listed above it, which is the healthy direction.
36→29 websockets.registry uses com.envimate.httpmate✕
- Connections
- 1 pair of types, where a type in websockets.registry uses a type in com.envimate.httpmate.
- The types involved
com.envimate.httpmate.websockets.registry.WebSocketRegistry→com.envimate.httpmate.MetricsProvider
- Direction
- websockets.registry uses com.envimate.httpmate, so a change to com.envimate.httpmate can break websockets.registry, while a change to websockets.registry can't break com.envimate.httpmate.
- Position
- Below the diagonal: websockets.registry uses a module listed above it, which is the healthy direction.
36→38 websockets.registry uses websockets part of a loop✕
- Connections
- 1 pair of types, where a type in websockets.registry uses a type in websockets.
- The types involved
com.envimate.httpmate.websockets.registry.WebSocketRegistry→com.envimate.httpmate.websockets.WebSocket
- Direction
- websockets.registry uses websockets, so a change to websockets can break websockets.registry, while a change to websockets.registry can't break websockets.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→7 client.issuer.bypass uses client.issuer✕
- Connections
- 1 pair of types, where a type in client.issuer.bypass uses a type in client.issuer.
- The types involved
com.envimate.httpmate.client.issuer.bypass.BypassIssuer→com.envimate.httpmate.client.issuer.Issuer
- Direction
- client.issuer.bypass uses client.issuer, so a change to client.issuer can break client.issuer.bypass, while a change to client.issuer.bypass can't break client.issuer.
- Position
- Below the diagonal: client.issuer.bypass uses a module listed above it, which is the healthy direction.
37→29 client.issuer.bypass uses com.envimate.httpmate✕
- Connections
- 1 pair of types, where a type in client.issuer.bypass uses a type in com.envimate.httpmate.
- The types involved
com.envimate.httpmate.client.issuer.bypass.BypassIssuer→com.envimate.httpmate.HttpMate
- Direction
- client.issuer.bypass uses com.envimate.httpmate, so a change to com.envimate.httpmate can break client.issuer.bypass, while a change to client.issuer.bypass can't break com.envimate.httpmate.
- Position
- Below the diagonal: client.issuer.bypass uses a module listed above it, which is the healthy direction.
37→34 client.issuer.bypass uses client✕
- Connections
- 2 pairs of types, where a type in client.issuer.bypass uses a type in client.
- The types involved
com.envimate.httpmate.client.issuer.bypass.BypassIssuer→com.envimate.httpmate.client.HttpClientRequestcom.envimate.httpmate.client.issuer.bypass.BypassIssuer→com.envimate.httpmate.client.RawClientResponse
- Direction
- client.issuer.bypass uses client, so a change to client can break client.issuer.bypass, while a change to client.issuer.bypass can't break client.
- Position
- Below the diagonal: client.issuer.bypass uses a module listed above it, which is the healthy direction.
38→5 websockets uses path✕
- Connections
- 1 pair of types, where a type in websockets uses a type in path.
- The types involved
com.envimate.httpmate.websockets.WebSocketMapping→com.envimate.httpmate.path.PathTemplate
- Direction
- websockets uses path, so a change to path can break websockets, while a change to websockets can't break path.
- Position
- Below the diagonal: websockets uses a module listed above it, which is the healthy direction.
38→8 websockets uses chains✕
- Connections
- 18 pairs of types, where a type in websockets uses a type in chains.
- The types involved
com.envimate.httpmate.websockets.1→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.websockets.1→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.websockets.MetaDataEntriesToSave→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.websockets.MetaDataEntry→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.websockets.MetaDataEntryProvider→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.websockets.MetaDataEntryProvider→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.websockets.SavedMetaDataEntries→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.websockets.SavedMetaDataEntries→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.websockets.WebSocketForEventFilter→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.websockets.WebSocketMetrics→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.websockets.WebSocketModule→com.envimate.httpmate.chains.ChainExtendercom.envimate.httpmate.websockets.WebSocketModule→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.websockets.WebSocketModule→com.envimate.httpmate.chains.DependencyRegistrycom.envimate.httpmate.websockets.WebSocketsConfigurator→com.envimate.httpmate.chains.ChainModulecom.envimate.httpmate.websockets.WebSocketsConfigurator→com.envimate.httpmate.chains.Configuratorcom.envimate.httpmate.websockets.WebSocketsConfigurator→com.envimate.httpmate.chains.DependencyRegistrycom.envimate.httpmate.websockets.WebsocketChainKeys→com.envimate.httpmate.chains.MetaDataKeycom.envimate.httpmate.websockets.WebsocketChains→com.envimate.httpmate.chains.ChainName
- Direction
- websockets uses chains, so a change to chains can break websockets, while a change to websockets can't break chains.
- Position
- Below the diagonal: websockets uses a module listed above it, which is the healthy direction.
38→36 websockets uses websockets.registry✕
- Connections
- 3 pairs of types, where a type in websockets uses a type in websockets.registry.
- The types involved
com.envimate.httpmate.websockets.WebSocket→com.envimate.httpmate.websockets.registry.WebSocketIdcom.envimate.httpmate.websockets.WebsocketChainKeys→com.envimate.httpmate.websockets.registry.WebSocketIdcom.envimate.httpmate.websockets.WebsocketChainKeys→com.envimate.httpmate.websockets.registry.WebSocketRegistry
- Direction
- websockets uses websockets.registry, so a change to websockets.registry can break websockets, while a change to websockets can't break websockets.registry.
- Position
- Below the diagonal: websockets uses a module listed above it, which is the healthy direction.
39→29 servletwithwebsockets uses com.envimate.httpmate✕
- Connections
- 2 pairs of types, where a type in servletwithwebsockets uses a type in com.envimate.httpmate.
- The types involved
com.envimate.httpmate.servletwithwebsockets.JettyStyleWebSocket→com.envimate.httpmate.HttpMatecom.envimate.httpmate.servletwithwebsockets.WebSocketAwareHttpMateServlet→com.envimate.httpmate.HttpMate
- Direction
- servletwithwebsockets uses com.envimate.httpmate, so a change to com.envimate.httpmate can break servletwithwebsockets, while a change to servletwithwebsockets can't break com.envimate.httpmate.
- Position
- Below the diagonal: servletwithwebsockets uses a module listed above it, which is the healthy direction.
39→36 servletwithwebsockets uses websockets.registry✕
- Connections
- 1 pair of types, where a type in servletwithwebsockets uses a type in websockets.registry.
- The types involved
com.envimate.httpmate.servletwithwebsockets.JettyStyleWebSocket→com.envimate.httpmate.websockets.registry.WebSocketId
- Direction
- servletwithwebsockets uses websockets.registry, so a change to websockets.registry can break servletwithwebsockets, while a change to servletwithwebsockets can't break websockets.registry.
- Position
- Below the diagonal: servletwithwebsockets uses a module listed above it, which is the healthy direction.
39→38 servletwithwebsockets uses websockets✕
- Connections
- 1 pair of types, where a type in servletwithwebsockets uses a type in websockets.
- The types involved
com.envimate.httpmate.servletwithwebsockets.JettyStyleWebSocket→com.envimate.httpmate.websockets.WebSocketDelegate
- Direction
- servletwithwebsockets uses websockets, so a change to websockets can break servletwithwebsockets, while a change to servletwithwebsockets can't break websockets.
- Position
- Below the diagonal: servletwithwebsockets uses a module listed above it, which is the healthy direction.
40→8 websocketsevents uses chains✕
- Connections
- 5 pairs of types, where a type in websocketsevents uses a type in chains.
- The types involved
com.envimate.httpmate.websocketsevents.DetermineEventForWebSocketsProcessor→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.websocketsevents.DetermineEventForWebSocketsProcessor→com.envimate.httpmate.chains.Processorcom.envimate.httpmate.websocketsevents.EventMapping→com.envimate.httpmate.chains.MetaDatacom.envimate.httpmate.websocketsevents.WebSocketsExternalEventMapping→com.envimate.httpmate.chains.ChainNamecom.envimate.httpmate.websocketsevents.WebSocketsExternalEventMapping→com.envimate.httpmate.chains.MetaData
- Direction
- websocketsevents uses chains, so a change to chains can break websocketsevents, while a change to websocketsevents can't break chains.
- Position
- Below the diagonal: websocketsevents uses a module listed above it, which is the healthy direction.
40→14 websocketsevents uses generator✕
- Connections
- 1 pair of types, where a type in websocketsevents uses a type in generator.
- The types involved
com.envimate.httpmate.websocketsevents.Conditions→com.envimate.httpmate.generator.GenerationCondition
- Direction
- websocketsevents uses generator, so a change to generator can break websocketsevents, while a change to websocketsevents can't break generator.
- Position
- Below the diagonal: websocketsevents uses a module listed above it, which is the healthy direction.
40→23 websocketsevents uses events✕
- Connections
- 2 pairs of types, where a type in websocketsevents uses a type in events.
- The types involved
com.envimate.httpmate.websocketsevents.Conditions→com.envimate.httpmate.events.ExternalEventMappingcom.envimate.httpmate.websocketsevents.WebSocketsExternalEventMapping→com.envimate.httpmate.events.ExternalEventMapping
- Direction
- websocketsevents uses events, so a change to events can break websocketsevents, while a change to websocketsevents can't break events.
- Position
- Below the diagonal: websocketsevents uses a module listed above it, which is the healthy direction.
40→38 websocketsevents uses websockets✕
- Connections
- 4 pairs of types, where a type in websocketsevents uses a type in websockets.
- The types involved
com.envimate.httpmate.websocketsevents.Conditions→com.envimate.httpmate.websockets.WebSocketForEventFiltercom.envimate.httpmate.websocketsevents.IncomingEventMapping→com.envimate.httpmate.websockets.WebSocketForEventFiltercom.envimate.httpmate.websocketsevents.WebSocketsExternalEventMapping→com.envimate.httpmate.websockets.WebSocketcom.envimate.httpmate.websocketsevents.WebSocketsExternalEventMapping→com.envimate.httpmate.websockets.WebSocketForEventFilter
- Direction
- websocketsevents uses websockets, so a change to websockets can break websocketsevents, while a change to websocketsevents can't break websockets.
- Position
- Below the diagonal: websocketsevents 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 106 Orphaned file finding(s) in Knowledge Freshness — start with EventModule.java, CoreModule.java, UseCasesModule.java; 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; Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.2 pts | Medium | Architecture documentation |
| Resolve the 106 Orphaned file finding(s) in Knowledge Freshness — start with EventModule.java, CoreModule.java, UseCasesModule.java. | +10.3 pts | High | Knowledge Freshness |
| Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor). | +3.5 pts | Medium | Nullable reference types |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +2.0 pts | Medium | Observability |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.0 pts | Medium | Documentation (README) |
| Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers. | +1.5 pts | Medium | Library API & versioning |
| Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub. | +0.6 pts | Medium | Release Hygiene |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +0.2 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| integrations/jetty/src/main/java/com/envimate/httpmate/jetty/JettyEndpointHandler.java | 7.8 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| integrations/multipart/src/main/java/com/envimate/httpmate/multipart/internal/AbstractHttpServletRequestWithMockImplementations.java | 8.5 | Near-clean | God Classes: TooManyMethods: AbstractHttpServletRequestWithMockImplementations |
| core/src/main/java/com/envimate/httpmate/purejavaendpoint/PureJavaEndpointHandler.java | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| core/src/main/java/com/envimate/httpmate/http/headers/HeaderValueWithComment.java | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| integrations/client/src/main/java/com/envimate/httpmate/client/HttpClientRequestBuilder.java | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| core/src/main/java/com/envimate/httpmate/Configurators.java | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| examples/documentation/src/main/java/com/envimate/httpmate/documentation/authentication/CustomLoginExample.java | 8.5 | Near-clean | Code Duplication: Duplicated block (4–15 lines × 3) |
| examples/documentation/src/main/java/com/envimate/httpmate/documentation/xx_usecases/calculation/CalculationExample.java | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| examples/documentation/src/main/java/com/envimate/httpmate/documentation/download/JavaResourceExample.java | 8.5 | Near-clean | Code Duplication: Duplicated block (36 lines × 2) |
| tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: authenticationCanBeLimitedToCertainRoutes |
| tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/CookieSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: cookieCanBeInvalidated |
| tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/HttpMateSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: testContentTypeCanContainParameters |
| tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/LowLevelSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: testBodyOfADeleteRequest |
| tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/MarshallingSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: defaultContentTypeIsUsedForUnmarshallingIfNoContentTypeIsSpecified |
| tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/MultipartSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: testAuthenticationByFirstMultipartPart |
| tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/StaticFilesSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: aDirectoryLeadsToAnException |
| integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: testANormalRequestBeIssuedToAPathThatIsSpecifiedForNormalAndWebSocketRequests |
| integrations/client/src/test/java/com/envimate/httpmate/tests/ClientSpecs.java | 9.0 | Near-clean | Test Quality: No direct assertions: clientDoesNotAppendATrailingSlashToPathToDirectory |
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 54 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 — 54 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, 278 of 289 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — 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 (.java) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Not scored — a Maven build resolved 1 artifact(s) (1 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 77 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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 defines its own container in core/src/main/java/com/envimate/httpmate/chains/DependencyRegistry.java, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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").
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with AbstractHttpServletRequestWithMockImplementations.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
9 duplicated block group(s) detected. 3 of the 9 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 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with JettyEndpointHandler.java, Configurators.java. — 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 HttpClientRequestBuilder.java, CalculationExample.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with PureJavaEndpointHandler.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
18 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 15 of the 18 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 149 classes have LCOM4 above 3.
D9 · Test Distribution
151 test methods: 151 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
7 skipped (7 with a documented reason), 142 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 151 tests (3 harness-style project(s) excluded from the assertion penalty).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 20266 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 33 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 15 build units (Maven) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
72 % of calls cross a namespace and 7 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
106 of 106 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is integrations/events/src/main/java/com/envimate/httpmate/events/EventModule.java. Counted over 106 of the 334 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 106 Orphaned file finding(s) in Knowledge Freshness — start with EventModule.java, CoreModule.java, UseCasesModule.java. — One of this dimension's main actionable groups (106 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 0 platform declaration(s) and 86 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×7) — integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:182, integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:193, integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:206, …
What to do
- Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 20 of 21 project(s) that lack one — worth up to 1.9 pts.
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
- 297/342 types (87%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P2 · Observability
- Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `core`, `integrations/servlet`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 168 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- The changelog this check read carries 1 versioned entry, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
What to do
- Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 0/73 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 74% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 49% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 51% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Checked 5 of 11 | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — 60 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Not scored — a Maven build resolved 1 artifact(s) (1 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Not scored — this repository's 60 declared JVM dependency coordinate(s) were read from its 25 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 2 of them (POM at http://172.31.7.1:8790/maven/com/amazonaws/aws-lambda-java-events/2.2.7/aws-lambda-java-events-2.2.7.pom could not be parsed), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 94 value object(s); a Domain/Aggregates/ValueObjects layer
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- 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.
- 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 — 3 finding(s)
- REDACTED
- REDACTED
- REDACTED
Serious — 11 finding(s)
- Duplicated block (7 lines × 2) integrations/jetty/src/main/java/com/envimate/httpmate/jetty/JettyEndpointHandler.java:90
- Duplicated block (7 lines × 2) core/src/main/java/com/envimate/httpmate/Configurators.java:34
- Duplicated block (8 lines × 2) integrations/client/src/main/java/com/envimate/httpmate/client/HttpClientRequestBuilder.java:117
- Duplicated block (8 lines × 2) examples/documentation/src/main/java/com/envimate/httpmate/documentation/xx_usecases/calculation/CalculationExample.java:40
- TooManyMethods: AbstractHttpServletRequestWithMockImplementations integrations/multipart/src/main/java/com/envimate/httpmate/multipart/internal/AbstractHttpServletRequestWithMockImplementations.java:36
- Duplicated block (10 lines × 2) core/src/main/java/com/envimate/httpmate/purejavaendpoint/PureJavaEndpointHandler.java:60
- Duplicated block (9 lines × 2) integrations/jetty/src/main/java/com/envimate/httpmate/jetty/JettyEndpointHandler.java:77
- Duplicated block (5 lines × 2) core/src/main/java/com/envimate/httpmate/http/headers/HeaderValueWithComment.java:46
- Duplicated block (4–15 lines × 3) examples/documentation/src/main/java/com/envimate/httpmate/documentation/authentication/CustomLoginExample.java:54
- Duplicated block (36 lines × 2) examples/documentation/src/main/java/com/envimate/httpmate/documentation/download/JavaResourceExample.java:1
- Off the main sequence: core
Minor — 268 finding(s)
- No direct assertions: authenticationCanBeLimitedToCertainRoutes tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java:151
- No direct assertions: requestsCanBeAuthenticatedWithBody tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java:103
- No direct assertions: requestsCanBeAuthenticatedWithCookie tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java:55
- No direct assertions: requestsCanBeAuthenticatedWithHeader tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java:39
- No direct assertions: requestsCanBeAuthenticatedWithOAuth2BearerToken tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java:119
- No direct assertions: requestsCanBeAuthenticatedWithPathParameter tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java:87
- No direct assertions: requestsCanBeAuthenticatedWithQueryParameter tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java:71
- No direct assertions: routesCanBeExcludedFromAuthentication tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthenticationSpecs.java:135
- No direct assertions: authorizationCanBeLimitedToCertainRoutes tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthorizationSpecs.java:83
- No direct assertions: rejectionCanBeConfigured tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthorizationSpecs.java:51
- No direct assertions: routesCanBeExcludedFromAuthorization tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthorizationSpecs.java:69
- No direct assertions: unauthorizedRequestsCanBeRejected tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/AuthorizationSpecs.java:37
- No direct assertions: messageCanBeSet tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/BasicAuthSpecs.java:83
- No direct assertions: requestWithCorrectCredentialsDoNotGetRejected tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/BasicAuthSpecs.java:68
- No direct assertions: requestWithWrongCredentialsGetsRejected tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/BasicAuthSpecs.java:53
- No direct assertions: unauthenticatedRequestsAreRejected tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/BasicAuthSpecs.java:39
- No direct assertions: requestsCanBeFiltered tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/aaa/FilterSpecs.java:37
- No direct assertions: testEventsCanBeTriggered tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/events/EventSpecs.java:35
- No direct assertions: mapMateIntegrationCanHelpWithValidation tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/mapmate/MapMateSpecs.java:105
- No direct assertions: mapMateIntegrationCanUnmarshalCustomFormat tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/mapmate/MapMateSpecs.java:67
- No direct assertions: mapMateIntegrationCanUnmarshalFormEncodedButDoesNotMarshalFormEncodedByDefault tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/mapmate/MapMateSpecs.java:77
- No direct assertions: mapMateIntegrationCorrectlyUnmarshallsWithoutSpecifiedRequestContentType tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/mapmate/MapMateSpecs.java:87
- No direct assertions: aUseCaseWithNoParametersAndVoidReturnTypeCanBeInvokedWithoutConfiguringAnySerializers tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/usecase/UseCaseSpecs.java:42
- No direct assertions: checkedExceptionInUseCaseCanBeCaughtInSpecializedHandler tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/usecase/UseCaseSpecs.java:85
- No direct assertions: exceptionInInitializerCanBeCaughtInDefaultHandler tests/testsuite/src/test/java/com/envimate/httpmate/tests/lowlevel/usecase/UseCaseSpecs.java:72
- Orphaned file integrations/events/src/main/java/com/envimate/httpmate/events/EventModule.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/CoreModule.java:1
- Orphaned file integrations/usecases/src/main/java/com/envimate/httpmate/usecases/UseCasesModule.java:1
- Orphaned file integrations/mapmate/src/main/java/com/envimate/httpmate/mapmate/MapMateSerializerAndDeserializer.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/marshalling/MarshallingModule.java:1
- Orphaned file integrations/multipart/src/main/java/com/envimate/httpmate/multipart/internal/AbstractHttpServletRequestWithMockImplementations.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/chains/ChainRegistry.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/handler/http/HttpResponse.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/chains/GraphCreator.java:1
- Orphaned file integrations/websocket/src/main/java/com/envimate/httpmate/websockets/WebSocketModule.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/cors/CorsConfigurator.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/HttpMateBuilder.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/security/SecurityConfigurators.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/security/authentication/AuthenticatorConfigurator.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/http/headers/cookies/CookieBuilder.java:1
- Orphaned file integrations/client/src/main/java/com/envimate/httpmate/client/issuer/real/RealIssuer.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/chains/ChainExtender.java:1
- Orphaned file integrations/client/src/main/java/com/envimate/httpmate/client/HttpClientRequestBuilder.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/util/describing/CardBuilder.java:1
- Orphaned file integrations/client/src/main/java/com/envimate/httpmate/client/HttpMateClientBuilder.java:1
- Orphaned file integrations/jetty/src/main/java/com/envimate/httpmate/jetty/JettyEndpointHandler.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/path/PathTemplate.java:1
- Orphaned file integrations/servlet/src/main/java/com/envimate/httpmate/servlet/ServletHandling.java:1
- Orphaned file core/src/main/java/com/envimate/httpmate/util/Maps.java:1
- Orphaned file integrations/events/src/main/java/com/envimate/httpmate/events/EventConfigurators.java:1
- Disabled test integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:182
- Disabled test integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:193
- Disabled test integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:206
- Disabled test integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:226
- Disabled test integrations/jetty-with-websockets/src/test/java/websockets/lowlevel/LowLevelSpecs.java:49
- Disabled test integrations/jetty-with-websockets/src/test/java/websockets/lowlevel/LowLevelSpecs.java:60
- Disabled test integrations/jetty-with-websockets/src/test/java/websockets/lowlevel/UseCasesWithWebsocketsSpecs.java:34
- Test project verifies nothing: httpmate-client integrations/client/src/test/java/com/envimate/httpmate/tests/ClientSpecs.java:34
- Test project verifies nothing: maven-surefire-plugin integrations/jetty-with-websockets/src/test/java/websockets/lowlevel/LowLevelSpecs.java:33
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- No ADRs
- No architecture diagram/doc
- Large public API surface
- Logging is not universal
- No SAST
- Changelog looks stale/thin
- Java packages are not null-marked everywhere
- Silent fallback default on parse failure core/src/main/java/com/envimate/httpmate/chains/autoloading/Autoloader.java:58
Minor — 7 finding(s)
- Skipped (documented): testMetaDataEntriesFromWebSocketEstablishmentCanBeSavedAndRestoredInWebSocketMessages integrations/jetty-with-websockets/src/test/java/websockets/lowlevel/LowLevelSpecs.java:51
- Skipped (documented): testTheLoggerIsAvailableDuringWebSocketMessageProcessing integrations/jetty-with-websockets/src/test/java/websockets/lowlevel/LowLevelSpecs.java:62
- Skipped (documented): useCaseCanBeCalledOnWebSocketMessage integrations/jetty-with-websockets/src/test/java/websockets/lowlevel/UseCasesWithWebsocketsSpecs.java:36
- Skipped (documented): testAMultiBrowsertabAwareChatServerCanBeImplemented integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:195
- Skipped (documented): testASendingUseCaseCanDistinguishBetweenDifferentGroupsOfWebSockets integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:208
- Skipped (documented): testAWebSocketCanReceiveArbitraryMessagesFromUseCases integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:184
- Skipped (documented): testAWebSocketThatGetsClosedByTheClientWillGetCleanedUp integrations/jetty-with-websockets/src/test/java/websockets/WebSocketsSpecs.java:228
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-d0778aeb5e854773bc04c14c7c0f85e2/history.json --exit-code 0 --source . | 0 | 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-d0778aeb5e854773bc04c14c7c0f85e2/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 . | 0 | 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 . | 3 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| 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 . | 0 | artifacts/raw/osv-scanner.json |