Executive summary
h2oai/sparkling-water is rated At risk because critical security findings are open, most of them in its servers and containers. Its score is held back because 192 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 57 out of 100, which the At risk rating leaves unchanged.
Maturity, at 49, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 7 points. Recording design decisions comes next, also worth about 7. Raising Maturity to 70 would lift the score to about 63.
Twenty-one settings leave the servers or containers unsafe. Two pipeline steps run downloads nobody checks, and one password or key is open to anyone who can read the repository. Correcting the unsafe settings, checking each download against a checksum and replacing the exposed password or key would close these risks. The two tests the project itself marks as unreliable need fixing or deleting.
The product code is 34,649 lines, about €51,000 to rebuild.
If Maturity rose from 49 to 70, the lowest score rated Strong, the score would rise from 57 to about 63.
Rebuild cost: about €51,000 · Estimate
| Cost to rebuild | €17,000 to €86,000, for 285 to 904 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 34,649 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: which parts of the code depend on which
| uses → | 1 ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate | 2 org.apache.spark.expose | 3 org.apache.spark.ml.util.expose.DefaultParamsReader | 4 py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase | 5 py-scoring.src.ai.h2o.sparkling.ml.params.H2OCommonParams | 6 py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputCol | 7 py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO | 8 py.src.ai.h2o.sparkling.ml.H2OStageBase | 9 ai.h2o.sparkling.api.generation.common | 10 ai.h2o.sparkling.backend.converters | 11 ai.h2o.sparkling.backend.utils | 12 ai.h2o.sparkling.repl | 13 org.apache.spark.h2o.ui | 14 py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase | 15 py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO | 16 py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams | 17 py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO | 18 py.src.ai.h2o.sparkling.ml.algos.H2OEstimator | 19 ai.h2o.sparkling.backend | 20 py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams | 21 py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm | 22 py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator | 23 ai.h2o.sparkling.backend.external | 24 ai.h2o.sparkling.backend.internal | 25 py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel | 26 py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase | 27 ai.h2o.sparkling | 28 ai.h2o.sparkling.backend.api | 29 ai.h2o.sparkling.ml.utils | 30 org.apache.spark.h2o.backends.internal | 31 ai.h2o.sparkling.backend.api.dataframes | 32 ai.h2o.sparkling.backend.api.h2oframes | 33 ai.h2o.sparkling.backend.api.rdds | 34 ai.h2o.sparkling.backend.api.scalainterpreter | 35 ai.h2o.sparkling.ml.params | 36 ai.h2o.sparkling.ml.metrics | 37 ai.h2o.sparkling.ml.models | 38 ai.h2o.sparkling.ml.algos | 39 ai.h2o.sparkling.ml.internals | 40 ai.h2o.sparkling.ml.features |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate | ||||||||||||||||||||||||||||||||||||||||
| 2 org.apache.spark.expose | ||||||||||||||||||||||||||||||||||||||||
| 3 org.apache.spark.ml.util.expose.DefaultParamsReader | ||||||||||||||||||||||||||||||||||||||||
| 4 py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase | ||||||||||||||||||||||||||||||||||||||||
| 5 py-scoring.src.ai.h2o.sparkling.ml.params.H2OCommonParams | ||||||||||||||||||||||||||||||||||||||||
| 6 py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputCol | ||||||||||||||||||||||||||||||||||||||||
| 7 py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO | ||||||||||||||||||||||||||||||||||||||||
| 8 py.src.ai.h2o.sparkling.ml.H2OStageBase | ||||||||||||||||||||||||||||||||||||||||
| 9 ai.h2o.sparkling.api.generation.common | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 ai.h2o.sparkling.backend.converters | 5 | 2 | 10 | |||||||||||||||||||||||||||||||||||||
| 11 ai.h2o.sparkling.backend.utils | 4 | 5 | 4 | 11 | ||||||||||||||||||||||||||||||||||||
| 12 ai.h2o.sparkling.repl | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 org.apache.spark.h2o.ui | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 py.src.ai.h2o.sparkling.ml.algos.H2OEstimator | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 ai.h2o.sparkling.backend | 6 | 1 | 1 | 1 | 1 | 12 | ||||||||||||||||||||||||||||||||||
| 20 py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 ai.h2o.sparkling.backend.external | 2 | 3 | 1 | 3 | 6 | |||||||||||||||||||||||||||||||||||
| 24 ai.h2o.sparkling.backend.internal | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 ai.h2o.sparkling | 2 | 1 | 2 | 2 | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 28 ai.h2o.sparkling.backend.api | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 ai.h2o.sparkling.ml.utils | 1 | 2 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 org.apache.spark.h2o.backends.internal | 1 | 2 | 2 | 2 | 5 | |||||||||||||||||||||||||||||||||||
| 31 ai.h2o.sparkling.backend.api.dataframes | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 ai.h2o.sparkling.backend.api.h2oframes | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 ai.h2o.sparkling.backend.api.rdds | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 ai.h2o.sparkling.backend.api.scalainterpreter | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 ai.h2o.sparkling.ml.params | 11 | 1 | 22 | 1 | 1 | 8 | 7 | |||||||||||||||||||||||||||||||||
| 36 ai.h2o.sparkling.ml.metrics | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 ai.h2o.sparkling.ml.models | 2 | 5 | 2 | 1 | 22 | 2 | ||||||||||||||||||||||||||||||||||
| 38 ai.h2o.sparkling.ml.algos | 4 | 5 | 8 | 2 | 5 | 13 | ||||||||||||||||||||||||||||||||||
| 39 ai.h2o.sparkling.ml.internals | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 40 ai.h2o.sparkling.ml.features | 1 | 1 | 1 | 8 | 5 | 1 |
9→1 ai.h2o.sparkling.api.generation.common uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 3 pairs of types, where a type in ai.h2o.sparkling.api.generation.common uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.api.generation.common.AlgorithmSubstitutionContext→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.api.generation.common.DeprecatedField→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.api.generation.common.ExplicitField→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.api.generation.common uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.api.generation.common, while a change to ai.h2o.sparkling.api.generation.common can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.api.generation.common uses a module listed above it, which is the healthy direction.
10→1 ai.h2o.sparkling.backend.converters uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 5 pairs of types, where a type in ai.h2o.sparkling.backend.converters uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.backend.converters.SparkDataFrameConverter→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.converters.SupportedDataset→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.converters.SupportedDatasetConverter→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.converters.SupportedRDD→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.converters.SupportedRDDConverter→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.backend.converters uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.backend.converters, while a change to ai.h2o.sparkling.backend.converters can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.converters uses a module listed above it, which is the healthy direction.
10→2 ai.h2o.sparkling.backend.converters uses org.apache.spark.expose✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.backend.converters uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.backend.converters.SparkDataFrameConverter→org.apache.spark.expose.Loggingai.h2o.sparkling.backend.converters.SupportedDatasetConverter→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.backend.converters uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.backend.converters, while a change to ai.h2o.sparkling.backend.converters can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.converters uses a module listed above it, which is the healthy direction.
10→27 ai.h2o.sparkling.backend.converters uses ai.h2o.sparkling part of a loop✕
- Connections
- 10 pairs of types, where a type in ai.h2o.sparkling.backend.converters uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.backend.converters.SparkDataFrameConverter→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.converters.SparkDataFrameConverter→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.converters.SupportedDataset→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.converters.SupportedDataset→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.converters.SupportedDatasetConverter→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.converters.SupportedDatasetConverter→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.converters.SupportedRDD→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.converters.SupportedRDD→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.converters.SupportedRDDConverter→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.converters.SupportedRDDConverter→ai.h2o.sparkling.H2OFrame
- Direction
- ai.h2o.sparkling.backend.converters uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.backend.converters, while a change to ai.h2o.sparkling.backend.converters can't break ai.h2o.sparkling.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→1 ai.h2o.sparkling.backend.utils uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 4 pairs of types, where a type in ai.h2o.sparkling.backend.utils uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.backend.utils.ArgumentBuilder→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.utils.H2OFrameLifecycle→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.utils.RestCommunication→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.utils.SharedBackendUtils→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.backend.utils uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.backend.utils, while a change to ai.h2o.sparkling.backend.utils can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.utils uses a module listed above it, which is the healthy direction.
11→2 ai.h2o.sparkling.backend.utils uses org.apache.spark.expose✕
- Connections
- 5 pairs of types, where a type in ai.h2o.sparkling.backend.utils uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.backend.utils.AzureDatabricksUtils→org.apache.spark.expose.Loggingai.h2o.sparkling.backend.utils.ProxyStarter→org.apache.spark.expose.Loggingai.h2o.sparkling.backend.utils.RestCommunication→org.apache.spark.expose.Loggingai.h2o.sparkling.backend.utils.SharedBackendUtils→org.apache.spark.expose.Loggingai.h2o.sparkling.backend.utils.ShellUtils→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.backend.utils uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.backend.utils, while a change to ai.h2o.sparkling.backend.utils can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.utils uses a module listed above it, which is the healthy direction.
11→19 ai.h2o.sparkling.backend.utils uses ai.h2o.sparkling.backend part of a loop✕
- Connections
- 4 pairs of types, where a type in ai.h2o.sparkling.backend.utils uses a type in ai.h2o.sparkling.backend.
- The types involved
ai.h2o.sparkling.backend.utils.H2OContextExtensions→ai.h2o.sparkling.backend.NodeDescai.h2o.sparkling.backend.utils.RestApiUtils→ai.h2o.sparkling.backend.NodeDescai.h2o.sparkling.backend.utils.RestCommunication→ai.h2o.sparkling.backend.NodeDescai.h2o.sparkling.backend.utils.SharedBackendUtils→ai.h2o.sparkling.backend.NodeDesc
- Direction
- ai.h2o.sparkling.backend.utils uses ai.h2o.sparkling.backend, so a change to ai.h2o.sparkling.backend can break ai.h2o.sparkling.backend.utils, while a change to ai.h2o.sparkling.backend.utils can't break ai.h2o.sparkling.backend.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→27 ai.h2o.sparkling.backend.utils uses ai.h2o.sparkling part of a loop✕
- Connections
- 11 pairs of types, where a type in ai.h2o.sparkling.backend.utils uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.backend.utils.AzureDatabricksUtils→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.utils.H2OContextExtensions→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.utils.H2OContextExtensions→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.utils.H2OFrameLifecycle→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.utils.ProxyStarter→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.utils.ProxyStarter→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.utils.ReflectionUtils→ai.h2o.sparkling.H2OColumnai.h2o.sparkling.backend.utils.RestApiUtils→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.utils.RestCommunication→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.utils.SecurityUtils→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.utils.SharedBackendUtils→ai.h2o.sparkling.H2OConf
- Direction
- ai.h2o.sparkling.backend.utils uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.backend.utils, while a change to ai.h2o.sparkling.backend.utils can't break ai.h2o.sparkling.
- 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→1 ai.h2o.sparkling.repl uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.repl uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.repl.BaseH2OInterpreter→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.repl.H2OInterpreter→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.repl uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.repl, while a change to ai.h2o.sparkling.repl can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.repl uses a module listed above it, which is the healthy direction.
12→2 ai.h2o.sparkling.repl uses org.apache.spark.expose✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.repl uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.repl.BaseH2OInterpreter→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.repl uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.repl, while a change to ai.h2o.sparkling.repl can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.repl uses a module listed above it, which is the healthy direction.
13→1 org.apache.spark.h2o.ui uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 2 pairs of types, where a type in org.apache.spark.h2o.ui uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
org.apache.spark.h2o.ui.AppStatusStore→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionorg.apache.spark.h2o.ui.SparklingWaterListener→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- org.apache.spark.h2o.ui uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break org.apache.spark.h2o.ui, while a change to org.apache.spark.h2o.ui can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: org.apache.spark.h2o.ui uses a module listed above it, which is the healthy direction.
13→2 org.apache.spark.h2o.ui uses org.apache.spark.expose✕
- Connections
- 2 pairs of types, where a type in org.apache.spark.h2o.ui uses a type in org.apache.spark.expose.
- The types involved
org.apache.spark.h2o.ui.AppStatusListener→org.apache.spark.expose.Loggingorg.apache.spark.h2o.ui.SparklingWaterListener→org.apache.spark.expose.Logging
- Direction
- org.apache.spark.h2o.ui uses org.apache.spark.expose, so a change to org.apache.spark.expose can break org.apache.spark.h2o.ui, while a change to org.apache.spark.h2o.ui can't break org.apache.spark.expose.
- Position
- Below the diagonal: org.apache.spark.h2o.ui uses a module listed above it, which is the healthy direction.
14→4 py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase uses py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase uses a type in py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase.H2OAlgorithmMOJOModelBase→py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase.H2OMOJOModelBase
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase uses py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase, so a change to py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase can break py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase, while a change to py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase can't break py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase uses a module listed above it, which is the healthy direction.
15→7 py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO uses py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO uses a type in py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO.H2OAutoEncoderExtraParamsOnMOJO→py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.HasOutputColOnMOJO
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO uses py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO, so a change to py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO can break py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO, while a change to py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO can't break py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsOnMOJO uses a module listed above it, which is the healthy direction.
16→6 py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams uses py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputCol✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams uses a type in py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputCol.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams.H2ODimReductionExtraParams→py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputCol.HasOutputCol
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams uses py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputCol, so a change to py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputCol can break py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams, while a change to py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams can't break py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputCol.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParams uses a module listed above it, which is the healthy direction.
17→7 py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO uses py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO uses a type in py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO.H2ODimReductionExtraParamsOnMOJO→py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.HasOutputColOnMOJO
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO uses py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO, so a change to py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO can break py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO, while a change to py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO can't break py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO uses a module listed above it, which is the healthy direction.
18→8 py.src.ai.h2o.sparkling.ml.algos.H2OEstimator uses py.src.ai.h2o.sparkling.ml.H2OStageBase✕
- Connections
- 1 pair of types, where a type in py.src.ai.h2o.sparkling.ml.algos.H2OEstimator uses a type in py.src.ai.h2o.sparkling.ml.H2OStageBase.
- The types involved
py.src.ai.h2o.sparkling.ml.algos.H2OEstimator.H2OEstimator→py.src.ai.h2o.sparkling.ml.H2OStageBase.H2OStageBase
- Direction
- py.src.ai.h2o.sparkling.ml.algos.H2OEstimator uses py.src.ai.h2o.sparkling.ml.H2OStageBase, so a change to py.src.ai.h2o.sparkling.ml.H2OStageBase can break py.src.ai.h2o.sparkling.ml.algos.H2OEstimator, while a change to py.src.ai.h2o.sparkling.ml.algos.H2OEstimator can't break py.src.ai.h2o.sparkling.ml.H2OStageBase.
- Position
- Below the diagonal: py.src.ai.h2o.sparkling.ml.algos.H2OEstimator uses a module listed above it, which is the healthy direction.
19→1 ai.h2o.sparkling.backend uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 6 pairs of types, where a type in ai.h2o.sparkling.backend uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.backend.H2ORDD→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.PartitionStats→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.PartitionStatsGenerator→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.Reader→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.SharedBackendConf→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.WriterMetadata→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.backend uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.backend, while a change to ai.h2o.sparkling.backend can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.backend uses a module listed above it, which is the healthy direction.
19→2 ai.h2o.sparkling.backend uses org.apache.spark.expose✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.backend.H2OJob→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.backend uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.backend, while a change to ai.h2o.sparkling.backend can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.backend uses a module listed above it, which is the healthy direction.
19→3 ai.h2o.sparkling.backend uses org.apache.spark.ml.util.expose.DefaultParamsReader✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend uses a type in org.apache.spark.ml.util.expose.DefaultParamsReader.
- The types involved
ai.h2o.sparkling.backend.H2OFrameRelation→org.apache.spark.ml.util.expose.DefaultParamsReader.Metadata
- Direction
- ai.h2o.sparkling.backend uses org.apache.spark.ml.util.expose.DefaultParamsReader, so a change to org.apache.spark.ml.util.expose.DefaultParamsReader can break ai.h2o.sparkling.backend, while a change to ai.h2o.sparkling.backend can't break org.apache.spark.ml.util.expose.DefaultParamsReader.
- Position
- Below the diagonal: ai.h2o.sparkling.backend uses a module listed above it, which is the healthy direction.
19→10 ai.h2o.sparkling.backend uses ai.h2o.sparkling.backend.converters✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend uses a type in ai.h2o.sparkling.backend.converters.
- The types involved
ai.h2o.sparkling.backend.Reader→ai.h2o.sparkling.backend.converters.TimeZoneConversions
- Direction
- ai.h2o.sparkling.backend uses ai.h2o.sparkling.backend.converters, so a change to ai.h2o.sparkling.backend.converters can break ai.h2o.sparkling.backend, while a change to ai.h2o.sparkling.backend can't break ai.h2o.sparkling.backend.converters.
- Position
- Below the diagonal: ai.h2o.sparkling.backend uses a module listed above it, which is the healthy direction.
19→11 ai.h2o.sparkling.backend uses ai.h2o.sparkling.backend.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.backend.H2ORDD→ai.h2o.sparkling.backend.utils.ProductType
- Direction
- ai.h2o.sparkling.backend uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.backend, while a change to ai.h2o.sparkling.backend can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.backend uses a module listed above it, which is the healthy direction.
19→27 ai.h2o.sparkling.backend uses ai.h2o.sparkling part of a loop✕
- Connections
- 12 pairs of types, where a type in ai.h2o.sparkling.backend uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.backend.H2OContextImplicits→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.H2OContextImplicits→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.H2ODataFrame→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.H2ODataFrame→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.H2OFrameRelation→ai.h2o.sparkling.H2OColumnai.h2o.sparkling.backend.H2OFrameRelation→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.H2ORDD→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.H2ORDD→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.H2OSparkEntity→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.backend.SharedBackendConf→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.SparklingBackend→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.WriterMetadata→ai.h2o.sparkling.H2OConf
- Direction
- ai.h2o.sparkling.backend uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.backend, while a change to ai.h2o.sparkling.backend can't break ai.h2o.sparkling.
- 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.
20→4 py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams uses py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams uses a type in py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams.H2OFeatureMOJOModelParams→py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase.H2OMOJOModelBase
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams uses py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase, so a change to py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase can break py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams, while a change to py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams can't break py-scoring.src.ai.h2o.sparkling.ml.models.H2OMOJOModelBase.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams uses a module listed above it, which is the healthy direction.
20→14 py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams uses py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams uses a type in py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams.H2OAlgorithmMOJOModelParams→py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase.H2OAlgorithmMOJOModelBase
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams uses py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase, so a change to py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase can break py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams, while a change to py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams can't break py-scoring.src.ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelBase.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams uses a module listed above it, which is the healthy direction.
21→18 py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm uses py.src.ai.h2o.sparkling.ml.algos.H2OEstimator✕
- Connections
- 1 pair of types, where a type in py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm uses a type in py.src.ai.h2o.sparkling.ml.algos.H2OEstimator.
- The types involved
py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm.H2OAlgorithm→py.src.ai.h2o.sparkling.ml.algos.H2OEstimator.H2OEstimator
- Direction
- py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm uses py.src.ai.h2o.sparkling.ml.algos.H2OEstimator, so a change to py.src.ai.h2o.sparkling.ml.algos.H2OEstimator can break py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm, while a change to py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm can't break py.src.ai.h2o.sparkling.ml.algos.H2OEstimator.
- Position
- Below the diagonal: py.src.ai.h2o.sparkling.ml.algos.H2OAlgorithm uses a module listed above it, which is the healthy direction.
22→18 py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator uses py.src.ai.h2o.sparkling.ml.algos.H2OEstimator✕
- Connections
- 1 pair of types, where a type in py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator uses a type in py.src.ai.h2o.sparkling.ml.algos.H2OEstimator.
- The types involved
py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator.H2OFeatureEstimator→py.src.ai.h2o.sparkling.ml.algos.H2OEstimator.H2OEstimator
- Direction
- py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator uses py.src.ai.h2o.sparkling.ml.algos.H2OEstimator, so a change to py.src.ai.h2o.sparkling.ml.algos.H2OEstimator can break py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator, while a change to py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator can't break py.src.ai.h2o.sparkling.ml.algos.H2OEstimator.
- Position
- Below the diagonal: py.src.ai.h2o.sparkling.ml.features.H2OFeatureEstimator uses a module listed above it, which is the healthy direction.
23→1 ai.h2o.sparkling.backend.external uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.backend.external uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.backend.external.ExternalBackendConf→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.backend.external.ExternalH2OBackend→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.backend.external uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.backend.external, while a change to ai.h2o.sparkling.backend.external can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.external uses a module listed above it, which is the healthy direction.
23→2 ai.h2o.sparkling.backend.external uses org.apache.spark.expose✕
- Connections
- 3 pairs of types, where a type in ai.h2o.sparkling.backend.external uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.backend.external.ExternalBackendConf→org.apache.spark.expose.Loggingai.h2o.sparkling.backend.external.ExternalBackendConfExtensions→org.apache.spark.expose.Loggingai.h2o.sparkling.backend.external.K8sExternalBackendClient→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.backend.external uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.backend.external, while a change to ai.h2o.sparkling.backend.external can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.external uses a module listed above it, which is the healthy direction.
23→11 ai.h2o.sparkling.backend.external uses ai.h2o.sparkling.backend.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.external uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.backend.external.ExternalH2OBackend→ai.h2o.sparkling.backend.utils.ShellUtils
- Direction
- ai.h2o.sparkling.backend.external uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.backend.external, while a change to ai.h2o.sparkling.backend.external can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.external uses a module listed above it, which is the healthy direction.
23→19 ai.h2o.sparkling.backend.external uses ai.h2o.sparkling.backend✕
- Connections
- 3 pairs of types, where a type in ai.h2o.sparkling.backend.external uses a type in ai.h2o.sparkling.backend.
- The types involved
ai.h2o.sparkling.backend.external.ExternalBackendConf→ai.h2o.sparkling.backend.SharedBackendConfai.h2o.sparkling.backend.external.ExternalBackendConfExtensions→ai.h2o.sparkling.backend.SharedBackendConfai.h2o.sparkling.backend.external.ExternalH2OBackend→ai.h2o.sparkling.backend.SparklingBackend
- Direction
- ai.h2o.sparkling.backend.external uses ai.h2o.sparkling.backend, so a change to ai.h2o.sparkling.backend can break ai.h2o.sparkling.backend.external, while a change to ai.h2o.sparkling.backend.external can't break ai.h2o.sparkling.backend.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.external uses a module listed above it, which is the healthy direction.
23→27 ai.h2o.sparkling.backend.external uses ai.h2o.sparkling part of a loop✕
- Connections
- 6 pairs of types, where a type in ai.h2o.sparkling.backend.external uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.backend.external.ExternalBackendConf→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.external.ExternalH2OBackend→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.external.ExternalH2OBackend→ai.h2o.sparkling.H2OContextai.h2o.sparkling.backend.external.K8sExternalBackendClient→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.external.K8sH2OStatefulSet→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.external.K8sHeadlessService→ai.h2o.sparkling.H2OConf
- Direction
- ai.h2o.sparkling.backend.external uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.backend.external, while a change to ai.h2o.sparkling.backend.external can't break ai.h2o.sparkling.
- 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.
24→1 ai.h2o.sparkling.backend.internal uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.internal uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.backend.internal.InternalBackendConf→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.backend.internal uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.backend.internal, while a change to ai.h2o.sparkling.backend.internal can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.internal uses a module listed above it, which is the healthy direction.
24→19 ai.h2o.sparkling.backend.internal uses ai.h2o.sparkling.backend✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.backend.internal uses a type in ai.h2o.sparkling.backend.
- The types involved
ai.h2o.sparkling.backend.internal.InternalBackendConf→ai.h2o.sparkling.backend.SharedBackendConfai.h2o.sparkling.backend.internal.InternalBackendConfExtensions→ai.h2o.sparkling.backend.SharedBackendConf
- Direction
- ai.h2o.sparkling.backend.internal uses ai.h2o.sparkling.backend, so a change to ai.h2o.sparkling.backend can break ai.h2o.sparkling.backend.internal, while a change to ai.h2o.sparkling.backend.internal can't break ai.h2o.sparkling.backend.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.internal uses a module listed above it, which is the healthy direction.
24→27 ai.h2o.sparkling.backend.internal uses ai.h2o.sparkling part of a loop✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.internal uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.backend.internal.InternalBackendConf→ai.h2o.sparkling.H2OConf
- Direction
- ai.h2o.sparkling.backend.internal uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.backend.internal, while a change to ai.h2o.sparkling.backend.internal can't break ai.h2o.sparkling.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→17 py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel uses py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel uses a type in py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel.H2ODimReductionMOJOModel→py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO.H2ODimReductionExtraParamsOnMOJO
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel uses py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO, so a change to py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO can break py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel, while a change to py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel can't break py-scoring.src.ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsOnMOJO.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel uses a module listed above it, which is the healthy direction.
25→20 py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel uses py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel uses a type in py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel.H2ODimReductionMOJOModel→py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams.H2OFeatureMOJOModelParams
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel uses py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams, so a change to py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams can break py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel, while a change to py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel can't break py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel uses a module listed above it, which is the healthy direction.
26→7 py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase uses py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase uses a type in py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase.H2OWord2VecMOJOBase→py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.HasOutputColOnMOJO
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase uses py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO, so a change to py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO can break py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase, while a change to py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase can't break py-scoring.src.ai.h2o.sparkling.ml.params.HasOutputColOnMOJO.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase uses a module listed above it, which is the healthy direction.
26→20 py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase uses py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams✕
- Connections
- 1 pair of types, where a type in py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase uses a type in py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams.
- The types involved
py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase.H2OWord2VecMOJOBase→py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams.H2OFeatureMOJOModelParams
- Direction
- py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase uses py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams, so a change to py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams can break py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase, while a change to py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase can't break py-scoring.src.ai.h2o.sparkling.ml.params.H2OMOJOModelParams.
- Position
- Below the diagonal: py-scoring.src.ai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase uses a module listed above it, which is the healthy direction.
27→1 ai.h2o.sparkling uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.H2OConf→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.H2OContext→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling, while a change to ai.h2o.sparkling can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling uses a module listed above it, which is the healthy direction.
27→2 ai.h2o.sparkling uses org.apache.spark.expose✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.H2OConf→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling, while a change to ai.h2o.sparkling can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling uses a module listed above it, which is the healthy direction.
27→10 ai.h2o.sparkling uses ai.h2o.sparkling.backend.converters✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling uses a type in ai.h2o.sparkling.backend.converters.
- The types involved
ai.h2o.sparkling.H2OContext→ai.h2o.sparkling.backend.converters.SupportedDatasetai.h2o.sparkling.H2OContext→ai.h2o.sparkling.backend.converters.SupportedRDD
- Direction
- ai.h2o.sparkling uses ai.h2o.sparkling.backend.converters, so a change to ai.h2o.sparkling.backend.converters can break ai.h2o.sparkling, while a change to ai.h2o.sparkling can't break ai.h2o.sparkling.backend.converters.
- Position
- Below the diagonal: ai.h2o.sparkling uses a module listed above it, which is the healthy direction.
27→11 ai.h2o.sparkling uses ai.h2o.sparkling.backend.utils✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.H2OContext→ai.h2o.sparkling.backend.utils.H2OContextExtensionsai.h2o.sparkling.H2OFrame→ai.h2o.sparkling.backend.utils.RestEncodingUtils
- Direction
- ai.h2o.sparkling uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling, while a change to ai.h2o.sparkling can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling uses a module listed above it, which is the healthy direction.
27→13 ai.h2o.sparkling uses org.apache.spark.h2o.ui✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling uses a type in org.apache.spark.h2o.ui.
- The types involved
ai.h2o.sparkling.H2OContext→org.apache.spark.h2o.ui.SparklingWaterHeartbeatEvent
- Direction
- ai.h2o.sparkling uses org.apache.spark.h2o.ui, so a change to org.apache.spark.h2o.ui can break ai.h2o.sparkling, while a change to ai.h2o.sparkling can't break org.apache.spark.h2o.ui.
- Position
- Below the diagonal: ai.h2o.sparkling uses a module listed above it, which is the healthy direction.
27→19 ai.h2o.sparkling uses ai.h2o.sparkling.backend✕
- Connections
- 4 pairs of types, where a type in ai.h2o.sparkling uses a type in ai.h2o.sparkling.backend.
- The types involved
ai.h2o.sparkling.DefaultSource→ai.h2o.sparkling.backend.H2OFrameRelationai.h2o.sparkling.H2OContext→ai.h2o.sparkling.backend.NodeDescai.h2o.sparkling.H2OContext→ai.h2o.sparkling.backend.SparklingBackendai.h2o.sparkling.H2OFrame→ai.h2o.sparkling.backend.H2OChunk
- Direction
- ai.h2o.sparkling uses ai.h2o.sparkling.backend, so a change to ai.h2o.sparkling.backend can break ai.h2o.sparkling, while a change to ai.h2o.sparkling can't break ai.h2o.sparkling.backend.
- Position
- Below the diagonal: ai.h2o.sparkling uses a module listed above it, which is the healthy direction.
27→23 ai.h2o.sparkling uses ai.h2o.sparkling.backend.external✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling uses a type in ai.h2o.sparkling.backend.external.
- The types involved
ai.h2o.sparkling.H2OConf→ai.h2o.sparkling.backend.external.ExternalBackendConf
- Direction
- ai.h2o.sparkling uses ai.h2o.sparkling.backend.external, so a change to ai.h2o.sparkling.backend.external can break ai.h2o.sparkling, while a change to ai.h2o.sparkling can't break ai.h2o.sparkling.backend.external.
- Position
- Below the diagonal: ai.h2o.sparkling uses a module listed above it, which is the healthy direction.
27→24 ai.h2o.sparkling uses ai.h2o.sparkling.backend.internal✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling uses a type in ai.h2o.sparkling.backend.internal.
- The types involved
ai.h2o.sparkling.H2OConf→ai.h2o.sparkling.backend.internal.InternalBackendConf
- Direction
- ai.h2o.sparkling uses ai.h2o.sparkling.backend.internal, so a change to ai.h2o.sparkling.backend.internal can break ai.h2o.sparkling, while a change to ai.h2o.sparkling can't break ai.h2o.sparkling.backend.internal.
- Position
- Below the diagonal: ai.h2o.sparkling uses a module listed above it, which is the healthy direction.
28→27 ai.h2o.sparkling.backend.api uses ai.h2o.sparkling✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.backend.api uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.backend.api.ServletRegister→ai.h2o.sparkling.H2OConfai.h2o.sparkling.backend.api.ServletRegister→ai.h2o.sparkling.H2OContext
- Direction
- ai.h2o.sparkling.backend.api uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.backend.api, while a change to ai.h2o.sparkling.backend.api can't break ai.h2o.sparkling.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api uses a module listed above it, which is the healthy direction.
29→1 ai.h2o.sparkling.ml.utils uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.utils uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.ml.utils.SchemaUtils→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.ml.utils uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.ml.utils, while a change to ai.h2o.sparkling.ml.utils can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.utils uses a module listed above it, which is the healthy direction.
29→2 ai.h2o.sparkling.ml.utils uses org.apache.spark.expose✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.ml.utils uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.ml.utils.H2OReaderBase→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.utils.Utils→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.ml.utils uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.ml.utils, while a change to ai.h2o.sparkling.ml.utils can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.utils uses a module listed above it, which is the healthy direction.
29→3 ai.h2o.sparkling.ml.utils uses org.apache.spark.ml.util.expose.DefaultParamsReader✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.ml.utils uses a type in org.apache.spark.ml.util.expose.DefaultParamsReader.
- The types involved
ai.h2o.sparkling.ml.utils.H2OParamsReader→org.apache.spark.ml.util.expose.DefaultParamsReader.Metadataai.h2o.sparkling.ml.utils.SchemaUtils→org.apache.spark.ml.util.expose.DefaultParamsReader.Metadata
- Direction
- ai.h2o.sparkling.ml.utils uses org.apache.spark.ml.util.expose.DefaultParamsReader, so a change to org.apache.spark.ml.util.expose.DefaultParamsReader can break ai.h2o.sparkling.ml.utils, while a change to ai.h2o.sparkling.ml.utils can't break org.apache.spark.ml.util.expose.DefaultParamsReader.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.utils uses a module listed above it, which is the healthy direction.
29→11 ai.h2o.sparkling.ml.utils uses ai.h2o.sparkling.backend.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.utils uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.ml.utils.EstimatorCommonUtils→ai.h2o.sparkling.backend.utils.RestCommunication
- Direction
- ai.h2o.sparkling.ml.utils uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.ml.utils, while a change to ai.h2o.sparkling.ml.utils can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.utils uses a module listed above it, which is the healthy direction.
29→27 ai.h2o.sparkling.ml.utils uses ai.h2o.sparkling✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.utils uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.ml.utils.EstimatorCommonUtils→ai.h2o.sparkling.H2OConf
- Direction
- ai.h2o.sparkling.ml.utils uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.ml.utils, while a change to ai.h2o.sparkling.ml.utils can't break ai.h2o.sparkling.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.utils uses a module listed above it, which is the healthy direction.
29→37 ai.h2o.sparkling.ml.utils uses ai.h2o.sparkling.ml.models part of a loop✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.utils uses a type in ai.h2o.sparkling.ml.models.
- The types involved
ai.h2o.sparkling.ml.utils.EstimatorCommonUtils→ai.h2o.sparkling.ml.models.H2OMOJOModel
- Direction
- ai.h2o.sparkling.ml.utils uses ai.h2o.sparkling.ml.models, so a change to ai.h2o.sparkling.ml.models can break ai.h2o.sparkling.ml.utils, while a change to ai.h2o.sparkling.ml.utils can't break ai.h2o.sparkling.ml.models.
- 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.
30→1 org.apache.spark.h2o.backends.internal uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 1 pair of types, where a type in org.apache.spark.h2o.backends.internal uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
org.apache.spark.h2o.backends.internal.InternalBackendUtils→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- org.apache.spark.h2o.backends.internal uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break org.apache.spark.h2o.backends.internal, while a change to org.apache.spark.h2o.backends.internal can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: org.apache.spark.h2o.backends.internal uses a module listed above it, which is the healthy direction.
30→2 org.apache.spark.h2o.backends.internal uses org.apache.spark.expose✕
- Connections
- 2 pairs of types, where a type in org.apache.spark.h2o.backends.internal uses a type in org.apache.spark.expose.
- The types involved
org.apache.spark.h2o.backends.internal.InternalH2OBackend→org.apache.spark.expose.Loggingorg.apache.spark.h2o.backends.internal.SpreadRDDBuilder→org.apache.spark.expose.Logging
- Direction
- org.apache.spark.h2o.backends.internal uses org.apache.spark.expose, so a change to org.apache.spark.expose can break org.apache.spark.h2o.backends.internal, while a change to org.apache.spark.h2o.backends.internal can't break org.apache.spark.expose.
- Position
- Below the diagonal: org.apache.spark.h2o.backends.internal uses a module listed above it, which is the healthy direction.
30→11 org.apache.spark.h2o.backends.internal uses ai.h2o.sparkling.backend.utils✕
- Connections
- 2 pairs of types, where a type in org.apache.spark.h2o.backends.internal uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
org.apache.spark.h2o.backends.internal.InternalBackendUtils→ai.h2o.sparkling.backend.utils.SharedBackendUtilsorg.apache.spark.h2o.backends.internal.RpcReferenceCache→ai.h2o.sparkling.backend.utils.SharedBackendUtils
- Direction
- org.apache.spark.h2o.backends.internal uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break org.apache.spark.h2o.backends.internal, while a change to org.apache.spark.h2o.backends.internal can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: org.apache.spark.h2o.backends.internal uses a module listed above it, which is the healthy direction.
30→19 org.apache.spark.h2o.backends.internal uses ai.h2o.sparkling.backend✕
- Connections
- 2 pairs of types, where a type in org.apache.spark.h2o.backends.internal uses a type in ai.h2o.sparkling.backend.
- The types involved
org.apache.spark.h2o.backends.internal.FlatFileMsg→ai.h2o.sparkling.backend.NodeDescorg.apache.spark.h2o.backends.internal.InternalH2OBackend→ai.h2o.sparkling.backend.SparklingBackend
- Direction
- org.apache.spark.h2o.backends.internal uses ai.h2o.sparkling.backend, so a change to ai.h2o.sparkling.backend can break org.apache.spark.h2o.backends.internal, while a change to org.apache.spark.h2o.backends.internal can't break ai.h2o.sparkling.backend.
- Position
- Below the diagonal: org.apache.spark.h2o.backends.internal uses a module listed above it, which is the healthy direction.
30→27 org.apache.spark.h2o.backends.internal uses ai.h2o.sparkling✕
- Connections
- 5 pairs of types, where a type in org.apache.spark.h2o.backends.internal uses a type in ai.h2o.sparkling.
- The types involved
org.apache.spark.h2o.backends.internal.InternalBackendUtils→ai.h2o.sparkling.H2OConforg.apache.spark.h2o.backends.internal.InternalH2OBackend→ai.h2o.sparkling.H2OConforg.apache.spark.h2o.backends.internal.InternalH2OBackend→ai.h2o.sparkling.H2OContextorg.apache.spark.h2o.backends.internal.SpreadRDDBuilder→ai.h2o.sparkling.H2OContextorg.apache.spark.h2o.backends.internal.StartH2OWorkersMsg→ai.h2o.sparkling.H2OConf
- Direction
- org.apache.spark.h2o.backends.internal uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break org.apache.spark.h2o.backends.internal, while a change to org.apache.spark.h2o.backends.internal can't break ai.h2o.sparkling.
- Position
- Below the diagonal: org.apache.spark.h2o.backends.internal uses a module listed above it, which is the healthy direction.
31→1 ai.h2o.sparkling.backend.api.dataframes uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.dataframes uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.backend.api.dataframes.DataFramesServlet→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.backend.api.dataframes uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.backend.api.dataframes, while a change to ai.h2o.sparkling.backend.api.dataframes can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.dataframes uses a module listed above it, which is the healthy direction.
31→11 ai.h2o.sparkling.backend.api.dataframes uses ai.h2o.sparkling.backend.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.dataframes uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.backend.api.dataframes.DataFramesRestApi→ai.h2o.sparkling.backend.utils.RestApiUtils
- Direction
- ai.h2o.sparkling.backend.api.dataframes uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.backend.api.dataframes, while a change to ai.h2o.sparkling.backend.api.dataframes can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.dataframes uses a module listed above it, which is the healthy direction.
31→28 ai.h2o.sparkling.backend.api.dataframes uses ai.h2o.sparkling.backend.api✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.dataframes uses a type in ai.h2o.sparkling.backend.api.
- The types involved
ai.h2o.sparkling.backend.api.dataframes.DataFramesServlet→ai.h2o.sparkling.backend.api.ServletBase
- Direction
- ai.h2o.sparkling.backend.api.dataframes uses ai.h2o.sparkling.backend.api, so a change to ai.h2o.sparkling.backend.api can break ai.h2o.sparkling.backend.api.dataframes, while a change to ai.h2o.sparkling.backend.api.dataframes can't break ai.h2o.sparkling.backend.api.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.dataframes uses a module listed above it, which is the healthy direction.
32→1 ai.h2o.sparkling.backend.api.h2oframes uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.h2oframes uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.backend.api.h2oframes.H2OFramesServlet→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.backend.api.h2oframes uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.backend.api.h2oframes, while a change to ai.h2o.sparkling.backend.api.h2oframes can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.h2oframes uses a module listed above it, which is the healthy direction.
32→11 ai.h2o.sparkling.backend.api.h2oframes uses ai.h2o.sparkling.backend.utils✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.backend.api.h2oframes uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.backend.api.h2oframes.H2OFramesRestApi→ai.h2o.sparkling.backend.utils.RestApiUtilsai.h2o.sparkling.backend.api.h2oframes.H2OFramesRestApi→ai.h2o.sparkling.backend.utils.RestEncodingUtils
- Direction
- ai.h2o.sparkling.backend.api.h2oframes uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.backend.api.h2oframes, while a change to ai.h2o.sparkling.backend.api.h2oframes can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.h2oframes uses a module listed above it, which is the healthy direction.
32→28 ai.h2o.sparkling.backend.api.h2oframes uses ai.h2o.sparkling.backend.api✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.h2oframes uses a type in ai.h2o.sparkling.backend.api.
- The types involved
ai.h2o.sparkling.backend.api.h2oframes.H2OFramesServlet→ai.h2o.sparkling.backend.api.ServletBase
- Direction
- ai.h2o.sparkling.backend.api.h2oframes uses ai.h2o.sparkling.backend.api, so a change to ai.h2o.sparkling.backend.api can break ai.h2o.sparkling.backend.api.h2oframes, while a change to ai.h2o.sparkling.backend.api.h2oframes can't break ai.h2o.sparkling.backend.api.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.h2oframes uses a module listed above it, which is the healthy direction.
33→1 ai.h2o.sparkling.backend.api.rdds uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.rdds uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.backend.api.rdds.RDDsServlet→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.backend.api.rdds uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.backend.api.rdds, while a change to ai.h2o.sparkling.backend.api.rdds can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.rdds uses a module listed above it, which is the healthy direction.
33→11 ai.h2o.sparkling.backend.api.rdds uses ai.h2o.sparkling.backend.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.rdds uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.backend.api.rdds.RDDsRestApi→ai.h2o.sparkling.backend.utils.RestApiUtils
- Direction
- ai.h2o.sparkling.backend.api.rdds uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.backend.api.rdds, while a change to ai.h2o.sparkling.backend.api.rdds can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.rdds uses a module listed above it, which is the healthy direction.
33→27 ai.h2o.sparkling.backend.api.rdds uses ai.h2o.sparkling✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.rdds uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.backend.api.rdds.RDDsServlet→ai.h2o.sparkling.H2OFrame
- Direction
- ai.h2o.sparkling.backend.api.rdds uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.backend.api.rdds, while a change to ai.h2o.sparkling.backend.api.rdds can't break ai.h2o.sparkling.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.rdds uses a module listed above it, which is the healthy direction.
33→28 ai.h2o.sparkling.backend.api.rdds uses ai.h2o.sparkling.backend.api✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.rdds uses a type in ai.h2o.sparkling.backend.api.
- The types involved
ai.h2o.sparkling.backend.api.rdds.RDDsServlet→ai.h2o.sparkling.backend.api.ServletBase
- Direction
- ai.h2o.sparkling.backend.api.rdds uses ai.h2o.sparkling.backend.api, so a change to ai.h2o.sparkling.backend.api can break ai.h2o.sparkling.backend.api.rdds, while a change to ai.h2o.sparkling.backend.api.rdds can't break ai.h2o.sparkling.backend.api.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.rdds uses a module listed above it, which is the healthy direction.
34→11 ai.h2o.sparkling.backend.api.scalainterpreter uses ai.h2o.sparkling.backend.utils✕
- Connections
- 3 pairs of types, where a type in ai.h2o.sparkling.backend.api.scalainterpreter uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.backend.api.scalainterpreter.ScalaInterpretJob→ai.h2o.sparkling.backend.utils.RestCommunicationai.h2o.sparkling.backend.api.scalainterpreter.ScalaInterpreterRestApi→ai.h2o.sparkling.backend.utils.RestApiUtilsai.h2o.sparkling.backend.api.scalainterpreter.ScalaInterpreterServlet→ai.h2o.sparkling.backend.utils.RestCommunication
- Direction
- ai.h2o.sparkling.backend.api.scalainterpreter uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.backend.api.scalainterpreter, while a change to ai.h2o.sparkling.backend.api.scalainterpreter can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.scalainterpreter uses a module listed above it, which is the healthy direction.
34→12 ai.h2o.sparkling.backend.api.scalainterpreter uses ai.h2o.sparkling.repl✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.backend.api.scalainterpreter uses a type in ai.h2o.sparkling.repl.
- The types involved
ai.h2o.sparkling.backend.api.scalainterpreter.ScalaInterpretJob→ai.h2o.sparkling.repl.H2OInterpreterai.h2o.sparkling.backend.api.scalainterpreter.ScalaInterpreterServlet→ai.h2o.sparkling.repl.H2OInterpreter
- Direction
- ai.h2o.sparkling.backend.api.scalainterpreter uses ai.h2o.sparkling.repl, so a change to ai.h2o.sparkling.repl can break ai.h2o.sparkling.backend.api.scalainterpreter, while a change to ai.h2o.sparkling.backend.api.scalainterpreter can't break ai.h2o.sparkling.repl.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.scalainterpreter uses a module listed above it, which is the healthy direction.
34→28 ai.h2o.sparkling.backend.api.scalainterpreter uses ai.h2o.sparkling.backend.api✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.backend.api.scalainterpreter uses a type in ai.h2o.sparkling.backend.api.
- The types involved
ai.h2o.sparkling.backend.api.scalainterpreter.ScalaInterpreterServlet→ai.h2o.sparkling.backend.api.ServletBase
- Direction
- ai.h2o.sparkling.backend.api.scalainterpreter uses ai.h2o.sparkling.backend.api, so a change to ai.h2o.sparkling.backend.api can break ai.h2o.sparkling.backend.api.scalainterpreter, while a change to ai.h2o.sparkling.backend.api.scalainterpreter can't break ai.h2o.sparkling.backend.api.
- Position
- Below the diagonal: ai.h2o.sparkling.backend.api.scalainterpreter uses a module listed above it, which is the healthy direction.
35→2 ai.h2o.sparkling.ml.params uses org.apache.spark.expose✕
- Connections
- 11 pairs of types, where a type in ai.h2o.sparkling.ml.params uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.ml.params.DeprecatableParams→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.H2OAlgorithmMOJOParams→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.HasBlendingDataFrame→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.HasGamColsOnMOJO→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.HasIgnoredColsOnMOJO→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.HasInputColOnMOJO→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.HasInputColsOnMOJO→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.HasInteractionPairs→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.HasLeaderboardDataFrame→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.HasMonotoneConstraintsOnMOJO→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.params.NonSerializableNullableDataFrameParam→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.ml.params uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.ml.params, while a change to ai.h2o.sparkling.ml.params can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.params uses a module listed above it, which is the healthy direction.
35→11 ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.backend.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.params uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.ml.params.H2OAlgoParamsBase→ai.h2o.sparkling.backend.utils.H2OFrameLifecycle
- Direction
- ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.ml.params, while a change to ai.h2o.sparkling.ml.params can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.params uses a module listed above it, which is the healthy direction.
35→27 ai.h2o.sparkling.ml.params uses ai.h2o.sparkling✕
- Connections
- 22 pairs of types, where a type in ai.h2o.sparkling.ml.params uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.ml.params.H2OAlgoParamsBase→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasBaseAlgorithms→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasBetaConstraints→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasBlendingDataFrame→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasCalibrationDataFrame→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasGamCols→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasIgnoredCols→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasInitialBiases→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasInitialWeights→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasInteractionPairs→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasLeaderboardDataFrame→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasLinearConstraints→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasLossByColNames→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasMonotoneConstraints→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasPlugValues→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasPreTrained→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasRandomCols→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasUnsupportedOffsetCol→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasUserPoints→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasUserX→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasUserY→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.params.HasValidationLabelCol→ai.h2o.sparkling.H2OFrame
- Direction
- ai.h2o.sparkling.ml.params uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.ml.params, while a change to ai.h2o.sparkling.ml.params can't break ai.h2o.sparkling.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.params uses a module listed above it, which is the healthy direction.
35→29 ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.ml.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.params uses a type in ai.h2o.sparkling.ml.utils.
- The types involved
ai.h2o.sparkling.ml.params.NullableMetricsParam→ai.h2o.sparkling.ml.utils.H2OParamsReader
- Direction
- ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.ml.utils, so a change to ai.h2o.sparkling.ml.utils can break ai.h2o.sparkling.ml.params, while a change to ai.h2o.sparkling.ml.params can't break ai.h2o.sparkling.ml.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.params uses a module listed above it, which is the healthy direction.
35→36 ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.ml.metrics part of a loop✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.params uses a type in ai.h2o.sparkling.ml.metrics.
- The types involved
ai.h2o.sparkling.ml.params.NullableMetricsParam→ai.h2o.sparkling.ml.metrics.H2OMetrics
- Direction
- ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.ml.metrics, so a change to ai.h2o.sparkling.ml.metrics can break ai.h2o.sparkling.ml.params, while a change to ai.h2o.sparkling.ml.params can't break ai.h2o.sparkling.ml.metrics.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→37 ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.ml.models part of a loop✕
- Connections
- 8 pairs of types, where a type in ai.h2o.sparkling.ml.params uses a type in ai.h2o.sparkling.ml.models.
- The types involved
ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParams→ai.h2o.sparkling.ml.models.H2OFeatureEstimatorBaseai.h2o.sparkling.ml.params.H2ODimReductionExtraParams→ai.h2o.sparkling.ml.models.H2OFeatureEstimatorBaseai.h2o.sparkling.ml.params.H2OWord2VecExtraParams→ai.h2o.sparkling.ml.models.H2OFeatureEstimatorBaseai.h2o.sparkling.ml.params.HasGamColsOnMOJO→ai.h2o.sparkling.ml.models.SpecificMOJOParametersai.h2o.sparkling.ml.params.HasIgnoredColsOnMOJO→ai.h2o.sparkling.ml.models.SpecificMOJOParametersai.h2o.sparkling.ml.params.HasInputColOnMOJO→ai.h2o.sparkling.ml.models.SpecificMOJOParametersai.h2o.sparkling.ml.params.HasInputColsOnMOJO→ai.h2o.sparkling.ml.models.SpecificMOJOParametersai.h2o.sparkling.ml.params.HasMonotoneConstraintsOnMOJO→ai.h2o.sparkling.ml.models.SpecificMOJOParameters
- Direction
- ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.ml.models, so a change to ai.h2o.sparkling.ml.models can break ai.h2o.sparkling.ml.params, while a change to ai.h2o.sparkling.ml.params can't break ai.h2o.sparkling.ml.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→38 ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.ml.algos part of a loop✕
- Connections
- 7 pairs of types, where a type in ai.h2o.sparkling.ml.params uses a type in ai.h2o.sparkling.ml.algos.
- The types involved
ai.h2o.sparkling.ml.params.AlgoParam→ai.h2o.sparkling.ml.algos.H2OAlgorithmai.h2o.sparkling.ml.params.H2OGridSearchParams→ai.h2o.sparkling.ml.algos.H2OAlgorithmai.h2o.sparkling.ml.params.HasBaseAlgorithms→ai.h2o.sparkling.ml.algos.H2OAlgorithmai.h2o.sparkling.ml.params.HasGamCols→ai.h2o.sparkling.ml.algos.H2OAlgoCommonUtilsai.h2o.sparkling.ml.params.HasRandomCols→ai.h2o.sparkling.ml.algos.H2OAlgoCommonUtilsai.h2o.sparkling.ml.params.HasValidationLabelCol→ai.h2o.sparkling.ml.algos.H2OAlgoCommonUtilsai.h2o.sparkling.ml.params.NullableAlgoArrayParam→ai.h2o.sparkling.ml.algos.H2OAlgorithm
- Direction
- ai.h2o.sparkling.ml.params uses ai.h2o.sparkling.ml.algos, so a change to ai.h2o.sparkling.ml.algos can break ai.h2o.sparkling.ml.params, while a change to ai.h2o.sparkling.ml.params can't break ai.h2o.sparkling.ml.algos.
- 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.
36→2 ai.h2o.sparkling.ml.metrics uses org.apache.spark.expose✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.metrics uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.ml.metrics.H2OMetrics→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.ml.metrics uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.ml.metrics, while a change to ai.h2o.sparkling.ml.metrics can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.metrics uses a module listed above it, which is the healthy direction.
36→35 ai.h2o.sparkling.ml.metrics uses ai.h2o.sparkling.ml.params✕
- Connections
- 3 pairs of types, where a type in ai.h2o.sparkling.ml.metrics uses a type in ai.h2o.sparkling.ml.params.
- The types involved
ai.h2o.sparkling.ml.metrics.H2OMetrics→ai.h2o.sparkling.ml.params.HasDataFrameSerializerai.h2o.sparkling.ml.metrics.H2OMetrics→ai.h2o.sparkling.ml.params.NullableDataFrameParamai.h2o.sparkling.ml.metrics.H2OMetrics→ai.h2o.sparkling.ml.params.ParameterConstructorMethods
- Direction
- ai.h2o.sparkling.ml.metrics uses ai.h2o.sparkling.ml.params, so a change to ai.h2o.sparkling.ml.params can break ai.h2o.sparkling.ml.metrics, while a change to ai.h2o.sparkling.ml.metrics can't break ai.h2o.sparkling.ml.params.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.metrics uses a module listed above it, which is the healthy direction.
36→37 ai.h2o.sparkling.ml.metrics uses ai.h2o.sparkling.ml.models part of a loop✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.metrics uses a type in ai.h2o.sparkling.ml.models.
- The types involved
ai.h2o.sparkling.ml.metrics.H2OMetrics→ai.h2o.sparkling.ml.models.H2OMOJOModelUtils
- Direction
- ai.h2o.sparkling.ml.metrics uses ai.h2o.sparkling.ml.models, so a change to ai.h2o.sparkling.ml.models can break ai.h2o.sparkling.ml.metrics, while a change to ai.h2o.sparkling.ml.metrics can't break ai.h2o.sparkling.ml.models.
- 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→1 ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.ml.models uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.ml.models.H2OMOJOModelUtils→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.ml.models.HasBinaryModel→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.ml.models, while a change to ai.h2o.sparkling.ml.models can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.models uses a module listed above it, which is the healthy direction.
37→2 ai.h2o.sparkling.ml.models uses org.apache.spark.expose✕
- Connections
- 5 pairs of types, where a type in ai.h2o.sparkling.ml.models uses a type in org.apache.spark.expose.
- The types involved
ai.h2o.sparkling.ml.models.H2OBinaryModel→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.models.H2OFeatureMOJOModel→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.models.H2OMOJOBaseCache→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.models.H2OMOJOModel→org.apache.spark.expose.Loggingai.h2o.sparkling.ml.models.H2OMOJOModelUtils→org.apache.spark.expose.Logging
- Direction
- ai.h2o.sparkling.ml.models uses org.apache.spark.expose, so a change to org.apache.spark.expose can break ai.h2o.sparkling.ml.models, while a change to ai.h2o.sparkling.ml.models can't break org.apache.spark.expose.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.models uses a module listed above it, which is the healthy direction.
37→11 ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.backend.utils✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.ml.models uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.ml.models.H2OBinaryModel→ai.h2o.sparkling.backend.utils.RestCommunicationai.h2o.sparkling.ml.models.H2OTargetEncoderModel→ai.h2o.sparkling.backend.utils.RestCommunication
- Direction
- ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.ml.models, while a change to ai.h2o.sparkling.ml.models can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.models uses a module listed above it, which is the healthy direction.
37→29 ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.ml.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.models uses a type in ai.h2o.sparkling.ml.utils.
- The types involved
ai.h2o.sparkling.ml.models.H2OMOJOReader→ai.h2o.sparkling.ml.utils.H2OReaderBase
- Direction
- ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.ml.utils, so a change to ai.h2o.sparkling.ml.utils can break ai.h2o.sparkling.ml.models, while a change to ai.h2o.sparkling.ml.models can't break ai.h2o.sparkling.ml.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.models uses a module listed above it, which is the healthy direction.
37→35 ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.ml.params✕
- Connections
- 22 pairs of types, where a type in ai.h2o.sparkling.ml.models uses a type in ai.h2o.sparkling.ml.params.
- The types involved
ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModel→ai.h2o.sparkling.ml.params.H2OAlgorithmMOJOParamsai.h2o.sparkling.ml.models.H2OAutoEncoderMOJOBase→ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsai.h2o.sparkling.ml.models.H2ODimReductionMOJOModel→ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsai.h2o.sparkling.ml.models.H2OGLRMMOJOBase→ai.h2o.sparkling.ml.params.H2OGLRMExtraParamsai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.params.DoubleParamai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.params.H2OBaseMOJOParamsai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.params.HasFeatureTypesOnMOJOai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.params.MapStringDoubleParamai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.params.MapStringStringParamai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.params.NullableDataFrameParamai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.params.NullableMetricsParamai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.params.NullableStringParamai.h2o.sparkling.ml.models.H2OMOJOPipelineModel→ai.h2o.sparkling.ml.params.H2OAlgorithmMOJOParamsai.h2o.sparkling.ml.models.H2OMOJOPipelineModel→ai.h2o.sparkling.ml.params.H2OBaseMOJOParamsai.h2o.sparkling.ml.models.H2OMOJOPipelineModel→ai.h2o.sparkling.ml.params.HasFeatureTypesOnMOJOai.h2o.sparkling.ml.models.H2OMOJOPipelineModel→ai.h2o.sparkling.ml.params.ParameterConstructorMethodsai.h2o.sparkling.ml.models.H2OSupervisedMOJOModel→ai.h2o.sparkling.ml.params.H2OSupervisedMOJOParamsai.h2o.sparkling.ml.models.H2OTargetEncoderBase→ai.h2o.sparkling.ml.params.H2OTargetEncoderMOJOParamsai.h2o.sparkling.ml.models.H2OTreeBasedSupervisedMOJOModel→ai.h2o.sparkling.ml.params.H2OSupervisedMOJOParamsai.h2o.sparkling.ml.models.H2OTreeBasedSupervisedMOJOModel→ai.h2o.sparkling.ml.params.H2OTreeBasedMOJOParamsai.h2o.sparkling.ml.models.H2OTreeBasedUnsupervisedMOJOModel→ai.h2o.sparkling.ml.params.H2OTreeBasedMOJOParamsai.h2o.sparkling.ml.models.H2OWord2VecMOJOBase→ai.h2o.sparkling.ml.params.H2OWord2VecExtraParams
- Direction
- ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.ml.params, so a change to ai.h2o.sparkling.ml.params can break ai.h2o.sparkling.ml.models, while a change to ai.h2o.sparkling.ml.models can't break ai.h2o.sparkling.ml.params.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.models uses a module listed above it, which is the healthy direction.
37→36 ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.ml.metrics✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.ml.models uses a type in ai.h2o.sparkling.ml.metrics.
- The types involved
ai.h2o.sparkling.ml.models.H2OMOJOModel→ai.h2o.sparkling.ml.metrics.H2OMetricsai.h2o.sparkling.ml.models.H2OMOJOModelUtils→ai.h2o.sparkling.ml.metrics.H2OMetrics
- Direction
- ai.h2o.sparkling.ml.models uses ai.h2o.sparkling.ml.metrics, so a change to ai.h2o.sparkling.ml.metrics can break ai.h2o.sparkling.ml.models, while a change to ai.h2o.sparkling.ml.models can't break ai.h2o.sparkling.ml.metrics.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.models uses a module listed above it, which is the healthy direction.
38→1 ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 4 pairs of types, where a type in ai.h2o.sparkling.ml.algos uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.ml.algos.H2OAlgoCommonUtils→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.ml.algos.H2OAutoML→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.ml.algos.H2OEstimator→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Optionai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.ml.algos, while a change to ai.h2o.sparkling.ml.algos can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.algos uses a module listed above it, which is the healthy direction.
38→11 ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.backend.utils✕
- Connections
- 5 pairs of types, where a type in ai.h2o.sparkling.ml.algos uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.ml.algos.H2OAlgoCommonUtils→ai.h2o.sparkling.backend.utils.H2OFrameLifecycleai.h2o.sparkling.ml.algos.H2OAutoML→ai.h2o.sparkling.backend.utils.RestCommunicationai.h2o.sparkling.ml.algos.H2OEstimator→ai.h2o.sparkling.backend.utils.RestCommunicationai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.backend.utils.RestCommunicationai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.backend.utils.RestEncodingUtils
- Direction
- ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.ml.algos, while a change to ai.h2o.sparkling.ml.algos can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.algos uses a module listed above it, which is the healthy direction.
38→27 ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling✕
- Connections
- 8 pairs of types, where a type in ai.h2o.sparkling.ml.algos uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.ml.algos.DistributionBasedH2OTrainFramePreparation→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.algos.FamilyBasedH2OTrainFramePreparation→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.algos.H2OAutoML→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.algos.H2OEstimator→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.H2OConfai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.algos.H2OKMeansExtras→ai.h2o.sparkling.H2OFrameai.h2o.sparkling.ml.algos.H2OTrainFramePreparation→ai.h2o.sparkling.H2OFrame
- Direction
- ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.ml.algos, while a change to ai.h2o.sparkling.ml.algos can't break ai.h2o.sparkling.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.algos uses a module listed above it, which is the healthy direction.
38→29 ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.ml.utils✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.ml.algos uses a type in ai.h2o.sparkling.ml.utils.
- The types involved
ai.h2o.sparkling.ml.algos.H2OAlgoCommonUtils→ai.h2o.sparkling.ml.utils.EstimatorCommonUtilsai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.ml.utils.EstimatorCommonUtils
- Direction
- ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.ml.utils, so a change to ai.h2o.sparkling.ml.utils can break ai.h2o.sparkling.ml.algos, while a change to ai.h2o.sparkling.ml.algos can't break ai.h2o.sparkling.ml.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.algos uses a module listed above it, which is the healthy direction.
38→35 ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.ml.params✕
- Connections
- 5 pairs of types, where a type in ai.h2o.sparkling.ml.algos uses a type in ai.h2o.sparkling.ml.params.
- The types involved
ai.h2o.sparkling.ml.algos.H2OAlgorithm→ai.h2o.sparkling.ml.params.H2OAlgorithmCommonParamsai.h2o.sparkling.ml.algos.H2OAutoML→ai.h2o.sparkling.ml.params.H2OAutoMLParamsai.h2o.sparkling.ml.algos.H2OEstimator→ai.h2o.sparkling.ml.params.H2OAlgoParamsBaseai.h2o.sparkling.ml.algos.H2OEstimator→ai.h2o.sparkling.ml.params.H2OCommonParamsai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.ml.params.H2OGridSearchParams
- Direction
- ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.ml.params, so a change to ai.h2o.sparkling.ml.params can break ai.h2o.sparkling.ml.algos, while a change to ai.h2o.sparkling.ml.algos can't break ai.h2o.sparkling.ml.params.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.algos uses a module listed above it, which is the healthy direction.
38→37 ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.ml.models✕
- Connections
- 13 pairs of types, where a type in ai.h2o.sparkling.ml.algos uses a type in ai.h2o.sparkling.ml.models.
- The types involved
ai.h2o.sparkling.ml.algos.H2OAlgoCommonUtils→ai.h2o.sparkling.ml.models.H2OBinaryModelai.h2o.sparkling.ml.algos.H2OAlgorithm→ai.h2o.sparkling.ml.models.H2OAlgorithmMOJOModelai.h2o.sparkling.ml.algos.H2OAlgorithm→ai.h2o.sparkling.ml.models.H2OMOJOSettingsai.h2o.sparkling.ml.algos.H2OAutoML→ai.h2o.sparkling.ml.models.H2OMOJOModelai.h2o.sparkling.ml.algos.H2OEstimator→ai.h2o.sparkling.ml.models.H2OMOJOModelai.h2o.sparkling.ml.algos.H2OEstimator→ai.h2o.sparkling.ml.models.H2OMOJOSettingsai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.ml.models.H2OBinaryModelai.h2o.sparkling.ml.algos.H2OGridSearch→ai.h2o.sparkling.ml.models.H2OMOJOModelai.h2o.sparkling.ml.algos.H2OStackedEnsemble→ai.h2o.sparkling.ml.models.H2OMOJOModelai.h2o.sparkling.ml.algos.H2OSupervisedAlgorithm→ai.h2o.sparkling.ml.models.H2OSupervisedMOJOModelai.h2o.sparkling.ml.algos.H2OTreeBasedSupervisedAlgorithm→ai.h2o.sparkling.ml.models.H2OTreeBasedSupervisedMOJOModelai.h2o.sparkling.ml.algos.H2OTreeBasedUnsupervisedAlgorithm→ai.h2o.sparkling.ml.models.H2OTreeBasedUnsupervisedMOJOModelai.h2o.sparkling.ml.algos.H2OUnsupervisedAlgorithm→ai.h2o.sparkling.ml.models.H2OUnsupervisedMOJOModel
- Direction
- ai.h2o.sparkling.ml.algos uses ai.h2o.sparkling.ml.models, so a change to ai.h2o.sparkling.ml.models can break ai.h2o.sparkling.ml.algos, while a change to ai.h2o.sparkling.ml.algos can't break ai.h2o.sparkling.ml.models.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.algos uses a module listed above it, which is the healthy direction.
39→1 ai.h2o.sparkling.ml.internals uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.internals uses a type in ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- The types involved
ai.h2o.sparkling.ml.internals.H2OModel→ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.Option
- Direction
- ai.h2o.sparkling.ml.internals uses ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate, so a change to ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate can break ai.h2o.sparkling.ml.internals, while a change to ai.h2o.sparkling.ml.internals can't break ai.h2o.sparkling.booklet.generation.ConfigurationsTemplate.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.internals uses a module listed above it, which is the healthy direction.
39→11 ai.h2o.sparkling.ml.internals uses ai.h2o.sparkling.backend.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.internals uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.ml.internals.H2OModel→ai.h2o.sparkling.backend.utils.RestCommunication
- Direction
- ai.h2o.sparkling.ml.internals uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.ml.internals, while a change to ai.h2o.sparkling.ml.internals can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.internals uses a module listed above it, which is the healthy direction.
39→37 ai.h2o.sparkling.ml.internals uses ai.h2o.sparkling.ml.models✕
- Connections
- 2 pairs of types, where a type in ai.h2o.sparkling.ml.internals uses a type in ai.h2o.sparkling.ml.models.
- The types involved
ai.h2o.sparkling.ml.internals.H2OModel→ai.h2o.sparkling.ml.models.H2OMOJOModelai.h2o.sparkling.ml.internals.H2OModel→ai.h2o.sparkling.ml.models.H2OMOJOSettings
- Direction
- ai.h2o.sparkling.ml.internals uses ai.h2o.sparkling.ml.models, so a change to ai.h2o.sparkling.ml.models can break ai.h2o.sparkling.ml.internals, while a change to ai.h2o.sparkling.ml.internals can't break ai.h2o.sparkling.ml.models.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.internals uses a module listed above it, which is the healthy direction.
40→11 ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.backend.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.features uses a type in ai.h2o.sparkling.backend.utils.
- The types involved
ai.h2o.sparkling.ml.features.H2OTargetEncoder→ai.h2o.sparkling.backend.utils.RestCommunication
- Direction
- ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.backend.utils, so a change to ai.h2o.sparkling.backend.utils can break ai.h2o.sparkling.ml.features, while a change to ai.h2o.sparkling.ml.features can't break ai.h2o.sparkling.backend.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.features uses a module listed above it, which is the healthy direction.
40→27 ai.h2o.sparkling.ml.features uses ai.h2o.sparkling✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.features uses a type in ai.h2o.sparkling.
- The types involved
ai.h2o.sparkling.ml.features.H2OAutoEncoderBase→ai.h2o.sparkling.H2OFrame
- Direction
- ai.h2o.sparkling.ml.features uses ai.h2o.sparkling, so a change to ai.h2o.sparkling can break ai.h2o.sparkling.ml.features, while a change to ai.h2o.sparkling.ml.features can't break ai.h2o.sparkling.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.features uses a module listed above it, which is the healthy direction.
40→29 ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.ml.utils✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.features uses a type in ai.h2o.sparkling.ml.utils.
- The types involved
ai.h2o.sparkling.ml.features.H2OTargetEncoder→ai.h2o.sparkling.ml.utils.EstimatorCommonUtils
- Direction
- ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.ml.utils, so a change to ai.h2o.sparkling.ml.utils can break ai.h2o.sparkling.ml.features, while a change to ai.h2o.sparkling.ml.features can't break ai.h2o.sparkling.ml.utils.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.features uses a module listed above it, which is the healthy direction.
40→35 ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.ml.params✕
- Connections
- 8 pairs of types, where a type in ai.h2o.sparkling.ml.features uses a type in ai.h2o.sparkling.ml.params.
- The types involved
ai.h2o.sparkling.ml.features.ColumnPruner→ai.h2o.sparkling.ml.params.ColumnPrunerParamsai.h2o.sparkling.ml.features.H2OAutoEncoderBase→ai.h2o.sparkling.ml.params.H2OAutoEncoderExtraParamsai.h2o.sparkling.ml.features.H2OAutoEncoderBase→ai.h2o.sparkling.ml.params.HasInputColsai.h2o.sparkling.ml.features.H2ODimReductionEstimator→ai.h2o.sparkling.ml.params.H2ODimReductionExtraParamsai.h2o.sparkling.ml.features.H2ODimReductionEstimator→ai.h2o.sparkling.ml.params.HasInputColsai.h2o.sparkling.ml.features.H2OGLRMBase→ai.h2o.sparkling.ml.params.H2OGLRMExtraParamsai.h2o.sparkling.ml.features.H2OGLRMBase→ai.h2o.sparkling.ml.params.HasInputColsai.h2o.sparkling.ml.features.H2OWord2VecBase→ai.h2o.sparkling.ml.params.H2OWord2VecExtraParams
- Direction
- ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.ml.params, so a change to ai.h2o.sparkling.ml.params can break ai.h2o.sparkling.ml.features, while a change to ai.h2o.sparkling.ml.features can't break ai.h2o.sparkling.ml.params.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.features uses a module listed above it, which is the healthy direction.
40→37 ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.ml.models✕
- Connections
- 5 pairs of types, where a type in ai.h2o.sparkling.ml.features uses a type in ai.h2o.sparkling.ml.models.
- The types involved
ai.h2o.sparkling.ml.features.H2ODimReductionEstimator→ai.h2o.sparkling.ml.models.H2ODimReductionMOJOModelai.h2o.sparkling.ml.features.H2OFeatureEstimator→ai.h2o.sparkling.ml.models.H2OFeatureEstimatorBaseai.h2o.sparkling.ml.features.H2OFeatureEstimator→ai.h2o.sparkling.ml.models.H2OFeatureMOJOModelai.h2o.sparkling.ml.features.H2OTargetEncoder→ai.h2o.sparkling.ml.models.H2OTargetEncoderBaseai.h2o.sparkling.ml.features.H2OTargetEncoder→ai.h2o.sparkling.ml.models.H2OTargetEncoderModel
- Direction
- ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.ml.models, so a change to ai.h2o.sparkling.ml.models can break ai.h2o.sparkling.ml.features, while a change to ai.h2o.sparkling.ml.features can't break ai.h2o.sparkling.ml.models.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.features uses a module listed above it, which is the healthy direction.
40→38 ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.ml.algos✕
- Connections
- 1 pair of types, where a type in ai.h2o.sparkling.ml.features uses a type in ai.h2o.sparkling.ml.algos.
- The types involved
ai.h2o.sparkling.ml.features.H2OFeatureEstimator→ai.h2o.sparkling.ml.algos.H2OEstimator
- Direction
- ai.h2o.sparkling.ml.features uses ai.h2o.sparkling.ml.algos, so a change to ai.h2o.sparkling.ml.algos can break ai.h2o.sparkling.ml.features, while a change to ai.h2o.sparkling.ml.features can't break ai.h2o.sparkling.ml.algos.
- Position
- Below the diagonal: ai.h2o.sparkling.ml.features uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 73 | High / Critical |
| A05:2025 — Injection | 6 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Begin by resolving the single documentation quality issue in README.rst and adding a quick-start build section to the root README to improve newcomer onboarding. Next, address the complete absence of Architecture Decision Records by creating a docs/adr folder and documenting significant design decisions with their context and consequences. Finally, tackle the 192 orphaned files in Knowledge Freshness, prioritizing cleanup of build.gradle, __init__.py, and H2OFrame.scala to maintain codebase hygiene.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.rst. | +7.3 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +7.3 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.2 pts | Medium | Architecture documentation |
| Resolve the 192 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (10), __init__.py (4), H2OFrame.scala (2). | +7.3 pts | High | Knowledge Freshness |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +3.5 pts | Medium | Documentation (README) |
| Run what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +1.9 pts | Medium | Security & performance tooling |
| Improve Test Distribution — currently 8.8/10. | +1.3 pts | Medium | Test Distribution |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +0.5 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 0.0 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.6 | Mixed | IaC & Container Security: Critical IaC: REDACTED |
| py/tests/integration/external_only/test_security.py | 7.0 | Mixed | Test Reliability: Test declared unreliable: testPamAuthWithCorrectCredentials |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| core/src/main/scala/ai/h2o/sparkling/backend/external/ExternalH2OBackend.scala | 7.8 | Mixed | Cyclomatic Complexity: ExternalH2OBackend.checkAndUpdateConf (cyclomatic 27) |
| scoring/src/main/scala/ai/h2o/sparkling/ml/models/H2OMOJOPipelineModel.scala | 7.8 | Mixed | Cyclomatic Complexity: H2OMOJOPipelineModel.rowsToMojoFrame (cyclomatic 18) |
| core/src/main/scala/ai/h2o/sparkling/backend/utils/SharedBackendUtils.scala | 7.8 | Mixed | Cyclomatic Complexity: SharedBackendUtils.checkAndUpdateConf (cyclomatic 16) |
| core/src/main/scala/ai/h2o/sparkling/H2OContext.scala | 7.8 | Mixed | Cognitive Complexity: H2OContext.createHeartBeatEventThread (cognitive 20) |
| doc/src/main/scala/ai/h2o/sparkling/doc/generation/Runner.scala | 7.8 | Mixed | Cognitive Complexity: Runner.main (cognitive 19) |
| core/src/main/scala/ai/h2o/sparkling/backend/SharedBackendConf.scala | 7.8 | Mixed | God Classes: TooManyMethods: SharedBackendConf |
| ml/src/main/scala/ai/h2o/sparkling/ml/params/HyperParamsParam.scala | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| core/src/main/scala/ai/h2o/sparkling/H2OFrame.scala | 7.8 | Mixed | Code Duplication: Duplicated block (15–16 lines × 2) |
| core/src/main/scala_spark_2.1/org/apache/spark/h2o/ui/SparklingWaterListener.scala | 7.8 | Mixed | Code Duplication: Duplicated block (16 lines × 2) |
| ml/src/main/scala/ai/h2o/sparkling/ml/params/NullableStringPairArrayParam.scala | 7.8 | Mixed | Code Duplication: Duplicated block (15 lines × 2) |
| examples/src/main/scala/ai/h2o/sparkling/examples/ChicagoCrimeApp.scala | 7.8 | Mixed | Code Duplication: Duplicated block (17 lines × 2) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog 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. 58 of 58 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 58 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, 347 of 356 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala, .py) 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or `coverage run -m pytest` then `coverage xml`) 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or `coverage run -m pytest` then `coverage xml`) 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 — Watchdog 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 repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.scala, .py), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- D12 Dependency Hygiene — not measured this run — Watchdog 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 — 26 Maven/Gradle manifest(s) were read, stating a version for 21 dependency(ies) and leaving 86 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. 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. All 195 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 152 of the 597 production source files in this repository: 402 are under the ~2,400-byte size floor this dimension measures over, and the remaining 43 have no attributable history left to measure.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 — Watchdog measured this, but not all of it. What it 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 — Watchdog 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 — Watchdog 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 a COLLECTOR gap, not an environment fault: it declares a published package (py-scoring/src/pyproject.toml), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `dist/src/buildinfo.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `core/src/main/scala/org/apache/spark/h2o/ui/SparklingWaterInfoPage.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
- P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- S1 Web-Security Posture — not measured this run — Watchdog 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.
- X4 Structured logging — not measured this run — Watchdog 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, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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.
- 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
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ExternalH2OBackend.checkAndUpdateConf at 27. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ProblemType.distributionToProblemType at 17 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: ml/src/main/scala/ai/h2o/sparkling/ml/algos/ProblemType.scala (ProblemType.distributionToProblemType at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ExternalH2OBackend.checkAndUpdateConf (cyclomatic 27), RowConverter.toH2ORowData (cyclomatic 21), H2OMOJOPipelineModel.rowsToMojoFrame (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was ExternalH2OBackend.checkAndUpdateConf at 51.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with ExternalH2OBackend.checkAndUpdateConf (cognitive 51). — Refactoring it lifts Cognitive Complexity from 8.1 to about 8.6/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with SharedBackendConf.scala, ExternalBackendConf.scala, H2OTypeConverters.py. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with SharedBackendConf.scala. — 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
31 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 2 of the 32 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 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ParametersTemplateBase.scala, HasGamColsOnMOJO.scala, SchemaUtils.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with H2OFrame.scala, ChunkServlet.scala, DataFramesServlet.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with MOJOModelTemplate.scala, SparkSpecificUtils.scala, H2ODataFrameConverters.py. — One of this dimension's main actionable groups (3 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
25 production modules (Gradle+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 13 of the 25 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
1 of 42 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with H2OTargetEncoder.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
812 test methods: 698 unit, 14 integration, 100 BDD, 0 e2e. The Python suite contributes 260 test function(s) across 38 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Scala suite contributes 552 test case(s) across 68 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
What to do
- Improve Test Distribution — currently 8.8/10. — 812 test methods: 698 unit, 14 integration, 100 BDD, 0 e2e. The Python suite contributes 260 test function(s) across 38 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Scala suite contributes 552 test case(s) across 68 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 12 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 26 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 86 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. 1 of them resolve to no licence at all on Central, even through their parent POMs; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 34649 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.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with H2OMOJOModelTestSuite.scala, H2OSupervisedMOJOModelTestSuite.scala, H2OAutoMLTestSuite.scala. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 84 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.rst. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 14 build units (Gradle, Python) 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).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 2 high, 3 medium, 1 low. semgrep hit a parse error in 2 file(s) — `core/src/main/scala/org/apache/spark/h2o/ui/SparklingWaterInfoPage.scala`, `gradlew` (line 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
73 finding(s): 4 critical, 17 high, 35 medium, 17 low.
What to do
- Resolve the 35 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (19), REDACTED (14), REDACTED. — One of this dimension's main actionable groups (35 warning-level).
- Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (14), REDACTED (3). — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 4 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
D34 · Knowledge Freshness
195 of 195 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/src/main/scala/ai/h2o/sparkling/backend/SharedBackendConf.scala. Counted over 195 of the 597 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 192 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (10), __init__.py (4), H2OFrame.scala (2). — One of this dimension's main actionable groups (192 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with SharedBackendConf.scala, H2OMOJOModel.scala, H2OContext.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 23 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
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×3) — core/src/integTest/scala/ai/h2o/sparkling/PamProxyOnlyModeAuthCustomUserTestSuite.scala:30, core/src/integTest/scala/ai/h2o/sparkling/PamProxyOnlyModeAuthTestSuite.scala:30, ml/src/test/scala/ai/h2o/sparkling/ml/models/H2OSupervisedMOJOModelTestSuite.scala:172
- `validate` has an empty body — confirm it's an intentional no-op and not an unfinished method. — core/src/main/scala/ai/h2o/sparkling/backend/api/scalainterpreter/ScalaCodeResult.scala:30
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 22 of 26 project(s) that lack one — worth up to 1.7 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.
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.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P10 · Library API & versioning
P2 · Observability
- Only 4/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `api-generation`, `booklet`, `doc`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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
- Run what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 5 use(s) across 32,054 production line(s) (~0.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `new JarFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and it is held in `jarFile`, and every later use of `jarFile` in its block reads a member through it — it is never returned, passed, stored, captured by a lambda, reassigned or released, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(new JarFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — doc/src/main/scala/ai/h2o/sparkling/doc/generation/Runner.scala:117
- `Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.getLines` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — core/src/main/scala/ai/h2o/sparkling/backend/external/ExternalH2OBackend.scala:86
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
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
- `except` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:199
- `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — core/src/main/scala/ai/h2o/sparkling/backend/H2ORDD.scala:103
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — core/src/main/scala/ai/h2o/sparkling/backend/utils/ProxyStarter.scala:73
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 417 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Exemplary | Strongest area. |
| Maturity | 49% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62% | Adequate — gated by D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 67% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- D11 Test Reliability — 2 observation(s) recorded · This repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.scala, .py), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- X10 Duplicated predicate — 5 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 — 55 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 applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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.
- D10 Test Quality — ~15571 lines of test source are present (.scala, .py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Not scored — 26 Maven/Gradle manifest(s) were read, stating a version for 21 dependency(ies) and leaving 86 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, Python, Scala 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .java, .py, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 31 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 84 current-state document(s) make no claim of a kind M4 checks. 20 claim(s) of kinds M4 does not check were not checked (environment variable 20); M4 checks only links and versions.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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
- 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.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala, Java and Python were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- 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 — 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
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 26 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test declared unreliable: testPamAuthWithCorrectCredentials py/tests/integration/external_only/test_security.py:74
- Test declared unreliable: testPamAuthWithWrongCredentials py/tests/integration/external_only/test_security.py:87
- REDACTED
- REDACTED
- REDACTED
Serious — 98 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: SharedBackendConf core/src/main/scala/ai/h2o/sparkling/backend/SharedBackendConf.scala:28
- TooManyMethods: ExternalBackendConf core/src/main/scala/ai/h2o/sparkling/backend/external/ExternalBackendConf.scala:32
- TooManyMethods: H2OTypeConverters py-scoring/src/ai/h2o/sparkling/ml/params/H2OTypeConverters.py:26
- TooManyMethods: H2OContext core/src/main/scala/ai/h2o/sparkling/H2OContext.scala:64
- TooManyMethods: H2OMOJOModel scoring/src/main/scala/ai/h2o/sparkling/ml/models/H2OMOJOModel.scala:49
- Duplicated block (9 lines × 2) api-generation/src/main/scala/ai/h2o/sparkling/api/generation/scala/ParametersTemplateBase.scala:61
- Duplicated block (9 lines × 2) scoring/src/main/scala/ai/h2o/sparkling/ml/params/HasGamColsOnMOJO.scala:33
- Duplicated block (9 lines × 2) utils/src/main/scala/ai/h2o/sparkling/ml/utils/SchemaUtils.scala:249
- Duplicated block (9 lines × 2) core/src/main/scala_spark_2.1/org/apache/spark/h2o/SparkSpecificUtils.scala:33
- Duplicated block (9 lines × 2) core/src/main/scala_spark_2.1/org/apache/spark/h2o/ui/SparklingWaterListener.scala:90
- TodoComment ml/src/test/scala/ai/h2o/sparkling/ml/models/H2OMOJOModelTestSuite.scala:113
- TodoComment ml/src/test/scala/ai/h2o/sparkling/ml/models/H2OSupervisedMOJOModelTestSuite.scala:170
- TodoComment ml/src/test/scala/ai/h2o/sparkling/ml/algos/H2OAutoMLTestSuite.scala:69
- Duplicated block (7 lines × 2) core/src/main/scala/ai/h2o/sparkling/H2OFrame.scala:245
- Duplicated block (7 lines × 2) extensions/src/main/scala/ai/h2o/sparkling/extensions/rest/api/ChunkServlet.scala:90
- Duplicated block (7 lines × 2) core/src/main/scala/ai/h2o/sparkling/backend/api/dataframes/DataFramesServlet.scala:32
- Duplicated block (6 lines × 2) api-generation/src/main/scala/ai/h2o/sparkling/api/generation/python/MOJOModelTemplate.scala:34
- Duplicated block (6 lines × 2) core/src/main/scala_spark_2.3/org/apache/spark/h2o/SparkSpecificUtils.scala:39
- Duplicated block (6 lines × 2) py-scoring/src/ai/h2o/sparkling/H2ODataFrameConverters.py:40
- Duplicated block (10 lines × 2) ml/src/main/scala/ai/h2o/sparkling/ml/params/NullableStringPairArrayParam.scala:43
- Duplicated block (10 lines × 2) core/src/main/scala_spark_2.3/org/apache/spark/h2o/ui/AppStatusPlugin.scala:29
- Duplicated block (8 lines × 2) core/src/main/scala/ai/h2o/sparkling/backend/utils/ReflectionUtils.scala:183
- Duplicated block (8 lines × 2) extensions/src/main/scala/ai/h2o/sparkling/extensions/internals/ConvertCategoricalToStringColumnsTask.java:39
- Duplicated block (7 lines × 3) core/src/main/scala/ai/h2o/sparkling/backend/converters/SupportedDataset.scala:145
- Duplicated block (7 lines × 3) core/src/main/scala/ai/h2o/sparkling/backend/converters/SupportedRDD.scala:168
- Disposable created and abandoned in the function that made it doc/src/main/scala/ai/h2o/sparkling/doc/generation/Runner.scala:117
- Disposable created and abandoned in the function that made it core/src/main/scala/ai/h2o/sparkling/backend/external/ExternalH2OBackend.scala:86
- Swallowed exception (caught, then discarded) REDACTED:199
- Swallowed exception (caught, then discarded) core/src/main/scala/ai/h2o/sparkling/backend/H2ORDD.scala:103
- ExternalH2OBackend.checkAndUpdateConf (cyclomatic 27) core/src/main/scala/ai/h2o/sparkling/backend/external/ExternalH2OBackend.scala:177
- RowConverter.toH2ORowData (cyclomatic 21) scoring/src/main/scala/ai/h2o/sparkling/ml/models/RowConverter.scala:35
- H2OMOJOPipelineModel.rowsToMojoFrame (cyclomatic 18) scoring/src/main/scala/ai/h2o/sparkling/ml/models/H2OMOJOPipelineModel.scala:152
- Writer.sparkRowToH2ORow (cyclomatic 17) core/src/main/scala/ai/h2o/sparkling/backend/Writer.scala:130
- SharedBackendUtils.checkAndUpdateConf (cyclomatic 16) core/src/main/scala/ai/h2o/sparkling/backend/utils/SharedBackendUtils.scala:51
- ExternalH2OBackend.checkAndUpdateConf (cognitive 51) core/src/main/scala/ai/h2o/sparkling/backend/external/ExternalH2OBackend.scala:177
- SharedBackendUtils.checkAndUpdateConf (cognitive 22) core/src/main/scala/ai/h2o/sparkling/backend/utils/SharedBackendUtils.scala:51
- H2OContext.createHeartBeatEventThread (cognitive 20) core/src/main/scala/ai/h2o/sparkling/H2OContext.scala:335
- Runner.main (cognitive 19) doc/src/main/scala/ai/h2o/sparkling/doc/generation/Runner.scala:39
- ChunkAutoBufferWriter.writeChunk (cognitive 19) extensions/src/main/scala/ai/h2o/sparkling/extensions/serde/ChunkAutoBufferWriter.scala:33
- Runner.getParamClasses (cognitive 17) doc/src/main/scala/ai/h2o/sparkling/doc/generation/Runner.scala:109
- H2OContext.__prepareSparkDataForConversion (cognitive 17) py/src/ai/h2o/sparkling/H2OContext.py:209
- H2OMOJOPipelineModel.rowsToMojoFrame (cognitive 16) scoring/src/main/scala/ai/h2o/sparkling/ml/models/H2OMOJOPipelineModel.scala:152
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: backend/SharedBackendConf.scala core/src/main/scala/ai/h2o/sparkling/backend/SharedBackendConf.scala
- Members sharing a duplicated core (4 members, 50+ identical tokens) ml/src/main/scala/ai/h2o/sparkling/ml/params/HyperParamsParam.scala:67
- Duplicated block (15–16 lines × 2) core/src/main/scala/ai/h2o/sparkling/H2OFrame.scala:64
- Duplicated block (16 lines × 2) core/src/main/scala_spark_2.1/org/apache/spark/h2o/ui/SparklingWaterListener.scala:47
- Duplicated block (14–16 lines × 2) ml/src/main/scala/ai/h2o/sparkling/ml/algos/H2OEstimator.scala:46
- Duplicated block (15 lines × 2) ml/src/main/scala/ai/h2o/sparkling/ml/params/NullableStringPairArrayParam.scala:56
- Duplicated block (14 lines × 2) core/src/main/scala/ai/h2o/sparkling/backend/BuildInfo.scala:61
- Duplicated block (11 lines × 4) ml/src/main/scala/ai/h2o/sparkling/ml/params/HyperParamsParam.scala:68
- Duplicated block (11 lines × 2) scoring/src/main/scala/ai/h2o/sparkling/ml/models/H2OMOJOPredictionWordEmbedding.scala:44
- Duplicated block (3–8 lines × 3) booklet/src/main/scala/ai/h2o/sparkling/booklet/generation/ConfigurationsTemplate.scala:93
- Duplicated block (7–8 lines × 2) utils/src/main/scala/ai/h2o/sparkling/utils/DataFrameJsonSerialization.scala:36
- Duplicated block (13 lines × 2) booklet/src/main/scala/ai/h2o/sparkling/booklet/generation/ConfigurationRunner.scala:25
- Duplicated block (33 lines × 2) core/src/main/scala_spark_2.3/org/apache/spark/h2o/ui/AppStatusListener.scala:32
- Duplicated block (28 lines × 2) core/src/main/scala_spark_2.3/org/apache/spark/h2o/ui/AppStatusStore.scala:29
- Duplicated block (17 lines × 2) examples/src/main/scala/ai/h2o/sparkling/examples/ChicagoCrimeApp.scala:97
- Duplicated block (12 lines × 2) examples/src/main/scala/ai/h2o/sparkling/examples/ChicagoCrimeApp.scala:213
- Low cohesion: H2OTargetEncoder (LCOM4 4) ml/src/main/scala/ai/h2o/sparkling/ml/features/H2OTargetEncoder.scala:34
- Swallowed exception (empty catch) core/src/main/scala/ai/h2o/sparkling/backend/utils/ProxyStarter.scala:73
Minor — 232 finding(s)
- Orphaned file core/src/main/scala/ai/h2o/sparkling/backend/external/ExternalBackendConf.scala:1
- Orphaned file core/src/main/scala/ai/h2o/sparkling/backend/utils/RestCommunication.scala:1
- Orphaned file utils/src/main/scala/ai/h2o/sparkling/ml/utils/SchemaUtils.scala:1
- Orphaned file py-scoring/src/ai/h2o/sparkling/ml/params/H2OTypeConverters.py:1
- Orphaned file scoring/src/main/scala/ai/h2o/sparkling/ml/models/H2OMOJOPipelineModel.scala:1
- Orphaned file core/src/main/scala/ai/h2o/sparkling/H2OFrame.scala:1
- Orphaned file core/src/main/scala/ai/h2o/sparkling/backend/external/ExternalH2OBackend.scala:1
- Orphaned file py/build.gradle:1
- Orphaned file ml/src/main/scala/ai/h2o/sparkling/ml/algos/H2OGridSearch.scala:1
- Orphaned file api-generation/src/main/scala/ai/h2o/sparkling/api/generation/common/AlgorithmConfigurations.scala:1
- Orphaned file REDACTED:1
- Orphaned file core/src/main/scala/ai/h2o/sparkling/backend/utils/SharedBackendUtils.scala:1
- Orphaned file py/src/ai/h2o/sparkling/H2OContext.py:1
- Orphaned file api-generation/src/main/scala/ai/h2o/sparkling/api/generation/scala/MOJOModelTemplate.scala:1
- Orphaned file core/src/main/scala/ai/h2o/sparkling/backend/utils/H2OContextExtensions.scala:1
- Orphaned file extensions/src/main/scala/ai/h2o/sparkling/extensions/rest/api/ChunkServlet.scala:1
- Orphaned file repl/src/main/scala/ai/h2o/sparkling/repl/BaseH2OInterpreter.scala:1
- Orphaned file ml/src/main/scala/ai/h2o/sparkling/ml/algos/H2OAutoML.scala:1
- Orphaned file gradle/utils.gradle:1
- Orphaned file ci/build.gradle:1
- Orphaned file build.gradle:1
- Orphaned file core/src/main/scala/org/apache/spark/h2o/backends/internal/InternalH2OBackend.scala:1
- Orphaned file core/src/main/scala/ai/h2o/sparkling/backend/internal/InternalBackendConf.scala:1
- Orphaned file core/src/main/scala/ai/h2o/sparkling/backend/converters/SupportedRDD.scala:1
- Orphaned file core/src/main/scala/ai/h2o/sparkling/backend/utils/ReflectionUtils.scala:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate core/src/main/scala/ai/h2o/sparkling/H2OContext.scala:246
- Duplicated predicate scoring/src/main/scala/ai/h2o/sparkling/ml/models/H2OTargetEncoderBase.scala:35
- Duplicated predicate api-generation/src/main/scala/ai/h2o/sparkling/api/generation/scala/MOJOModelTemplate.scala:143
- Duplicated predicate ml/src/main/scala/ai/h2o/sparkling/ml/algos/classification/DistributionForClassificationCheck.scala:30
- Duplicated predicate ml/src/main/scala/ai/h2o/sparkling/ml/algos/regression/DistributionForRegressionCheck.scala:30
- Most significant orphaned file core/src/main/scala/ai/h2o/sparkling/backend/SharedBackendConf.scala:1
- Most significant orphaned file scoring/src/main/scala/ai/h2o/sparkling/ml/models/H2OMOJOModel.scala:1
- Most significant orphaned file core/src/main/scala/ai/h2o/sparkling/H2OContext.scala:1
- Disabled test core/src/integTest/scala/ai/h2o/sparkling/PamProxyOnlyModeAuthCustomUserTestSuite.scala:30
- Disabled test core/src/integTest/scala/ai/h2o/sparkling/PamProxyOnlyModeAuthTestSuite.scala:30
- Disabled test ml/src/test/scala/ai/h2o/sparkling/ml/models/H2OSupervisedMOJOModelTestSuite.scala:172
- Documentation: no build, run or usage example README.rst:1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Dormant codebase
- Empty method body core/src/main/scala/ai/h2o/sparkling/backend/api/scalainterpreter/ScalaCodeResult.scala:30
- No ADRs
- Logging is not universal
- No SAST
- Benchmarks don't track allocations
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-eea7756d03804436a56792411f383b9b/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-eea7756d03804436a56792411f383b9b/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/watchdog-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 . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 73 | 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. semgrep could not parse 1 file(s) — `core/src/main/scala/org/apache/spark/h2o/ui/SparklingWaterInfoPage.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |