Executive summary
salesforce/TransmogrifAI is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 62 out of 100, which the At risk rating leaves unchanged.
Code Health, at 56, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Declaring which values may be missing would lift Code Health itself, worth about 4 points. Raising Code Health to 70 would lift the score to about 66.
Twenty-six known security holes in the packages the code depends on can be used by attackers. One password or key is open to anyone who can read the repository. Updating the vulnerable packages and replacing the exposed password or key would close both risks.
The product code is 55,548 lines, about €120,000 to rebuild.
If Code Health rose from 56 to 70, the lowest score rated Strong, the score would rise from 62 to about 66.
New since the last survey: 42 findings
- Code Duplication · Near-duplicate member pair (54 shared lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala
- Code Duplication · Edited copy of a member (56 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala
- Code Duplication · Edited copy of a member (31 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala
- Code Duplication · Edited copy of a member (27 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/MultiPickListMapVectorizer.scala
- Code Duplication · Edited copy of a member (22 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/MultiPickListMapVectorizer.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) core/src/main/scala/com/salesforce/op/stages/sparkwrappers/generic/SwQuaternaryEstimator.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) features/src/main/scala/com/salesforce/op/stages/base/quaternary/QuaternaryEstimator.scala
- Code Duplication · Edited copy of a member (28 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/TextMapLenEstimator.scala
- Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) core/src/main/scala/com/salesforce/op/evaluators/Evaluators.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichNumericFeature.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) utils/src/main/scala/com/salesforce/op/utils/spark/SequenceAggregators.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) core/src/main/scala/com/salesforce/op/stages/sparkwrappers/generic/SwQuaternaryTransformer.scala
- Code Duplication · Edited copy of a member (18 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala
- Code Duplication · Edited copy of a member (20 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) core/src/main/scala/com/salesforce/op/stages/sparkwrappers/generic/SwSequenceEstimator.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/DateMapToUnitCircleVectorizer.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) features/src/main/scala/com/salesforce/op/stages/base/sequence/BinarySequenceTransformer.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/IntegralVectorizer.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) features/src/main/scala/com/salesforce/op/stages/base/binary/BinaryEstimator.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/OPMapVectorizer.scala
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) features/src/main/scala/com/salesforce/op/stages/base/binary/BinaryTransformer.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichDateFeature.scala
- Code Duplication · Edited copy of a member (20 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/DateMapToUnitCircleVectorizer.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala
- Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/PhoneNumberParser.scala
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) features/src/main/scala/com/salesforce/op/OpParams.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/DropIndicesByTransformer.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/regression/RegressionModelSelector.scala
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) core/src/main/scala/com/salesforce/op/stages/sparkwrappers/generic/SwBinaryTransformer.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/GeolocationVectorizer.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) core/src/main/scala/com/salesforce/op/evaluators/OpMultiClassificationEvaluator.scala
- Code Duplication · Edited copy of a member (2 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 13 findings
- Code Duplication · Near-duplicate member pair (23 shared lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala
- Code Duplication · Duplicated block (16–17 lines × 3) helloworld/src/main/scala/com/salesforce/hw/OpBostonSimple.scala
- Code Duplication · Duplicated block (6 lines × 2) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/FeatureAggregator.scala
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/Lists.scala
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/Lists.scala
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/Maps.scala
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/Maps.scala
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/Maps.scala
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/Maps.scala
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/Maps.scala
- Slice cohesion · Cross-slice coupling: src → types features/src/main/scala/com/salesforce/op/aggregators/Maps.scala
Rebuild cost: about €120,000 · Estimate
| Cost to rebuild | €40,000 to €200,000, for 666 to 2,111 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 62. 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: 55,548 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 com.salesforce.op.features.types | 2 com.salesforce.op.features.types.NameStats | 3 com.salesforce.op.utils.json | 4 com.salesforce.op.utils.text | 5 ml.dmlc.xgboost4j.scala.spark | 6 com.salesforce.op.aggregators | 7 com.salesforce.op.cli.gen | 8 com.salesforce.op.stages.impl.feature.TextTokenizer | 9 com.salesforce.op.utils.spark | 10 com.salesforce.op.utils.stages | 11 com.salesforce.op.cli | 12 com.salesforce.op.stages | 13 com.salesforce.op.features | 14 com.salesforce.op.readers | 15 com.salesforce.op.stages.base.binary | 16 com.salesforce.op.stages.base.unary | 17 com.salesforce.op.stages.sparkwrappers.generic | 18 com.salesforce.op.cli.gen.templates | 19 com.salesforce.op.evaluators | 20 com.salesforce.op.stages.impl | 21 com.salesforce.op.stages.sparkwrappers.specific | 22 com.salesforce.op.stages.impl.tuning | 23 com.salesforce.op.stages.impl.selector | 24 com.salesforce.op.stages.impl.classification | 25 com.salesforce.op.stages.impl.regression | 26 com.salesforce.op.dsl.RichVectorFeature | 27 com.salesforce.op.stages.impl.feature | 28 com.salesforce.op.dsl.RichDateFeature | 29 com.salesforce.op.dsl.RichListFeature | 30 com.salesforce.op.dsl.RichMapFeature | 31 com.salesforce.op.dsl.RichTextFeature | 32 com.salesforce.op.stages.impl.preparators | 33 com.salesforce.op.dsl.RichNumericFeature | 34 com.salesforce.op.filters | 35 com.salesforce.op | 36 com.salesforce.app.Simple | 37 com.salesforce.hw.boston | 38 com.salesforce.hw.iris | 39 com.salesforce.op.stages.impl.insights | 40 com.salesforce.hw.boston.BostonFeatures |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.salesforce.op.features.types | ||||||||||||||||||||||||||||||||||||||||
| 2 com.salesforce.op.features.types.NameStats | ||||||||||||||||||||||||||||||||||||||||
| 3 com.salesforce.op.utils.json | ||||||||||||||||||||||||||||||||||||||||
| 4 com.salesforce.op.utils.text | ||||||||||||||||||||||||||||||||||||||||
| 5 ml.dmlc.xgboost4j.scala.spark | ||||||||||||||||||||||||||||||||||||||||
| 6 com.salesforce.op.aggregators | 16 | |||||||||||||||||||||||||||||||||||||||
| 7 com.salesforce.op.cli.gen | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 com.salesforce.op.stages.impl.feature.TextTokenizer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 com.salesforce.op.utils.spark | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 com.salesforce.op.utils.stages | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 11 com.salesforce.op.cli | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 com.salesforce.op.stages | 2 | 13 | ||||||||||||||||||||||||||||||||||||||
| 13 com.salesforce.op.features | 53 | 1 | 2 | 7 | 2 | |||||||||||||||||||||||||||||||||||
| 14 com.salesforce.op.readers | 2 | 1 | 15 | |||||||||||||||||||||||||||||||||||||
| 15 com.salesforce.op.stages.base.binary | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 com.salesforce.op.stages.base.unary | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 com.salesforce.op.stages.sparkwrappers.generic | 10 | |||||||||||||||||||||||||||||||||||||||
| 18 com.salesforce.op.cli.gen.templates | 7 | 4 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 19 com.salesforce.op.evaluators | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 20 com.salesforce.op.stages.impl | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 com.salesforce.op.stages.sparkwrappers.specific | 9 | 1 | 2 | 5 | ||||||||||||||||||||||||||||||||||||
| 22 com.salesforce.op.stages.impl.tuning | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 com.salesforce.op.stages.impl.selector | 9 | 2 | 1 | 1 | 1 | 13 | 3 | 7 | 2 | |||||||||||||||||||||||||||||||
| 24 com.salesforce.op.stages.impl.classification | 1 | 2 | 2 | 16 | 2 | 4 | ||||||||||||||||||||||||||||||||||
| 25 com.salesforce.op.stages.impl.regression | 1 | 1 | 1 | 13 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 26 com.salesforce.op.dsl.RichVectorFeature | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 com.salesforce.op.stages.impl.feature | 59 | 6 | 10 | 1 | 1 | 17 | 8 | 6 | 8 | 18 | 52 | 1 | 1 | 8 | 1 | 1 | ||||||||||||||||||||||||
| 28 com.salesforce.op.dsl.RichDateFeature | 8 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 29 com.salesforce.op.dsl.RichListFeature | 8 | 4 | 4 | |||||||||||||||||||||||||||||||||||||
| 30 com.salesforce.op.dsl.RichMapFeature | 34 | 2 | 16 | 8 | ||||||||||||||||||||||||||||||||||||
| 31 com.salesforce.op.dsl.RichTextFeature | 29 | 5 | 1 | 8 | 4 | |||||||||||||||||||||||||||||||||||
| 32 com.salesforce.op.stages.impl.preparators | 7 | 3 | 2 | 6 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 33 com.salesforce.op.dsl.RichNumericFeature | 12 | 5 | 5 | 3 | ||||||||||||||||||||||||||||||||||||
| 34 com.salesforce.op.filters | 4 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 35 com.salesforce.op | 6 | 1 | 1 | 2 | 4 | 4 | 1 | 1 | 1 | 8 | ||||||||||||||||||||||||||||||
| 36 com.salesforce.app.Simple | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 com.salesforce.hw.boston | 3 | |||||||||||||||||||||||||||||||||||||||
| 38 com.salesforce.hw.iris | 3 | |||||||||||||||||||||||||||||||||||||||
| 39 com.salesforce.op.stages.impl.insights | 3 | 2 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 40 com.salesforce.hw.boston.BostonFeatures | 3 | 3 |
6→1 com.salesforce.op.aggregators uses com.salesforce.op.features.types✕
- Connections
- 16 pairs of types, where a type in com.salesforce.op.aggregators uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.aggregators.AggregatorDefaults→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.aggregators.ConcatList→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.aggregators.GeolocationFunctions→com.salesforce.op.features.types.Geolocationcom.salesforce.op.aggregators.GeolocationMidpoint→com.salesforce.op.features.types.Geolocationcom.salesforce.op.aggregators.MeanPercent→com.salesforce.op.features.types.Percentcom.salesforce.op.aggregators.MinMaxList→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.aggregators.ModePickList→com.salesforce.op.features.types.PickListcom.salesforce.op.aggregators.UnionBinaryMap→com.salesforce.op.features.types.BinaryMapcom.salesforce.op.aggregators.UnionBinaryMap→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.aggregators.UnionConcatTextMap→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.aggregators.UnionGeolocationMidpointMap→com.salesforce.op.features.types.GeolocationMapcom.salesforce.op.aggregators.UnionMeanDoubleMap→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.aggregators.UnionMeanPercentMap→com.salesforce.op.features.types.PercentMapcom.salesforce.op.aggregators.UnionMinMaxNumericMap→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.aggregators.UnionSetMap→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.aggregators.UnionSumNumericMap→com.salesforce.op.features.types.FeatureTypeFactory
- Direction
- com.salesforce.op.aggregators uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.aggregators, while a change to com.salesforce.op.aggregators can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.aggregators uses a module listed above it, which is the healthy direction.
7→11 com.salesforce.op.cli.gen uses com.salesforce.op.cli part of a loop✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.cli.gen uses a type in com.salesforce.op.cli.
- The types involved
com.salesforce.op.cli.gen.Ops→com.salesforce.op.cli.GeneratorConfigcom.salesforce.op.cli.gen.ProjectGenerator→com.salesforce.op.cli.GeneratorConfig
- Direction
- com.salesforce.op.cli.gen uses com.salesforce.op.cli, so a change to com.salesforce.op.cli can break com.salesforce.op.cli.gen, while a change to com.salesforce.op.cli.gen can't break com.salesforce.op.cli.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 com.salesforce.op.stages.impl.feature.TextTokenizer uses com.salesforce.op.features.types✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.feature.TextTokenizer uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.stages.impl.feature.TextTokenizer.TextTokenizerResult→com.salesforce.op.features.types.TextList
- Direction
- com.salesforce.op.stages.impl.feature.TextTokenizer uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.stages.impl.feature.TextTokenizer, while a change to com.salesforce.op.stages.impl.feature.TextTokenizer can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature.TextTokenizer uses a module listed above it, which is the healthy direction.
8→4 com.salesforce.op.stages.impl.feature.TextTokenizer uses com.salesforce.op.utils.text✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.feature.TextTokenizer uses a type in com.salesforce.op.utils.text.
- The types involved
com.salesforce.op.stages.impl.feature.TextTokenizer.TextTokenizerResult→com.salesforce.op.utils.text.Language
- Direction
- com.salesforce.op.stages.impl.feature.TextTokenizer uses com.salesforce.op.utils.text, so a change to com.salesforce.op.utils.text can break com.salesforce.op.stages.impl.feature.TextTokenizer, while a change to com.salesforce.op.stages.impl.feature.TextTokenizer can't break com.salesforce.op.utils.text.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature.TextTokenizer uses a module listed above it, which is the healthy direction.
9→3 com.salesforce.op.utils.spark uses com.salesforce.op.utils.json✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.utils.spark uses a type in com.salesforce.op.utils.json.
- The types involved
com.salesforce.op.utils.spark.MetricJsonLike→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.utils.spark.OpVectorColumnHistory→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.utils.spark.OpVectorColumnMetadata→com.salesforce.op.utils.json.JsonLike
- Direction
- com.salesforce.op.utils.spark uses com.salesforce.op.utils.json, so a change to com.salesforce.op.utils.json can break com.salesforce.op.utils.spark, while a change to com.salesforce.op.utils.spark can't break com.salesforce.op.utils.json.
- Position
- Below the diagonal: com.salesforce.op.utils.spark uses a module listed above it, which is the healthy direction.
9→35 com.salesforce.op.utils.spark uses com.salesforce.op part of a loop✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.utils.spark uses a type in com.salesforce.op.
- The types involved
com.salesforce.op.utils.spark.OpVectorMetadata→com.salesforce.op.FeatureHistorycom.salesforce.op.utils.spark.OpVectorMetadata→com.salesforce.op.SensitiveFeatureInformation
- Direction
- com.salesforce.op.utils.spark uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.op.utils.spark, while a change to com.salesforce.op.utils.spark can't break com.salesforce.op.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 com.salesforce.op.utils.stages uses com.salesforce.op.features.types✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.utils.stages uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.utils.stages.NameDetectFun→com.salesforce.op.features.types.Text
- Direction
- com.salesforce.op.utils.stages uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.utils.stages, while a change to com.salesforce.op.utils.stages can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.utils.stages uses a module listed above it, which is the healthy direction.
10→2 com.salesforce.op.utils.stages uses com.salesforce.op.features.types.NameStats✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.utils.stages uses a type in com.salesforce.op.features.types.NameStats.
- The types involved
com.salesforce.op.utils.stages.NameDetectFun→com.salesforce.op.features.types.NameStats.GenderValue
- Direction
- com.salesforce.op.utils.stages uses com.salesforce.op.features.types.NameStats, so a change to com.salesforce.op.features.types.NameStats can break com.salesforce.op.utils.stages, while a change to com.salesforce.op.utils.stages can't break com.salesforce.op.features.types.NameStats.
- Position
- Below the diagonal: com.salesforce.op.utils.stages uses a module listed above it, which is the healthy direction.
10→3 com.salesforce.op.utils.stages uses com.salesforce.op.utils.json✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.utils.stages uses a type in com.salesforce.op.utils.json.
- The types involved
com.salesforce.op.utils.stages.NameDetectStats→com.salesforce.op.utils.json.JsonLike
- Direction
- com.salesforce.op.utils.stages uses com.salesforce.op.utils.json, so a change to com.salesforce.op.utils.json can break com.salesforce.op.utils.stages, while a change to com.salesforce.op.utils.stages can't break com.salesforce.op.utils.json.
- Position
- Below the diagonal: com.salesforce.op.utils.stages uses a module listed above it, which is the healthy direction.
10→27 com.salesforce.op.utils.stages uses com.salesforce.op.stages.impl.feature part of a loop✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.utils.stages uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.utils.stages.NameDetectFun→com.salesforce.op.stages.impl.feature.GenderDetectStrategycom.salesforce.op.utils.stages.NameDetectUtils→com.salesforce.op.stages.impl.feature.GenderDetectStrategy
- Direction
- com.salesforce.op.utils.stages uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.utils.stages, while a change to com.salesforce.op.utils.stages can't break com.salesforce.op.stages.impl.feature.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→35 com.salesforce.op.utils.stages uses com.salesforce.op part of a loop✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.utils.stages uses a type in com.salesforce.op.
- The types involved
com.salesforce.op.utils.stages.FitStagesUtil→com.salesforce.op.OpWorkflowcom.salesforce.op.utils.stages.NameDetectFun→com.salesforce.op.SensitiveFeatureInformation
- Direction
- com.salesforce.op.utils.stages uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.op.utils.stages, while a change to com.salesforce.op.utils.stages can't break com.salesforce.op.
- 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→7 com.salesforce.op.cli uses com.salesforce.op.cli.gen✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.cli uses a type in com.salesforce.op.cli.gen.
- The types involved
com.salesforce.op.cli.AutomaticSchema→com.salesforce.op.cli.gen.AvroFieldcom.salesforce.op.cli.AvroSchemaFromFile→com.salesforce.op.cli.gen.AvroFieldcom.salesforce.op.cli.SchemaSource→com.salesforce.op.cli.gen.AvroField
- Direction
- com.salesforce.op.cli uses com.salesforce.op.cli.gen, so a change to com.salesforce.op.cli.gen can break com.salesforce.op.cli, while a change to com.salesforce.op.cli can't break com.salesforce.op.cli.gen.
- Position
- Below the diagonal: com.salesforce.op.cli uses a module listed above it, which is the healthy direction.
12→6 com.salesforce.op.stages uses com.salesforce.op.aggregators✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages uses a type in com.salesforce.op.aggregators.
- The types involved
com.salesforce.op.stages.FeatureGeneratorStage→com.salesforce.op.aggregators.Eventcom.salesforce.op.stages.FeatureGeneratorStage→com.salesforce.op.aggregators.FeatureAggregator
- Direction
- com.salesforce.op.stages uses com.salesforce.op.aggregators, so a change to com.salesforce.op.aggregators can break com.salesforce.op.stages, while a change to com.salesforce.op.stages can't break com.salesforce.op.aggregators.
- Position
- Below the diagonal: com.salesforce.op.stages uses a module listed above it, which is the healthy direction.
12→13 com.salesforce.op.stages uses com.salesforce.op.features part of a loop✕
- Connections
- 13 pairs of types, where a type in com.salesforce.op.stages uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.stages.FeatureGeneratorStage→com.salesforce.op.features.FeatureLikecom.salesforce.op.stages.HasIn1→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.HasIn1PlusN→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.HasIn2→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.HasIn3→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.HasIn4→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.HasInN→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.HasOut→com.salesforce.op.features.FeatureLikecom.salesforce.op.stages.InputParams→com.salesforce.op.features.FeatureLikecom.salesforce.op.stages.InputParams→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.OpPipelineStage2N→com.salesforce.op.features.FeatureLikecom.salesforce.op.stages.OpPipelineStageN→com.salesforce.op.features.FeatureLikecom.salesforce.op.stages.TransientFeatureArrayParam→com.salesforce.op.features.TransientFeature
- Direction
- com.salesforce.op.stages uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.stages, while a change to com.salesforce.op.stages can't break com.salesforce.op.features.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 com.salesforce.op.features uses com.salesforce.op.features.types✕
- Connections
- 53 pairs of types, where a type in com.salesforce.op.features uses a type in com.salesforce.op.features.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Base64com.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Base64Mapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Binarycom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.BinaryMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Citycom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.CityMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.ComboBoxcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.ComboBoxMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Countrycom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.CountryMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Currencycom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.CurrencyMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Datecom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.DateListcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.DateMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.DateTimecom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.DateTimeListcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.DateTimeMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Emailcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.EmailMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Geolocationcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.GeolocationMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.IDcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.IDMapcom.salesforce.op.features.FeatureBuilder→com.salesforce.op.features.types.Integral
- Direction
- com.salesforce.op.features uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.features, while a change to com.salesforce.op.features can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.features uses a module listed above it, which is the healthy direction.
13→6 com.salesforce.op.features uses com.salesforce.op.aggregators✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.features uses a type in com.salesforce.op.aggregators.
- The types involved
com.salesforce.op.features.FeatureBuilderWithExtract→com.salesforce.op.aggregators.Event
- Direction
- com.salesforce.op.features uses com.salesforce.op.aggregators, so a change to com.salesforce.op.aggregators can break com.salesforce.op.features, while a change to com.salesforce.op.features can't break com.salesforce.op.aggregators.
- Position
- Below the diagonal: com.salesforce.op.features uses a module listed above it, which is the healthy direction.
13→9 com.salesforce.op.features uses com.salesforce.op.utils.spark✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.features uses a type in com.salesforce.op.utils.spark.
- The types involved
com.salesforce.op.features.TransientFeature→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.features.TransientFeature→com.salesforce.op.utils.spark.OpVectorMetadata
- Direction
- com.salesforce.op.features uses com.salesforce.op.utils.spark, so a change to com.salesforce.op.utils.spark can break com.salesforce.op.features, while a change to com.salesforce.op.features can't break com.salesforce.op.utils.spark.
- Position
- Below the diagonal: com.salesforce.op.features uses a module listed above it, which is the healthy direction.
13→12 com.salesforce.op.features uses com.salesforce.op.stages✕
- Connections
- 7 pairs of types, where a type in com.salesforce.op.features uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.features.Feature→com.salesforce.op.stages.OpPipelineStagecom.salesforce.op.features.FeatureLike→com.salesforce.op.stages.OpPipelineStagecom.salesforce.op.features.FeatureLike→com.salesforce.op.stages.OpPipelineStage1com.salesforce.op.features.FeatureLike→com.salesforce.op.stages.OpPipelineStage2com.salesforce.op.features.FeatureLike→com.salesforce.op.stages.OpPipelineStage3com.salesforce.op.features.FeatureLike→com.salesforce.op.stages.OpPipelineStage4com.salesforce.op.features.FeatureLike→com.salesforce.op.stages.OpPipelineStageN
- Direction
- com.salesforce.op.features uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.features, while a change to com.salesforce.op.features can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.features uses a module listed above it, which is the healthy direction.
13→35 com.salesforce.op.features uses com.salesforce.op part of a loop✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.features uses a type in com.salesforce.op.
- The types involved
com.salesforce.op.features.FeatureLike→com.salesforce.op.FeatureHistorycom.salesforce.op.features.TransientFeature→com.salesforce.op.FeatureHistory
- Direction
- com.salesforce.op.features uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.op.features, while a change to com.salesforce.op.features can't break com.salesforce.op.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→6 com.salesforce.op.readers uses com.salesforce.op.aggregators✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.readers uses a type in com.salesforce.op.aggregators.
- The types involved
com.salesforce.op.readers.AggregateParams→com.salesforce.op.aggregators.CutOffTimecom.salesforce.op.readers.ConditionalDataReader→com.salesforce.op.aggregators.CutOffTime
- Direction
- com.salesforce.op.readers uses com.salesforce.op.aggregators, so a change to com.salesforce.op.aggregators can break com.salesforce.op.readers, while a change to com.salesforce.op.readers can't break com.salesforce.op.aggregators.
- Position
- Below the diagonal: com.salesforce.op.readers uses a module listed above it, which is the healthy direction.
14→12 com.salesforce.op.readers uses com.salesforce.op.stages✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.readers uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.readers.Reader→com.salesforce.op.stages.FeatureGeneratorStage
- Direction
- com.salesforce.op.readers uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.readers, while a change to com.salesforce.op.readers can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.readers uses a module listed above it, which is the healthy direction.
14→35 com.salesforce.op.readers uses com.salesforce.op part of a loop✕
- Connections
- 15 pairs of types, where a type in com.salesforce.op.readers uses a type in com.salesforce.op.
- The types involved
com.salesforce.op.readers.AggregatedReader→com.salesforce.op.OpParamscom.salesforce.op.readers.AvroReader→com.salesforce.op.OpParamscom.salesforce.op.readers.CSVAutoReader→com.salesforce.op.OpParamscom.salesforce.op.readers.CSVProductReader→com.salesforce.op.OpParamscom.salesforce.op.readers.CSVReader→com.salesforce.op.OpParamscom.salesforce.op.readers.CustomReader→com.salesforce.op.OpParamscom.salesforce.op.readers.DataReader→com.salesforce.op.OpParamscom.salesforce.op.readers.FileStreamingAvroReader→com.salesforce.op.OpParamscom.salesforce.op.readers.JoinedAggregateDataReader→com.salesforce.op.OpParamscom.salesforce.op.readers.JoinedReader→com.salesforce.op.OpParamscom.salesforce.op.readers.ParquetProductReader→com.salesforce.op.OpParamscom.salesforce.op.readers.Reader→com.salesforce.op.OpParamscom.salesforce.op.readers.ReaderType→com.salesforce.op.OpParamscom.salesforce.op.readers.ReaderType→com.salesforce.op.ReaderParamscom.salesforce.op.readers.StreamingReader→com.salesforce.op.OpParams
- Direction
- com.salesforce.op.readers uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.op.readers, while a change to com.salesforce.op.readers can't break com.salesforce.op.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→12 com.salesforce.op.stages.base.binary uses com.salesforce.op.stages✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.stages.base.binary uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.stages.base.binary.BinaryEstimator→com.salesforce.op.stages.OpPipelineStage2com.salesforce.op.stages.base.binary.OpTransformer2→com.salesforce.op.stages.OpPipelineStage2com.salesforce.op.stages.base.binary.OpTransformer2→com.salesforce.op.stages.OpTransformer
- Direction
- com.salesforce.op.stages.base.binary uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.stages.base.binary, while a change to com.salesforce.op.stages.base.binary can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.stages.base.binary uses a module listed above it, which is the healthy direction.
16→12 com.salesforce.op.stages.base.unary uses com.salesforce.op.stages✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.stages.base.unary uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.stages.base.unary.OpTransformer1→com.salesforce.op.stages.OpPipelineStage1com.salesforce.op.stages.base.unary.OpTransformer1→com.salesforce.op.stages.OpTransformercom.salesforce.op.stages.base.unary.UnaryEstimator→com.salesforce.op.stages.OpPipelineStage1
- Direction
- com.salesforce.op.stages.base.unary uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.stages.base.unary, while a change to com.salesforce.op.stages.base.unary can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.stages.base.unary uses a module listed above it, which is the healthy direction.
17→12 com.salesforce.op.stages.sparkwrappers.generic uses com.salesforce.op.stages✕
- Connections
- 10 pairs of types, where a type in com.salesforce.op.stages.sparkwrappers.generic uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.stages.sparkwrappers.generic.SwBinaryEstimator→com.salesforce.op.stages.OpPipelineStage2com.salesforce.op.stages.sparkwrappers.generic.SwQuaternaryEstimator→com.salesforce.op.stages.OpPipelineStage4com.salesforce.op.stages.sparkwrappers.generic.SwSequenceEstimator→com.salesforce.op.stages.OpPipelineStageNcom.salesforce.op.stages.sparkwrappers.generic.SwTernaryEstimator→com.salesforce.op.stages.OpPipelineStage3com.salesforce.op.stages.sparkwrappers.generic.SwTransformer1→com.salesforce.op.stages.OpPipelineStage1com.salesforce.op.stages.sparkwrappers.generic.SwTransformer2→com.salesforce.op.stages.OpPipelineStage2com.salesforce.op.stages.sparkwrappers.generic.SwTransformer3→com.salesforce.op.stages.OpPipelineStage3com.salesforce.op.stages.sparkwrappers.generic.SwTransformer4→com.salesforce.op.stages.OpPipelineStage4com.salesforce.op.stages.sparkwrappers.generic.SwTransformerN→com.salesforce.op.stages.OpPipelineStageNcom.salesforce.op.stages.sparkwrappers.generic.SwUnaryEstimator→com.salesforce.op.stages.OpPipelineStage1
- Direction
- com.salesforce.op.stages.sparkwrappers.generic uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.stages.sparkwrappers.generic, while a change to com.salesforce.op.stages.sparkwrappers.generic can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.stages.sparkwrappers.generic uses a module listed above it, which is the healthy direction.
18→1 com.salesforce.op.cli.gen.templates uses com.salesforce.op.features.types✕
- Connections
- 7 pairs of types, where a type in com.salesforce.op.cli.gen.templates uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.cli.gen.templates.BinaryClassificationTemplate→com.salesforce.op.features.types.OPVectorcom.salesforce.op.cli.gen.templates.BinaryClassificationTemplate→com.salesforce.op.features.types.RealNNcom.salesforce.op.cli.gen.templates.FeatureVectorTemplate→com.salesforce.op.features.types.Binarycom.salesforce.op.cli.gen.templates.MultiClassificationTemplate→com.salesforce.op.features.types.OPVectorcom.salesforce.op.cli.gen.templates.MultiClassificationTemplate→com.salesforce.op.features.types.RealNNcom.salesforce.op.cli.gen.templates.RegressionTemplate→com.salesforce.op.features.types.OPVectorcom.salesforce.op.cli.gen.templates.RegressionTemplate→com.salesforce.op.features.types.RealNN
- Direction
- com.salesforce.op.cli.gen.templates uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.cli.gen.templates, while a change to com.salesforce.op.cli.gen.templates can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.cli.gen.templates uses a module listed above it, which is the healthy direction.
18→7 com.salesforce.op.cli.gen.templates uses com.salesforce.op.cli.gen✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op.cli.gen.templates uses a type in com.salesforce.op.cli.gen.
- The types involved
com.salesforce.op.cli.gen.templates.SimpleProject→com.salesforce.op.cli.gen.FileInProjectcom.salesforce.op.cli.gen.templates.SimpleProject→com.salesforce.op.cli.gen.Opscom.salesforce.op.cli.gen.templates.SimpleProject→com.salesforce.op.cli.gen.ProblemSchemacom.salesforce.op.cli.gen.templates.SimpleProject→com.salesforce.op.cli.gen.ProjectGenerator
- Direction
- com.salesforce.op.cli.gen.templates uses com.salesforce.op.cli.gen, so a change to com.salesforce.op.cli.gen can break com.salesforce.op.cli.gen.templates, while a change to com.salesforce.op.cli.gen.templates can't break com.salesforce.op.cli.gen.
- Position
- Below the diagonal: com.salesforce.op.cli.gen.templates uses a module listed above it, which is the healthy direction.
18→11 com.salesforce.op.cli.gen.templates uses com.salesforce.op.cli✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.cli.gen.templates uses a type in com.salesforce.op.cli.
- The types involved
com.salesforce.op.cli.gen.templates.SimpleProject→com.salesforce.op.cli.GeneratorConfig
- Direction
- com.salesforce.op.cli.gen.templates uses com.salesforce.op.cli, so a change to com.salesforce.op.cli can break com.salesforce.op.cli.gen.templates, while a change to com.salesforce.op.cli.gen.templates can't break com.salesforce.op.cli.
- Position
- Below the diagonal: com.salesforce.op.cli.gen.templates uses a module listed above it, which is the healthy direction.
18→13 com.salesforce.op.cli.gen.templates uses com.salesforce.op.features✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op.cli.gen.templates uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.cli.gen.templates.BinaryClassificationTemplate→com.salesforce.op.features.Featurecom.salesforce.op.cli.gen.templates.FeatureVectorTemplate→com.salesforce.op.features.Featurecom.salesforce.op.cli.gen.templates.MultiClassificationTemplate→com.salesforce.op.features.Featurecom.salesforce.op.cli.gen.templates.RegressionTemplate→com.salesforce.op.features.Feature
- Direction
- com.salesforce.op.cli.gen.templates uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.cli.gen.templates, while a change to com.salesforce.op.cli.gen.templates can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.cli.gen.templates uses a module listed above it, which is the healthy direction.
19→1 com.salesforce.op.evaluators uses com.salesforce.op.features.types✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.evaluators uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.evaluators.OpHasPredictionCol→com.salesforce.op.features.types.Prediction
- Direction
- com.salesforce.op.evaluators uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.evaluators, while a change to com.salesforce.op.evaluators can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.evaluators uses a module listed above it, which is the healthy direction.
19→3 com.salesforce.op.evaluators uses com.salesforce.op.utils.json✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.evaluators uses a type in com.salesforce.op.utils.json.
- The types involved
com.salesforce.op.evaluators.EvaluationMetrics→com.salesforce.op.utils.json.JsonLike
- Direction
- com.salesforce.op.evaluators uses com.salesforce.op.utils.json, so a change to com.salesforce.op.utils.json can break com.salesforce.op.evaluators, while a change to com.salesforce.op.evaluators can't break com.salesforce.op.utils.json.
- Position
- Below the diagonal: com.salesforce.op.evaluators uses a module listed above it, which is the healthy direction.
19→13 com.salesforce.op.evaluators uses com.salesforce.op.features✕
- Connections
- 5 pairs of types, where a type in com.salesforce.op.evaluators uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.evaluators.OpHasLabelCol→com.salesforce.op.features.FeatureLikecom.salesforce.op.evaluators.OpHasPredictionCol→com.salesforce.op.features.FeatureLikecom.salesforce.op.evaluators.OpHasPredictionValueCol→com.salesforce.op.features.FeatureLikecom.salesforce.op.evaluators.OpHasProbabilityCol→com.salesforce.op.features.FeatureLikecom.salesforce.op.evaluators.OpHasRawPredictionCol→com.salesforce.op.features.FeatureLike
- Direction
- com.salesforce.op.evaluators uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.evaluators, while a change to com.salesforce.op.evaluators can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.evaluators uses a module listed above it, which is the healthy direction.
20→13 com.salesforce.op.stages.impl uses com.salesforce.op.features✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.stages.impl.CheckIsResponseValues→com.salesforce.op.features.TransientFeature
- Direction
- com.salesforce.op.stages.impl uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.stages.impl, while a change to com.salesforce.op.stages.impl can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.stages.impl uses a module listed above it, which is the healthy direction.
21→1 com.salesforce.op.stages.sparkwrappers.specific uses com.salesforce.op.features.types✕
- Connections
- 9 pairs of types, where a type in com.salesforce.op.stages.sparkwrappers.specific uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapper→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapper→com.salesforce.op.features.types.Predictioncom.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapper→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapperModel→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapperModel→com.salesforce.op.features.types.Predictioncom.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapperModel→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.sparkwrappers.specific.SparkModelConverter→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.sparkwrappers.specific.SparkModelConverter→com.salesforce.op.features.types.Predictioncom.salesforce.op.stages.sparkwrappers.specific.SparkModelConverter→com.salesforce.op.features.types.RealNN
- Direction
- com.salesforce.op.stages.sparkwrappers.specific uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.stages.sparkwrappers.specific, while a change to com.salesforce.op.stages.sparkwrappers.specific can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.stages.sparkwrappers.specific uses a module listed above it, which is the healthy direction.
21→12 com.salesforce.op.stages.sparkwrappers.specific uses com.salesforce.op.stages✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.sparkwrappers.specific uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapper→com.salesforce.op.stages.OpPipelineStage2
- Direction
- com.salesforce.op.stages.sparkwrappers.specific uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.stages.sparkwrappers.specific, while a change to com.salesforce.op.stages.sparkwrappers.specific can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.stages.sparkwrappers.specific uses a module listed above it, which is the healthy direction.
21→15 com.salesforce.op.stages.sparkwrappers.specific uses com.salesforce.op.stages.base.binary✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.sparkwrappers.specific uses a type in com.salesforce.op.stages.base.binary.
- The types involved
com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapperModel→com.salesforce.op.stages.base.binary.OpTransformer2com.salesforce.op.stages.sparkwrappers.specific.SparkModelConverter→com.salesforce.op.stages.base.binary.OpTransformer2
- Direction
- com.salesforce.op.stages.sparkwrappers.specific uses com.salesforce.op.stages.base.binary, so a change to com.salesforce.op.stages.base.binary can break com.salesforce.op.stages.sparkwrappers.specific, while a change to com.salesforce.op.stages.sparkwrappers.specific can't break com.salesforce.op.stages.base.binary.
- Position
- Below the diagonal: com.salesforce.op.stages.sparkwrappers.specific uses a module listed above it, which is the healthy direction.
21→17 com.salesforce.op.stages.sparkwrappers.specific uses com.salesforce.op.stages.sparkwrappers.generic✕
- Connections
- 5 pairs of types, where a type in com.salesforce.op.stages.sparkwrappers.specific uses a type in com.salesforce.op.stages.sparkwrappers.generic.
- The types involved
com.salesforce.op.stages.sparkwrappers.specific.OpBinaryEstimatorWrapper→com.salesforce.op.stages.sparkwrappers.generic.SwBinaryEstimatorcom.salesforce.op.stages.sparkwrappers.specific.OpEstimatorWrapper→com.salesforce.op.stages.sparkwrappers.generic.SwUnaryEstimatorcom.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapper→com.salesforce.op.stages.sparkwrappers.generic.SparkWrapperParamscom.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapperModel→com.salesforce.op.stages.sparkwrappers.generic.SparkWrapperParamscom.salesforce.op.stages.sparkwrappers.specific.OpTransformerWrapper→com.salesforce.op.stages.sparkwrappers.generic.SwUnaryTransformer
- Direction
- com.salesforce.op.stages.sparkwrappers.specific uses com.salesforce.op.stages.sparkwrappers.generic, so a change to com.salesforce.op.stages.sparkwrappers.generic can break com.salesforce.op.stages.sparkwrappers.specific, while a change to com.salesforce.op.stages.sparkwrappers.specific can't break com.salesforce.op.stages.sparkwrappers.generic.
- Position
- Below the diagonal: com.salesforce.op.stages.sparkwrappers.specific uses a module listed above it, which is the healthy direction.
22→19 com.salesforce.op.stages.impl.tuning uses com.salesforce.op.evaluators✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.stages.impl.tuning uses a type in com.salesforce.op.evaluators.
- The types involved
com.salesforce.op.stages.impl.tuning.OpCrossValidation→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.stages.impl.tuning.OpTrainValidationSplit→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.stages.impl.tuning.OpValidator→com.salesforce.op.evaluators.OpEvaluatorBase
- Direction
- com.salesforce.op.stages.impl.tuning uses com.salesforce.op.evaluators, so a change to com.salesforce.op.evaluators can break com.salesforce.op.stages.impl.tuning, while a change to com.salesforce.op.stages.impl.tuning can't break com.salesforce.op.evaluators.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.tuning uses a module listed above it, which is the healthy direction.
22→20 com.salesforce.op.stages.impl.tuning uses com.salesforce.op.stages.impl✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.tuning uses a type in com.salesforce.op.stages.impl.
- The types involved
com.salesforce.op.stages.impl.tuning.SplitterSummary→com.salesforce.op.stages.impl.MetadataLike
- Direction
- com.salesforce.op.stages.impl.tuning uses com.salesforce.op.stages.impl, so a change to com.salesforce.op.stages.impl can break com.salesforce.op.stages.impl.tuning, while a change to com.salesforce.op.stages.impl.tuning can't break com.salesforce.op.stages.impl.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.tuning uses a module listed above it, which is the healthy direction.
22→23 com.salesforce.op.stages.impl.tuning uses com.salesforce.op.stages.impl.selector part of a loop✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.tuning uses a type in com.salesforce.op.stages.impl.selector.
- The types involved
com.salesforce.op.stages.impl.tuning.BestEstimator→com.salesforce.op.stages.impl.selector.ModelEvaluationcom.salesforce.op.stages.impl.tuning.OpValidator→com.salesforce.op.stages.impl.selector.ModelEvaluation
- Direction
- com.salesforce.op.stages.impl.tuning uses com.salesforce.op.stages.impl.selector, so a change to com.salesforce.op.stages.impl.selector can break com.salesforce.op.stages.impl.tuning, while a change to com.salesforce.op.stages.impl.tuning can't break com.salesforce.op.stages.impl.selector.
- 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.
23→1 com.salesforce.op.stages.impl.selector uses com.salesforce.op.features.types✕
- Connections
- 9 pairs of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.features.types.Predictioncom.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.impl.selector.SelectedCombinerModel→com.salesforce.op.features.types.Predictioncom.salesforce.op.stages.impl.selector.SelectedCombinerModel→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.impl.selector.SelectedModel→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.selector.SelectedModel→com.salesforce.op.features.types.Predictioncom.salesforce.op.stages.impl.selector.SelectedModel→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.impl.selector.SelectedModelCombiner→com.salesforce.op.features.types.Prediction
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.selector uses a module listed above it, which is the healthy direction.
23→12 com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.stages.OpPipelineStage2com.salesforce.op.stages.impl.selector.SelectedModelCombiner→com.salesforce.op.stages.OpPipelineStage3
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.selector uses a module listed above it, which is the healthy direction.
23→13 com.salesforce.op.stages.impl.selector uses com.salesforce.op.features✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.stages.impl.selector.SelectedModelCombiner→com.salesforce.op.features.TransientFeature
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.selector uses a module listed above it, which is the healthy direction.
23→15 com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.base.binary✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.stages.base.binary.
- The types involved
com.salesforce.op.stages.impl.selector.SelectedModel→com.salesforce.op.stages.base.binary.OpTransformer2
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.base.binary, so a change to com.salesforce.op.stages.base.binary can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.stages.base.binary.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.selector uses a module listed above it, which is the healthy direction.
23→17 com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.sparkwrappers.generic✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.stages.sparkwrappers.generic.
- The types involved
com.salesforce.op.stages.impl.selector.SelectedModel→com.salesforce.op.stages.sparkwrappers.generic.SparkWrapperParams
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.sparkwrappers.generic, so a change to com.salesforce.op.stages.sparkwrappers.generic can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.stages.sparkwrappers.generic.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.selector uses a module listed above it, which is the healthy direction.
23→19 com.salesforce.op.stages.impl.selector uses com.salesforce.op.evaluators✕
- Connections
- 13 pairs of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.evaluators.
- The types involved
com.salesforce.op.stages.impl.selector.HasEval→com.salesforce.op.evaluators.EvaluationMetricscom.salesforce.op.stages.impl.selector.HasEval→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.stages.impl.selector.ModelEvaluation→com.salesforce.op.evaluators.EvaluationMetricscom.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.stages.impl.selector.ModelSelectorFactory→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.stages.impl.selector.ModelSelectorSummary→com.salesforce.op.evaluators.EvalMetriccom.salesforce.op.stages.impl.selector.ModelSelectorSummary→com.salesforce.op.evaluators.EvaluationMetricscom.salesforce.op.stages.impl.selector.SelectedCombinerModel→com.salesforce.op.evaluators.EvalMetriccom.salesforce.op.stages.impl.selector.SelectedCombinerModel→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.stages.impl.selector.SelectedModel→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.stages.impl.selector.SelectedModelCombiner→com.salesforce.op.evaluators.EvalMetriccom.salesforce.op.stages.impl.selector.SelectedModelCombiner→com.salesforce.op.evaluators.EvaluationMetricscom.salesforce.op.stages.impl.selector.SelectedModelCombiner→com.salesforce.op.evaluators.OpEvaluatorBase
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.evaluators, so a change to com.salesforce.op.evaluators can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.evaluators.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.selector uses a module listed above it, which is the healthy direction.
23→20 com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.impl✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.stages.impl.
- The types involved
com.salesforce.op.stages.impl.selector.ModelEvaluation→com.salesforce.op.stages.impl.MetadataLikecom.salesforce.op.stages.impl.selector.ModelSelectorFactory→com.salesforce.op.stages.impl.ModelsToTrycom.salesforce.op.stages.impl.selector.ModelSelectorSummary→com.salesforce.op.stages.impl.MetadataLike
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.impl, so a change to com.salesforce.op.stages.impl can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.stages.impl.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.selector uses a module listed above it, which is the healthy direction.
23→22 com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.impl.tuning✕
- Connections
- 7 pairs of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.stages.impl.tuning.
- The types involved
com.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.stages.impl.tuning.BestEstimatorcom.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.stages.impl.tuning.OpValidatorcom.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.stages.impl.tuning.PrevalidationValcom.salesforce.op.stages.impl.selector.ModelSelector→com.salesforce.op.stages.impl.tuning.Splittercom.salesforce.op.stages.impl.selector.ModelSelectorFactory→com.salesforce.op.stages.impl.tuning.OpValidatorcom.salesforce.op.stages.impl.selector.ModelSelectorFactory→com.salesforce.op.stages.impl.tuning.Splittercom.salesforce.op.stages.impl.selector.ModelSelectorSummary→com.salesforce.op.stages.impl.tuning.SplitterSummary
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.impl.tuning, so a change to com.salesforce.op.stages.impl.tuning can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.stages.impl.tuning.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.selector uses a module listed above it, which is the healthy direction.
23→27 com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.impl.feature part of a loop✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.selector uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.stages.impl.selector.SelectedCombinerModel→com.salesforce.op.stages.impl.feature.CombinationStrategycom.salesforce.op.stages.impl.selector.SelectedCombinerParams→com.salesforce.op.stages.impl.feature.CombinationStrategy
- Direction
- com.salesforce.op.stages.impl.selector uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.stages.impl.selector, while a change to com.salesforce.op.stages.impl.selector can't break com.salesforce.op.stages.impl.feature.
- 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→5 com.salesforce.op.stages.impl.classification uses ml.dmlc.xgboost4j.scala.spark✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.classification uses a type in ml.dmlc.xgboost4j.scala.spark.
- The types involved
com.salesforce.op.stages.impl.classification.OpXGBoostClassifier→ml.dmlc.xgboost4j.scala.spark.OpXGBoostClassifierParams
- Direction
- com.salesforce.op.stages.impl.classification uses ml.dmlc.xgboost4j.scala.spark, so a change to ml.dmlc.xgboost4j.scala.spark can break com.salesforce.op.stages.impl.classification, while a change to com.salesforce.op.stages.impl.classification can't break ml.dmlc.xgboost4j.scala.spark.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.classification uses a module listed above it, which is the healthy direction.
24→19 com.salesforce.op.stages.impl.classification uses com.salesforce.op.evaluators✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.classification uses a type in com.salesforce.op.evaluators.
- The types involved
com.salesforce.op.stages.impl.classification.BinaryClassificationModelSelector→com.salesforce.op.evaluators.OpBinaryClassificationEvaluatorBasecom.salesforce.op.stages.impl.classification.MultiClassificationModelSelector→com.salesforce.op.evaluators.OpMultiClassificationEvaluatorBase
- Direction
- com.salesforce.op.stages.impl.classification uses com.salesforce.op.evaluators, so a change to com.salesforce.op.evaluators can break com.salesforce.op.stages.impl.classification, while a change to com.salesforce.op.stages.impl.classification can't break com.salesforce.op.evaluators.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.classification uses a module listed above it, which is the healthy direction.
24→20 com.salesforce.op.stages.impl.classification uses com.salesforce.op.stages.impl✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.classification uses a type in com.salesforce.op.stages.impl.
- The types involved
com.salesforce.op.stages.impl.classification.BinaryClassificationModelsToTry→com.salesforce.op.stages.impl.ModelsToTrycom.salesforce.op.stages.impl.classification.MultiClassClassificationModelsToTry→com.salesforce.op.stages.impl.ModelsToTry
- Direction
- com.salesforce.op.stages.impl.classification uses com.salesforce.op.stages.impl, so a change to com.salesforce.op.stages.impl can break com.salesforce.op.stages.impl.classification, while a change to com.salesforce.op.stages.impl.classification can't break com.salesforce.op.stages.impl.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.classification uses a module listed above it, which is the healthy direction.
24→21 com.salesforce.op.stages.impl.classification uses com.salesforce.op.stages.sparkwrappers.specific✕
- Connections
- 16 pairs of types, where a type in com.salesforce.op.stages.impl.classification uses a type in com.salesforce.op.stages.sparkwrappers.specific.
- The types involved
com.salesforce.op.stages.impl.classification.OpDecisionTreeClassificationModel→com.salesforce.op.stages.sparkwrappers.specific.OpProbabilisticClassifierModelcom.salesforce.op.stages.impl.classification.OpDecisionTreeClassifier→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.classification.OpGBTClassificationModel→com.salesforce.op.stages.sparkwrappers.specific.OpProbabilisticClassifierModelcom.salesforce.op.stages.impl.classification.OpGBTClassifier→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.classification.OpLinearSVC→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.classification.OpLinearSVCModel→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapperModelcom.salesforce.op.stages.impl.classification.OpLogisticRegression→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.classification.OpLogisticRegressionModel→com.salesforce.op.stages.sparkwrappers.specific.OpProbabilisticClassifierModelcom.salesforce.op.stages.impl.classification.OpMultilayerPerceptronClassificationModel→com.salesforce.op.stages.sparkwrappers.specific.OpProbabilisticClassifierModelcom.salesforce.op.stages.impl.classification.OpMultilayerPerceptronClassifier→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.classification.OpNaiveBayes→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.classification.OpNaiveBayesModel→com.salesforce.op.stages.sparkwrappers.specific.OpProbabilisticClassifierModelcom.salesforce.op.stages.impl.classification.OpRandomForestClassificationModel→com.salesforce.op.stages.sparkwrappers.specific.OpProbabilisticClassifierModelcom.salesforce.op.stages.impl.classification.OpRandomForestClassifier→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.classification.OpXGBoostClassificationModel→com.salesforce.op.stages.sparkwrappers.specific.OpProbabilisticClassifierModelcom.salesforce.op.stages.impl.classification.OpXGBoostClassifier→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapper
- Direction
- com.salesforce.op.stages.impl.classification uses com.salesforce.op.stages.sparkwrappers.specific, so a change to com.salesforce.op.stages.sparkwrappers.specific can break com.salesforce.op.stages.impl.classification, while a change to com.salesforce.op.stages.impl.classification can't break com.salesforce.op.stages.sparkwrappers.specific.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.classification uses a module listed above it, which is the healthy direction.
24→22 com.salesforce.op.stages.impl.classification uses com.salesforce.op.stages.impl.tuning✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.classification uses a type in com.salesforce.op.stages.impl.tuning.
- The types involved
com.salesforce.op.stages.impl.classification.BinaryClassificationModelSelector→com.salesforce.op.stages.impl.tuning.Splittercom.salesforce.op.stages.impl.classification.MultiClassificationModelSelector→com.salesforce.op.stages.impl.tuning.DataCutter
- Direction
- com.salesforce.op.stages.impl.classification uses com.salesforce.op.stages.impl.tuning, so a change to com.salesforce.op.stages.impl.tuning can break com.salesforce.op.stages.impl.classification, while a change to com.salesforce.op.stages.impl.classification can't break com.salesforce.op.stages.impl.tuning.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.classification uses a module listed above it, which is the healthy direction.
24→23 com.salesforce.op.stages.impl.classification uses com.salesforce.op.stages.impl.selector✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op.stages.impl.classification uses a type in com.salesforce.op.stages.impl.selector.
- The types involved
com.salesforce.op.stages.impl.classification.BinaryClassificationModelSelector→com.salesforce.op.stages.impl.selector.ModelSelectorcom.salesforce.op.stages.impl.classification.BinaryClassificationModelSelector→com.salesforce.op.stages.impl.selector.ModelSelectorFactorycom.salesforce.op.stages.impl.classification.MultiClassificationModelSelector→com.salesforce.op.stages.impl.selector.ModelSelectorcom.salesforce.op.stages.impl.classification.MultiClassificationModelSelector→com.salesforce.op.stages.impl.selector.ModelSelectorFactory
- Direction
- com.salesforce.op.stages.impl.classification uses com.salesforce.op.stages.impl.selector, so a change to com.salesforce.op.stages.impl.selector can break com.salesforce.op.stages.impl.classification, while a change to com.salesforce.op.stages.impl.classification can't break com.salesforce.op.stages.impl.selector.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.classification uses a module listed above it, which is the healthy direction.
25→5 com.salesforce.op.stages.impl.regression uses ml.dmlc.xgboost4j.scala.spark✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.regression uses a type in ml.dmlc.xgboost4j.scala.spark.
- The types involved
com.salesforce.op.stages.impl.regression.OpXGBoostRegressor→ml.dmlc.xgboost4j.scala.spark.OpXGBoostRegressorParams
- Direction
- com.salesforce.op.stages.impl.regression uses ml.dmlc.xgboost4j.scala.spark, so a change to ml.dmlc.xgboost4j.scala.spark can break com.salesforce.op.stages.impl.regression, while a change to com.salesforce.op.stages.impl.regression can't break ml.dmlc.xgboost4j.scala.spark.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.regression uses a module listed above it, which is the healthy direction.
25→19 com.salesforce.op.stages.impl.regression uses com.salesforce.op.evaluators✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.regression uses a type in com.salesforce.op.evaluators.
- The types involved
com.salesforce.op.stages.impl.regression.RegressionModelSelector→com.salesforce.op.evaluators.OpRegressionEvaluatorBase
- Direction
- com.salesforce.op.stages.impl.regression uses com.salesforce.op.evaluators, so a change to com.salesforce.op.evaluators can break com.salesforce.op.stages.impl.regression, while a change to com.salesforce.op.stages.impl.regression can't break com.salesforce.op.evaluators.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.regression uses a module listed above it, which is the healthy direction.
25→20 com.salesforce.op.stages.impl.regression uses com.salesforce.op.stages.impl✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.regression uses a type in com.salesforce.op.stages.impl.
- The types involved
com.salesforce.op.stages.impl.regression.RegressionModelsToTry→com.salesforce.op.stages.impl.ModelsToTry
- Direction
- com.salesforce.op.stages.impl.regression uses com.salesforce.op.stages.impl, so a change to com.salesforce.op.stages.impl can break com.salesforce.op.stages.impl.regression, while a change to com.salesforce.op.stages.impl.regression can't break com.salesforce.op.stages.impl.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.regression uses a module listed above it, which is the healthy direction.
25→21 com.salesforce.op.stages.impl.regression uses com.salesforce.op.stages.sparkwrappers.specific✕
- Connections
- 13 pairs of types, where a type in com.salesforce.op.stages.impl.regression uses a type in com.salesforce.op.stages.sparkwrappers.specific.
- The types involved
com.salesforce.op.stages.impl.regression.IsotonicRegressionCalibrator→com.salesforce.op.stages.sparkwrappers.specific.OpBinaryEstimatorWrappercom.salesforce.op.stages.impl.regression.OpDecisionTreeRegressionModel→com.salesforce.op.stages.sparkwrappers.specific.OpPredictionModelcom.salesforce.op.stages.impl.regression.OpDecisionTreeRegressor→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.regression.OpGBTRegressionModel→com.salesforce.op.stages.sparkwrappers.specific.OpPredictionModelcom.salesforce.op.stages.impl.regression.OpGBTRegressor→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.regression.OpGeneralizedLinearRegression→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.regression.OpGeneralizedLinearRegressionModel→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapperModelcom.salesforce.op.stages.impl.regression.OpLinearRegression→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.regression.OpLinearRegressionModel→com.salesforce.op.stages.sparkwrappers.specific.OpPredictionModelcom.salesforce.op.stages.impl.regression.OpRandomForestRegressionModel→com.salesforce.op.stages.sparkwrappers.specific.OpPredictionModelcom.salesforce.op.stages.impl.regression.OpRandomForestRegressor→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrappercom.salesforce.op.stages.impl.regression.OpXGBoostRegressionModel→com.salesforce.op.stages.sparkwrappers.specific.OpPredictionModelcom.salesforce.op.stages.impl.regression.OpXGBoostRegressor→com.salesforce.op.stages.sparkwrappers.specific.OpPredictorWrapper
- Direction
- com.salesforce.op.stages.impl.regression uses com.salesforce.op.stages.sparkwrappers.specific, so a change to com.salesforce.op.stages.sparkwrappers.specific can break com.salesforce.op.stages.impl.regression, while a change to com.salesforce.op.stages.impl.regression can't break com.salesforce.op.stages.sparkwrappers.specific.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.regression uses a module listed above it, which is the healthy direction.
25→22 com.salesforce.op.stages.impl.regression uses com.salesforce.op.stages.impl.tuning✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.regression uses a type in com.salesforce.op.stages.impl.tuning.
- The types involved
com.salesforce.op.stages.impl.regression.RegressionModelSelector→com.salesforce.op.stages.impl.tuning.DataSplitter
- Direction
- com.salesforce.op.stages.impl.regression uses com.salesforce.op.stages.impl.tuning, so a change to com.salesforce.op.stages.impl.tuning can break com.salesforce.op.stages.impl.regression, while a change to com.salesforce.op.stages.impl.regression can't break com.salesforce.op.stages.impl.tuning.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.regression uses a module listed above it, which is the healthy direction.
25→23 com.salesforce.op.stages.impl.regression uses com.salesforce.op.stages.impl.selector✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.regression uses a type in com.salesforce.op.stages.impl.selector.
- The types involved
com.salesforce.op.stages.impl.regression.RegressionModelSelector→com.salesforce.op.stages.impl.selector.ModelSelectorcom.salesforce.op.stages.impl.regression.RegressionModelSelector→com.salesforce.op.stages.impl.selector.ModelSelectorFactory
- Direction
- com.salesforce.op.stages.impl.regression uses com.salesforce.op.stages.impl.selector, so a change to com.salesforce.op.stages.impl.selector can break com.salesforce.op.stages.impl.regression, while a change to com.salesforce.op.stages.impl.regression can't break com.salesforce.op.stages.impl.selector.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.regression uses a module listed above it, which is the healthy direction.
26→1 com.salesforce.op.dsl.RichVectorFeature uses com.salesforce.op.features.types✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.dsl.RichVectorFeature uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.dsl.RichVectorFeature.RichVectorFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichVectorFeature.RichVectorFeature→com.salesforce.op.features.types.Predictioncom.salesforce.op.dsl.RichVectorFeature.RichVectorFeature→com.salesforce.op.features.types.RealNN
- Direction
- com.salesforce.op.dsl.RichVectorFeature uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.dsl.RichVectorFeature, while a change to com.salesforce.op.dsl.RichVectorFeature can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichVectorFeature uses a module listed above it, which is the healthy direction.
26→9 com.salesforce.op.dsl.RichVectorFeature uses com.salesforce.op.utils.spark✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.dsl.RichVectorFeature uses a type in com.salesforce.op.utils.spark.
- The types involved
com.salesforce.op.dsl.RichVectorFeature.RichVectorFeature→com.salesforce.op.utils.spark.OpVectorColumnMetadata
- Direction
- com.salesforce.op.dsl.RichVectorFeature uses com.salesforce.op.utils.spark, so a change to com.salesforce.op.utils.spark can break com.salesforce.op.dsl.RichVectorFeature, while a change to com.salesforce.op.dsl.RichVectorFeature can't break com.salesforce.op.utils.spark.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichVectorFeature uses a module listed above it, which is the healthy direction.
26→13 com.salesforce.op.dsl.RichVectorFeature uses com.salesforce.op.features✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.dsl.RichVectorFeature uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.dsl.RichVectorFeature.RichVectorFeature→com.salesforce.op.features.FeatureLike
- Direction
- com.salesforce.op.dsl.RichVectorFeature uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.dsl.RichVectorFeature, while a change to com.salesforce.op.dsl.RichVectorFeature can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichVectorFeature uses a module listed above it, which is the healthy direction.
26→24 com.salesforce.op.dsl.RichVectorFeature uses com.salesforce.op.stages.impl.classification✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.dsl.RichVectorFeature uses a type in com.salesforce.op.stages.impl.classification.
- The types involved
com.salesforce.op.dsl.RichVectorFeature.RichVectorFeature→com.salesforce.op.stages.impl.classification.Impurity
- Direction
- com.salesforce.op.dsl.RichVectorFeature uses com.salesforce.op.stages.impl.classification, so a change to com.salesforce.op.stages.impl.classification can break com.salesforce.op.dsl.RichVectorFeature, while a change to com.salesforce.op.dsl.RichVectorFeature can't break com.salesforce.op.stages.impl.classification.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichVectorFeature uses a module listed above it, which is the healthy direction.
27→1 com.salesforce.op.stages.impl.feature uses com.salesforce.op.features.types✕
- Connections
- 59 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.features.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.salesforce.op.stages.impl.feature.DateListVectorizer→com.salesforce.op.features.types.DateTimecom.salesforce.op.stages.impl.feature.DateMapToUnitCircleVectorizer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.DateMapVectorizer→com.salesforce.op.features.types.DateTimecom.salesforce.op.stages.impl.feature.DateMapVectorizerModel→com.salesforce.op.features.types.DateMapcom.salesforce.op.stages.impl.feature.DateMapVectorizerModel→com.salesforce.op.features.types.DateTimecom.salesforce.op.stages.impl.feature.DecisionTreeNumericBucketizer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.DecisionTreeNumericBucketizer→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.impl.feature.DecisionTreeNumericMapBucketizer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.DecisionTreeNumericMapBucketizer→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.impl.feature.DropIndicesByTransformer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.FillMissingWithMean→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.impl.feature.GeolocationMapVectorizer→com.salesforce.op.features.types.Geolocationcom.salesforce.op.stages.impl.feature.GeolocationMapVectorizer→com.salesforce.op.features.types.GeolocationMapcom.salesforce.op.stages.impl.feature.GeolocationMapVectorizer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.GeolocationVectorizer→com.salesforce.op.features.types.Geolocationcom.salesforce.op.stages.impl.feature.GeolocationVectorizer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.HashingFun→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.IntegralVectorizer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.MapHashingFun→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.MapHashingFun→com.salesforce.op.features.types.TextListcom.salesforce.op.stages.impl.feature.MimeTypeDetector→com.salesforce.op.features.types.Base64com.salesforce.op.stages.impl.feature.MimeTypeMapDetector→com.salesforce.op.features.types.Base64Mapcom.salesforce.op.stages.impl.feature.MultiPickListMapVectorizer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.feature.OPCollectionTransformer→com.salesforce.op.features.types.FeatureTypeFactorycom.salesforce.op.stages.impl.feature.OPCollectionTransformer→com.salesforce.op.features.types.FeatureTypeSparkConverter
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→3 com.salesforce.op.stages.impl.feature uses com.salesforce.op.utils.json✕
- Connections
- 6 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.utils.json.
- The types involved
com.salesforce.op.stages.impl.feature.ScalingArgs→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.stages.impl.feature.SmartTextFeatureInfo→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.stages.impl.feature.SmartTextMapVectorizerModelArgs→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.stages.impl.feature.SmartTextVectorizerModelArgs→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.stages.impl.feature.TextMapStats→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.stages.impl.feature.TextStats→com.salesforce.op.utils.json.JsonLike
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.utils.json, so a change to com.salesforce.op.utils.json can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.utils.json.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→4 com.salesforce.op.stages.impl.feature uses com.salesforce.op.utils.text✕
- Connections
- 10 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.utils.text.
- The types involved
com.salesforce.op.stages.impl.feature.LangDetector→com.salesforce.op.utils.text.LanguageDetectorcom.salesforce.op.stages.impl.feature.LanguageDetectionParams→com.salesforce.op.utils.text.Languagecom.salesforce.op.stages.impl.feature.NameEntityRecognizer→com.salesforce.op.utils.text.LanguageDetectorcom.salesforce.op.stages.impl.feature.NameEntityRecognizer→com.salesforce.op.utils.text.NameEntityTaggercom.salesforce.op.stages.impl.feature.NameEntityRecognizer→com.salesforce.op.utils.text.SentenceSplittercom.salesforce.op.stages.impl.feature.NameEntityRecognizer→com.salesforce.op.utils.text.TextAnalyzercom.salesforce.op.stages.impl.feature.TextTokenizer→com.salesforce.op.utils.text.LanguageDetectorcom.salesforce.op.stages.impl.feature.TextTokenizer→com.salesforce.op.utils.text.TextAnalyzercom.salesforce.op.stages.impl.feature.TextTokenizerParams→com.salesforce.op.utils.text.LanguageDetectorcom.salesforce.op.stages.impl.feature.TextTokenizerParams→com.salesforce.op.utils.text.TextAnalyzer
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.utils.text, so a change to com.salesforce.op.utils.text can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.utils.text.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→6 com.salesforce.op.stages.impl.feature uses com.salesforce.op.aggregators✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.aggregators.
- The types involved
com.salesforce.op.stages.impl.feature.GeolocationVectorizer→com.salesforce.op.aggregators.GeolocationFunctions
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.aggregators, so a change to com.salesforce.op.aggregators can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.aggregators.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→8 com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.impl.feature.TextTokenizer✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.stages.impl.feature.TextTokenizer.
- The types involved
com.salesforce.op.stages.impl.feature.TextTokenizerParams→com.salesforce.op.stages.impl.feature.TextTokenizer.TextTokenizerResult
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.impl.feature.TextTokenizer, so a change to com.salesforce.op.stages.impl.feature.TextTokenizer can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.stages.impl.feature.TextTokenizer.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→9 com.salesforce.op.stages.impl.feature uses com.salesforce.op.utils.spark✕
- Connections
- 17 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.utils.spark.
- The types involved
com.salesforce.op.stages.impl.feature.DateMapToUnitCircleVectorizer→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.DropIndicesByTransformer→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.stages.impl.feature.GeolocationMapVectorizer→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.GeolocationVectorizer→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.HashingFun→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.stages.impl.feature.HashingFun→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.MapHashingFun→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.stages.impl.feature.MapStringPivotHelper→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.stages.impl.feature.MapStringPivotHelper→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.MapVectorizerFuns→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.NumericBucketizerMetadata→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.stages.impl.feature.NumericBucketizerMetadata→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.OneHotFun→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.stages.impl.feature.OneHotFun→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.SmartTextMapVectorizer→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.SmartTextVectorizer→com.salesforce.op.utils.spark.OpVectorMetadatacom.salesforce.op.stages.impl.feature.VectorizerDefaults→com.salesforce.op.utils.spark.OpVectorMetadata
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.utils.spark, so a change to com.salesforce.op.utils.spark can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.utils.spark.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→10 com.salesforce.op.stages.impl.feature uses com.salesforce.op.utils.stages✕
- Connections
- 8 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.utils.stages.
- The types involved
com.salesforce.op.stages.impl.feature.HumanNameDetector→com.salesforce.op.utils.stages.NameDetectFuncom.salesforce.op.stages.impl.feature.HumanNameDetectorMetadata→com.salesforce.op.utils.stages.GenderStatscom.salesforce.op.stages.impl.feature.HumanNameDetectorModel→com.salesforce.op.utils.stages.NameDetectFuncom.salesforce.op.stages.impl.feature.SmartTextMapVectorizer→com.salesforce.op.utils.stages.NameDetectFuncom.salesforce.op.stages.impl.feature.SmartTextMapVectorizer→com.salesforce.op.utils.stages.NameDetectStatscom.salesforce.op.stages.impl.feature.SmartTextVectorizer→com.salesforce.op.utils.stages.NameDetectFuncom.salesforce.op.stages.impl.feature.SmartTextVectorizer→com.salesforce.op.utils.stages.NameDetectStatscom.salesforce.op.stages.impl.feature.TextMapStats→com.salesforce.op.utils.stages.NameDetectStats
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.utils.stages, so a change to com.salesforce.op.utils.stages can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.utils.stages.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→12 com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages✕
- Connections
- 6 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.stages.impl.feature.DecisionTreeNumericBucketizer→com.salesforce.op.stages.AllowLabelAsInputcom.salesforce.op.stages.impl.feature.DecisionTreeNumericBucketizerModel→com.salesforce.op.stages.AllowLabelAsInputcom.salesforce.op.stages.impl.feature.DecisionTreeNumericMapBucketizer→com.salesforce.op.stages.AllowLabelAsInputcom.salesforce.op.stages.impl.feature.DecisionTreeNumericMapBucketizerModel→com.salesforce.op.stages.AllowLabelAsInputcom.salesforce.op.stages.impl.feature.TextTokenizerReaderWriter→com.salesforce.op.stages.OpPipelineStageReaderWritercom.salesforce.op.stages.impl.feature.VectorizerDefaults→com.salesforce.op.stages.OpPipelineStageBase
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→13 com.salesforce.op.stages.impl.feature uses com.salesforce.op.features✕
- Connections
- 8 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.stages.impl.feature.HashingFun→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.impl.feature.MapHashingFun→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.impl.feature.MapStringPivotHelper→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.impl.feature.NumericBucketizerMetadata→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.impl.feature.OneHotFun→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.impl.feature.SmartTextVectorizerModel→com.salesforce.op.features.TransientFeaturecom.salesforce.op.stages.impl.feature.Transmogrifier→com.salesforce.op.features.FeatureLikecom.salesforce.op.stages.impl.feature.Transmogrifier→com.salesforce.op.features.TransientFeature
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→15 com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.base.binary✕
- Connections
- 18 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.stages.base.binary.
- The types involved
com.salesforce.op.stages.impl.feature.AddTransformer→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.DecisionTreeNumericBucketizer→com.salesforce.op.stages.base.binary.BinaryEstimatorcom.salesforce.op.stages.impl.feature.DecisionTreeNumericBucketizer→com.salesforce.op.stages.base.binary.BinaryModelcom.salesforce.op.stages.impl.feature.DecisionTreeNumericBucketizerModel→com.salesforce.op.stages.base.binary.BinaryModelcom.salesforce.op.stages.impl.feature.DecisionTreeNumericMapBucketizer→com.salesforce.op.stages.base.binary.BinaryEstimatorcom.salesforce.op.stages.impl.feature.DecisionTreeNumericMapBucketizer→com.salesforce.op.stages.base.binary.BinaryModelcom.salesforce.op.stages.impl.feature.DecisionTreeNumericMapBucketizerModel→com.salesforce.op.stages.base.binary.BinaryModelcom.salesforce.op.stages.impl.feature.DescalerTransformer→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.DivideTransformer→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.IsValidPhoneNumber→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.JaccardSimilarity→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.MultiLabelJoiner→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.MultiplyTransformer→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.NGramSimilarity→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.ParsePhoneNumber→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.PredictionDescaler→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.SubstringTransformer→com.salesforce.op.stages.base.binary.BinaryTransformercom.salesforce.op.stages.impl.feature.SubtractTransformer→com.salesforce.op.stages.base.binary.BinaryTransformer
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.base.binary, so a change to com.salesforce.op.stages.base.binary can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.stages.base.binary.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→16 com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.base.unary✕
- Connections
- 52 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.stages.base.unary. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.salesforce.op.stages.impl.feature.AbsoluteValueTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.AliasTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.CeilTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.DropIndicesByTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.ExistsTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.ExpTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.FillMissingWithMean→com.salesforce.op.stages.base.unary.UnaryEstimatorcom.salesforce.op.stages.impl.feature.FillMissingWithMean→com.salesforce.op.stages.base.unary.UnaryModelcom.salesforce.op.stages.impl.feature.FillMissingWithMeanModel→com.salesforce.op.stages.base.unary.UnaryModelcom.salesforce.op.stages.impl.feature.FilterMap→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.FilterTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.FloorTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.HumanNameDetector→com.salesforce.op.stages.base.unary.UnaryEstimatorcom.salesforce.op.stages.impl.feature.HumanNameDetectorModel→com.salesforce.op.stages.base.unary.UnaryModelcom.salesforce.op.stages.impl.feature.IsValidPhoneDefaultCountry→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.IsValidPhoneMapDefaultCountry→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.LangDetector→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.LogTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.MimeTypeDetector→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.MimeTypeMapDetector→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.NameEntityRecognizer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.NumericBucketizer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.OPCollectionTransformer→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.OpIndexToStringNoFilter→com.salesforce.op.stages.base.unary.UnaryTransformercom.salesforce.op.stages.impl.feature.OpScalarStandardScaler→com.salesforce.op.stages.base.unary.UnaryEstimator
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.base.unary, so a change to com.salesforce.op.stages.base.unary can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.stages.base.unary.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→17 com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.sparkwrappers.generic✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.stages.sparkwrappers.generic.
- The types involved
com.salesforce.op.stages.impl.feature.OpCountVectorizer→com.salesforce.op.stages.sparkwrappers.generic.SwUnaryModel
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.sparkwrappers.generic, so a change to com.salesforce.op.stages.sparkwrappers.generic can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.stages.sparkwrappers.generic.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→20 com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.impl✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.stages.impl.
- The types involved
com.salesforce.op.stages.impl.feature.HumanNameDetectorMetadata→com.salesforce.op.stages.impl.MetadataLike
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.impl, so a change to com.salesforce.op.stages.impl can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.stages.impl.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→21 com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.sparkwrappers.specific✕
- Connections
- 8 pairs of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.stages.sparkwrappers.specific.
- The types involved
com.salesforce.op.stages.impl.feature.OpCountVectorizer→com.salesforce.op.stages.sparkwrappers.specific.OpEstimatorWrappercom.salesforce.op.stages.impl.feature.OpHashingTF→com.salesforce.op.stages.sparkwrappers.specific.OpTransformerWrappercom.salesforce.op.stages.impl.feature.OpIndexToString→com.salesforce.op.stages.sparkwrappers.specific.OpTransformerWrappercom.salesforce.op.stages.impl.feature.OpLDA→com.salesforce.op.stages.sparkwrappers.specific.OpEstimatorWrappercom.salesforce.op.stages.impl.feature.OpNGram→com.salesforce.op.stages.sparkwrappers.specific.OpTransformerWrappercom.salesforce.op.stages.impl.feature.OpStopWordsRemover→com.salesforce.op.stages.sparkwrappers.specific.OpTransformerWrappercom.salesforce.op.stages.impl.feature.OpStringIndexer→com.salesforce.op.stages.sparkwrappers.specific.OpEstimatorWrappercom.salesforce.op.stages.impl.feature.OpWord2Vec→com.salesforce.op.stages.sparkwrappers.specific.OpEstimatorWrapper
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.sparkwrappers.specific, so a change to com.salesforce.op.stages.sparkwrappers.specific can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.stages.sparkwrappers.specific.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→24 com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.impl.classification✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.stages.impl.classification.
- The types involved
com.salesforce.op.stages.impl.feature.DecisionTreeNumericBucketizerParams→com.salesforce.op.stages.impl.classification.Impurity
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op.stages.impl.classification, so a change to com.salesforce.op.stages.impl.classification can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.stages.impl.classification.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.feature uses a module listed above it, which is the healthy direction.
27→35 com.salesforce.op.stages.impl.feature uses com.salesforce.op part of a loop✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.feature uses a type in com.salesforce.op.
- The types involved
com.salesforce.op.stages.impl.feature.Transmogrifier→com.salesforce.op.FeatureHistory
- Direction
- com.salesforce.op.stages.impl.feature uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.op.stages.impl.feature, while a change to com.salesforce.op.stages.impl.feature can't break com.salesforce.op.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→1 com.salesforce.op.dsl.RichDateFeature uses com.salesforce.op.features.types✕
- Connections
- 8 pairs of types, where a type in com.salesforce.op.dsl.RichDateFeature uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.dsl.RichDateFeature.RichDateFeature→com.salesforce.op.features.types.Datecom.salesforce.op.dsl.RichDateFeature.RichDateFeature→com.salesforce.op.features.types.DateListcom.salesforce.op.dsl.RichDateFeature.RichDateFeature→com.salesforce.op.features.types.Integralcom.salesforce.op.dsl.RichDateFeature.RichDateFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichDateFeature.RichDateTimeFeature→com.salesforce.op.features.types.DateTimecom.salesforce.op.dsl.RichDateFeature.RichDateTimeFeature→com.salesforce.op.features.types.DateTimeListcom.salesforce.op.dsl.RichDateFeature.RichDateTimeFeature→com.salesforce.op.features.types.Integralcom.salesforce.op.dsl.RichDateFeature.RichDateTimeFeature→com.salesforce.op.features.types.OPVector
- Direction
- com.salesforce.op.dsl.RichDateFeature uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.dsl.RichDateFeature, while a change to com.salesforce.op.dsl.RichDateFeature can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichDateFeature uses a module listed above it, which is the healthy direction.
28→13 com.salesforce.op.dsl.RichDateFeature uses com.salesforce.op.features✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.dsl.RichDateFeature uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.dsl.RichDateFeature.RichDateFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichDateFeature.RichDateTimeFeature→com.salesforce.op.features.FeatureLike
- Direction
- com.salesforce.op.dsl.RichDateFeature uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.dsl.RichDateFeature, while a change to com.salesforce.op.dsl.RichDateFeature can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichDateFeature uses a module listed above it, which is the healthy direction.
28→27 com.salesforce.op.dsl.RichDateFeature uses com.salesforce.op.stages.impl.feature✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op.dsl.RichDateFeature uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.dsl.RichDateFeature.RichDateFeature→com.salesforce.op.stages.impl.feature.DateListPivotcom.salesforce.op.dsl.RichDateFeature.RichDateFeature→com.salesforce.op.stages.impl.feature.TimePeriodcom.salesforce.op.dsl.RichDateFeature.RichDateTimeFeature→com.salesforce.op.stages.impl.feature.DateListPivotcom.salesforce.op.dsl.RichDateFeature.RichDateTimeFeature→com.salesforce.op.stages.impl.feature.TimePeriod
- Direction
- com.salesforce.op.dsl.RichDateFeature uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.dsl.RichDateFeature, while a change to com.salesforce.op.dsl.RichDateFeature can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichDateFeature uses a module listed above it, which is the healthy direction.
29→1 com.salesforce.op.dsl.RichListFeature uses com.salesforce.op.features.types✕
- Connections
- 8 pairs of types, where a type in com.salesforce.op.dsl.RichListFeature uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.dsl.RichListFeature.RichDateListFeature→com.salesforce.op.features.types.DateListcom.salesforce.op.dsl.RichListFeature.RichDateListFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichListFeature.RichDateTimeListFeature→com.salesforce.op.features.types.DateTimeListcom.salesforce.op.dsl.RichListFeature.RichDateTimeListFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichListFeature.RichGeolocationFeature→com.salesforce.op.features.types.Geolocationcom.salesforce.op.dsl.RichListFeature.RichGeolocationFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichListFeature.RichTextListFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichListFeature.RichTextListFeature→com.salesforce.op.features.types.TextList
- Direction
- com.salesforce.op.dsl.RichListFeature uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.dsl.RichListFeature, while a change to com.salesforce.op.dsl.RichListFeature can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichListFeature uses a module listed above it, which is the healthy direction.
29→13 com.salesforce.op.dsl.RichListFeature uses com.salesforce.op.features✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op.dsl.RichListFeature uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.dsl.RichListFeature.RichDateListFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichListFeature.RichDateTimeListFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichListFeature.RichGeolocationFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichListFeature.RichTextListFeature→com.salesforce.op.features.FeatureLike
- Direction
- com.salesforce.op.dsl.RichListFeature uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.dsl.RichListFeature, while a change to com.salesforce.op.dsl.RichListFeature can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichListFeature uses a module listed above it, which is the healthy direction.
29→27 com.salesforce.op.dsl.RichListFeature uses com.salesforce.op.stages.impl.feature✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op.dsl.RichListFeature uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.dsl.RichListFeature.RichDateListFeature→com.salesforce.op.stages.impl.feature.DateListPivotcom.salesforce.op.dsl.RichListFeature.RichDateListFeature→com.salesforce.op.stages.impl.feature.TimePeriodcom.salesforce.op.dsl.RichListFeature.RichDateTimeListFeature→com.salesforce.op.stages.impl.feature.DateListPivotcom.salesforce.op.dsl.RichListFeature.RichDateTimeListFeature→com.salesforce.op.stages.impl.feature.TimePeriod
- Direction
- com.salesforce.op.dsl.RichListFeature uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.dsl.RichListFeature, while a change to com.salesforce.op.dsl.RichListFeature can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichListFeature uses a module listed above it, which is the healthy direction.
30→1 com.salesforce.op.dsl.RichMapFeature uses com.salesforce.op.features.types✕
- Connections
- 34 pairs of types, where a type in com.salesforce.op.dsl.RichMapFeature uses a type in com.salesforce.op.features.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.salesforce.op.dsl.RichMapFeature.RichBase64MapFeature→com.salesforce.op.features.types.Base64Mapcom.salesforce.op.dsl.RichMapFeature.RichBase64MapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichBase64MapFeature→com.salesforce.op.features.types.PickListMapcom.salesforce.op.dsl.RichMapFeature.RichBooleanMapFeature→com.salesforce.op.features.types.BinaryMapcom.salesforce.op.dsl.RichMapFeature.RichBooleanMapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichDateMapFeature→com.salesforce.op.features.types.DateMapcom.salesforce.op.dsl.RichMapFeature.RichDateMapFeature→com.salesforce.op.features.types.DateTimecom.salesforce.op.dsl.RichMapFeature.RichDateMapFeature→com.salesforce.op.features.types.IntegralMapcom.salesforce.op.dsl.RichMapFeature.RichDateMapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichDateTimeMapFeature→com.salesforce.op.features.types.DateTimecom.salesforce.op.dsl.RichMapFeature.RichDateTimeMapFeature→com.salesforce.op.features.types.DateTimeMapcom.salesforce.op.dsl.RichMapFeature.RichDateTimeMapFeature→com.salesforce.op.features.types.IntegralMapcom.salesforce.op.dsl.RichMapFeature.RichDateTimeMapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichEmailMapFeature→com.salesforce.op.features.types.EmailMapcom.salesforce.op.dsl.RichMapFeature.RichEmailMapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichGeolocationMapFeature→com.salesforce.op.features.types.Geolocationcom.salesforce.op.dsl.RichMapFeature.RichGeolocationMapFeature→com.salesforce.op.features.types.GeolocationMapcom.salesforce.op.dsl.RichMapFeature.RichGeolocationMapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichIntegralMapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichIntegralMapFeature→com.salesforce.op.features.types.RealNNcom.salesforce.op.dsl.RichMapFeature.RichMultiPickListMapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichPhoneMapFeature→com.salesforce.op.features.types.BinaryMapcom.salesforce.op.dsl.RichMapFeature.RichPhoneMapFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichMapFeature.RichPhoneMapFeature→com.salesforce.op.features.types.PhoneMapcom.salesforce.op.dsl.RichMapFeature.RichPredictionFeature→com.salesforce.op.features.types.Prediction
- Direction
- com.salesforce.op.dsl.RichMapFeature uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.dsl.RichMapFeature, while a change to com.salesforce.op.dsl.RichMapFeature can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichMapFeature uses a module listed above it, which is the healthy direction.
30→4 com.salesforce.op.dsl.RichMapFeature uses com.salesforce.op.utils.text✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.dsl.RichMapFeature uses a type in com.salesforce.op.utils.text.
- The types involved
com.salesforce.op.dsl.RichMapFeature.RichTextAreaMapFeature→com.salesforce.op.utils.text.Languagecom.salesforce.op.dsl.RichMapFeature.RichTextMapFeature→com.salesforce.op.utils.text.Language
- Direction
- com.salesforce.op.dsl.RichMapFeature uses com.salesforce.op.utils.text, so a change to com.salesforce.op.utils.text can break com.salesforce.op.dsl.RichMapFeature, while a change to com.salesforce.op.dsl.RichMapFeature can't break com.salesforce.op.utils.text.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichMapFeature uses a module listed above it, which is the healthy direction.
30→13 com.salesforce.op.dsl.RichMapFeature uses com.salesforce.op.features✕
- Connections
- 16 pairs of types, where a type in com.salesforce.op.dsl.RichMapFeature uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.dsl.RichMapFeature.RichBase64MapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichBooleanMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichDateMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichDateTimeMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichEmailMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichGeolocationMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichIntegralMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichMultiPickListMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichPhoneMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichPredictionFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichRealMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichStringMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichTextAreaMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichTextMapFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichMapFeature.RichURLMapFeature→com.salesforce.op.features.FeatureLike
- Direction
- com.salesforce.op.dsl.RichMapFeature uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.dsl.RichMapFeature, while a change to com.salesforce.op.dsl.RichMapFeature can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichMapFeature uses a module listed above it, which is the healthy direction.
30→27 com.salesforce.op.dsl.RichMapFeature uses com.salesforce.op.stages.impl.feature✕
- Connections
- 8 pairs of types, where a type in com.salesforce.op.dsl.RichMapFeature uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.dsl.RichMapFeature.RichDateMapFeature→com.salesforce.op.stages.impl.feature.TimePeriodcom.salesforce.op.dsl.RichMapFeature.RichDateTimeMapFeature→com.salesforce.op.stages.impl.feature.TimePeriodcom.salesforce.op.dsl.RichMapFeature.RichTextAreaMapFeature→com.salesforce.op.stages.impl.feature.HashAlgorithmcom.salesforce.op.dsl.RichMapFeature.RichTextAreaMapFeature→com.salesforce.op.stages.impl.feature.HashSpaceStrategycom.salesforce.op.dsl.RichMapFeature.RichTextAreaMapFeature→com.salesforce.op.stages.impl.feature.TextLengthTypecom.salesforce.op.dsl.RichMapFeature.RichTextMapFeature→com.salesforce.op.stages.impl.feature.HashAlgorithmcom.salesforce.op.dsl.RichMapFeature.RichTextMapFeature→com.salesforce.op.stages.impl.feature.HashSpaceStrategycom.salesforce.op.dsl.RichMapFeature.RichTextMapFeature→com.salesforce.op.stages.impl.feature.TextLengthType
- Direction
- com.salesforce.op.dsl.RichMapFeature uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.dsl.RichMapFeature, while a change to com.salesforce.op.dsl.RichMapFeature can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichMapFeature uses a module listed above it, which is the healthy direction.
31→1 com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.features.types✕
- Connections
- 29 pairs of types, where a type in com.salesforce.op.dsl.RichTextFeature uses a type in com.salesforce.op.features.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.salesforce.op.dsl.RichTextFeature.RichBase64Feature→com.salesforce.op.features.types.Base64com.salesforce.op.dsl.RichTextFeature.RichBase64Feature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichTextFeature.RichBase64Feature→com.salesforce.op.features.types.Textcom.salesforce.op.dsl.RichTextFeature.RichComboBoxFeature→com.salesforce.op.features.types.ComboBoxcom.salesforce.op.dsl.RichTextFeature.RichComboBoxFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichTextFeature.RichEmailFeature→com.salesforce.op.features.types.Binarycom.salesforce.op.dsl.RichTextFeature.RichEmailFeature→com.salesforce.op.features.types.Emailcom.salesforce.op.dsl.RichTextFeature.RichEmailFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichTextFeature.RichEmailFeature→com.salesforce.op.features.types.Textcom.salesforce.op.dsl.RichTextFeature.RichIdFeature→com.salesforce.op.features.types.IDcom.salesforce.op.dsl.RichTextFeature.RichIdFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichTextFeature.RichPhoneFeature→com.salesforce.op.features.types.Binarycom.salesforce.op.dsl.RichTextFeature.RichPhoneFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichTextFeature.RichPhoneFeature→com.salesforce.op.features.types.Phonecom.salesforce.op.dsl.RichTextFeature.RichPhoneFeature→com.salesforce.op.features.types.Textcom.salesforce.op.dsl.RichTextFeature.RichPickListFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichTextFeature.RichPickListFeature→com.salesforce.op.features.types.PickListcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.types.Binarycom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.types.MultiPickListcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.types.MultiPickListMapcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.types.NameStatscom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.types.RealMapcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.types.RealNNcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.types.TextList
- Direction
- com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.dsl.RichTextFeature, while a change to com.salesforce.op.dsl.RichTextFeature can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichTextFeature uses a module listed above it, which is the healthy direction.
31→4 com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.utils.text✕
- Connections
- 5 pairs of types, where a type in com.salesforce.op.dsl.RichTextFeature uses a type in com.salesforce.op.utils.text.
- The types involved
com.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.utils.text.Languagecom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.utils.text.LanguageDetectorcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.utils.text.NameEntityTaggercom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.utils.text.SentenceSplittercom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.utils.text.TextAnalyzer
- Direction
- com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.utils.text, so a change to com.salesforce.op.utils.text can break com.salesforce.op.dsl.RichTextFeature, while a change to com.salesforce.op.dsl.RichTextFeature can't break com.salesforce.op.utils.text.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichTextFeature uses a module listed above it, which is the healthy direction.
31→10 com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.utils.stages✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.dsl.RichTextFeature uses a type in com.salesforce.op.utils.stages.
- The types involved
com.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.utils.stages.SensitiveFeatureMode
- Direction
- com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.utils.stages, so a change to com.salesforce.op.utils.stages can break com.salesforce.op.dsl.RichTextFeature, while a change to com.salesforce.op.dsl.RichTextFeature can't break com.salesforce.op.utils.stages.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichTextFeature uses a module listed above it, which is the healthy direction.
31→13 com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.features✕
- Connections
- 8 pairs of types, where a type in com.salesforce.op.dsl.RichTextFeature uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.dsl.RichTextFeature.RichBase64Feature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichTextFeature.RichComboBoxFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichTextFeature.RichEmailFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichTextFeature.RichIdFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichTextFeature.RichPhoneFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichTextFeature.RichPickListFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichTextFeature.RichURLFeature→com.salesforce.op.features.FeatureLike
- Direction
- com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.dsl.RichTextFeature, while a change to com.salesforce.op.dsl.RichTextFeature can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichTextFeature uses a module listed above it, which is the healthy direction.
31→27 com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.stages.impl.feature✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op.dsl.RichTextFeature uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.stages.impl.feature.HashAlgorithmcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.stages.impl.feature.HashSpaceStrategycom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.stages.impl.feature.StringIndexerHandleInvalidcom.salesforce.op.dsl.RichTextFeature.RichTextFeature→com.salesforce.op.stages.impl.feature.TextLengthType
- Direction
- com.salesforce.op.dsl.RichTextFeature uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.dsl.RichTextFeature, while a change to com.salesforce.op.dsl.RichTextFeature can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichTextFeature uses a module listed above it, which is the healthy direction.
32→1 com.salesforce.op.stages.impl.preparators uses com.salesforce.op.features.types✕
- Connections
- 7 pairs of types, where a type in com.salesforce.op.stages.impl.preparators uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.stages.impl.preparators.DerivedFeatureFilterUtils→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.preparators.MinVarianceFilter→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.preparators.MinVarianceFilterModel→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.preparators.PredictionDeIndexer→com.salesforce.op.features.types.RealNNcom.salesforce.op.stages.impl.preparators.PredictionDeIndexer→com.salesforce.op.features.types.Textcom.salesforce.op.stages.impl.preparators.SanityChecker→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.preparators.SanityChecker→com.salesforce.op.features.types.RealNN
- Direction
- com.salesforce.op.stages.impl.preparators uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.stages.impl.preparators, while a change to com.salesforce.op.stages.impl.preparators can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.preparators uses a module listed above it, which is the healthy direction.
32→9 com.salesforce.op.stages.impl.preparators uses com.salesforce.op.utils.spark✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.stages.impl.preparators uses a type in com.salesforce.op.utils.spark.
- The types involved
com.salesforce.op.stages.impl.preparators.ColumnStatistics→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.stages.impl.preparators.DerivedFeatureFilterUtils→com.salesforce.op.utils.spark.OpVectorColumnMetadatacom.salesforce.op.stages.impl.preparators.SanityChecker→com.salesforce.op.utils.spark.OpVectorColumnMetadata
- Direction
- com.salesforce.op.stages.impl.preparators uses com.salesforce.op.utils.spark, so a change to com.salesforce.op.utils.spark can break com.salesforce.op.stages.impl.preparators, while a change to com.salesforce.op.stages.impl.preparators can't break com.salesforce.op.utils.spark.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.preparators uses a module listed above it, which is the healthy direction.
32→12 com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.preparators uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.stages.impl.preparators.SanityChecker→com.salesforce.op.stages.AllowLabelAsInputcom.salesforce.op.stages.impl.preparators.SanityCheckerModel→com.salesforce.op.stages.AllowLabelAsInput
- Direction
- com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op.stages.impl.preparators, while a change to com.salesforce.op.stages.impl.preparators can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.preparators uses a module listed above it, which is the healthy direction.
32→15 com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages.base.binary✕
- Connections
- 6 pairs of types, where a type in com.salesforce.op.stages.impl.preparators uses a type in com.salesforce.op.stages.base.binary.
- The types involved
com.salesforce.op.stages.impl.preparators.PredictionDeIndexer→com.salesforce.op.stages.base.binary.BinaryEstimatorcom.salesforce.op.stages.impl.preparators.PredictionDeIndexer→com.salesforce.op.stages.base.binary.BinaryModelcom.salesforce.op.stages.impl.preparators.PredictionDeIndexerModel→com.salesforce.op.stages.base.binary.BinaryModelcom.salesforce.op.stages.impl.preparators.SanityChecker→com.salesforce.op.stages.base.binary.BinaryEstimatorcom.salesforce.op.stages.impl.preparators.SanityChecker→com.salesforce.op.stages.base.binary.BinaryModelcom.salesforce.op.stages.impl.preparators.SanityCheckerModel→com.salesforce.op.stages.base.binary.BinaryModel
- Direction
- com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages.base.binary, so a change to com.salesforce.op.stages.base.binary can break com.salesforce.op.stages.impl.preparators, while a change to com.salesforce.op.stages.impl.preparators can't break com.salesforce.op.stages.base.binary.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.preparators uses a module listed above it, which is the healthy direction.
32→16 com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages.base.unary✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.stages.impl.preparators uses a type in com.salesforce.op.stages.base.unary.
- The types involved
com.salesforce.op.stages.impl.preparators.MinVarianceFilter→com.salesforce.op.stages.base.unary.UnaryEstimatorcom.salesforce.op.stages.impl.preparators.MinVarianceFilter→com.salesforce.op.stages.base.unary.UnaryModelcom.salesforce.op.stages.impl.preparators.MinVarianceFilterModel→com.salesforce.op.stages.base.unary.UnaryModel
- Direction
- com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages.base.unary, so a change to com.salesforce.op.stages.base.unary can break com.salesforce.op.stages.impl.preparators, while a change to com.salesforce.op.stages.impl.preparators can't break com.salesforce.op.stages.base.unary.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.preparators uses a module listed above it, which is the healthy direction.
32→20 com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages.impl✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.preparators uses a type in com.salesforce.op.stages.impl.
- The types involved
com.salesforce.op.stages.impl.preparators.MinVarianceSummary→com.salesforce.op.stages.impl.MetadataLike
- Direction
- com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages.impl, so a change to com.salesforce.op.stages.impl can break com.salesforce.op.stages.impl.preparators, while a change to com.salesforce.op.stages.impl.preparators can't break com.salesforce.op.stages.impl.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.preparators uses a module listed above it, which is the healthy direction.
32→27 com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages.impl.feature✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.preparators uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.stages.impl.preparators.PredictionDeIndexer→com.salesforce.op.stages.impl.feature.SaveOthersParams
- Direction
- com.salesforce.op.stages.impl.preparators uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.stages.impl.preparators, while a change to com.salesforce.op.stages.impl.preparators can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.preparators uses a module listed above it, which is the healthy direction.
33→1 com.salesforce.op.dsl.RichNumericFeature uses com.salesforce.op.features.types✕
- Connections
- 12 pairs of types, where a type in com.salesforce.op.dsl.RichNumericFeature uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.dsl.RichNumericFeature.RichBinaryFeature→com.salesforce.op.features.types.Binarycom.salesforce.op.dsl.RichNumericFeature.RichBinaryFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichNumericFeature.RichBinaryFeature→com.salesforce.op.features.types.RealNNcom.salesforce.op.dsl.RichNumericFeature.RichIntegralFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichNumericFeature.RichIntegralFeature→com.salesforce.op.features.types.RealNNcom.salesforce.op.dsl.RichNumericFeature.RichNumericFeature→com.salesforce.op.features.types.Integralcom.salesforce.op.dsl.RichNumericFeature.RichNumericFeature→com.salesforce.op.features.types.Realcom.salesforce.op.dsl.RichNumericFeature.RichRealFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichNumericFeature.RichRealFeature→com.salesforce.op.features.types.RealNNcom.salesforce.op.dsl.RichNumericFeature.RichRealNNFeature→com.salesforce.op.features.types.OPVectorcom.salesforce.op.dsl.RichNumericFeature.RichRealNNFeature→com.salesforce.op.features.types.RealNNcom.salesforce.op.dsl.RichNumericFeature.RichRealNNFeature→com.salesforce.op.features.types.Text
- Direction
- com.salesforce.op.dsl.RichNumericFeature uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.dsl.RichNumericFeature, while a change to com.salesforce.op.dsl.RichNumericFeature can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichNumericFeature uses a module listed above it, which is the healthy direction.
33→13 com.salesforce.op.dsl.RichNumericFeature uses com.salesforce.op.features✕
- Connections
- 5 pairs of types, where a type in com.salesforce.op.dsl.RichNumericFeature uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.dsl.RichNumericFeature.RichBinaryFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichNumericFeature.RichIntegralFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichNumericFeature.RichNumericFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichNumericFeature.RichRealFeature→com.salesforce.op.features.FeatureLikecom.salesforce.op.dsl.RichNumericFeature.RichRealNNFeature→com.salesforce.op.features.FeatureLike
- Direction
- com.salesforce.op.dsl.RichNumericFeature uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.dsl.RichNumericFeature, while a change to com.salesforce.op.dsl.RichNumericFeature can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichNumericFeature uses a module listed above it, which is the healthy direction.
33→27 com.salesforce.op.dsl.RichNumericFeature uses com.salesforce.op.stages.impl.feature✕
- Connections
- 5 pairs of types, where a type in com.salesforce.op.dsl.RichNumericFeature uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.dsl.RichNumericFeature.RichIntegralFeature→com.salesforce.op.stages.impl.feature.Inclusioncom.salesforce.op.dsl.RichNumericFeature.RichRealFeature→com.salesforce.op.stages.impl.feature.Inclusioncom.salesforce.op.dsl.RichNumericFeature.RichRealFeature→com.salesforce.op.stages.impl.feature.ScalingArgscom.salesforce.op.dsl.RichNumericFeature.RichRealFeature→com.salesforce.op.stages.impl.feature.ScalingTypecom.salesforce.op.dsl.RichNumericFeature.RichRealNNFeature→com.salesforce.op.stages.impl.feature.IndexToStringHandleInvalid
- Direction
- com.salesforce.op.dsl.RichNumericFeature uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.dsl.RichNumericFeature, while a change to com.salesforce.op.dsl.RichNumericFeature can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichNumericFeature uses a module listed above it, which is the healthy direction.
33→32 com.salesforce.op.dsl.RichNumericFeature uses com.salesforce.op.stages.impl.preparators✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.dsl.RichNumericFeature uses a type in com.salesforce.op.stages.impl.preparators.
- The types involved
com.salesforce.op.dsl.RichNumericFeature.RichRealNNFeature→com.salesforce.op.stages.impl.preparators.CorrelationExclusioncom.salesforce.op.dsl.RichNumericFeature.RichRealNNFeature→com.salesforce.op.stages.impl.preparators.CorrelationLevelcom.salesforce.op.dsl.RichNumericFeature.RichRealNNFeature→com.salesforce.op.stages.impl.preparators.CorrelationType
- Direction
- com.salesforce.op.dsl.RichNumericFeature uses com.salesforce.op.stages.impl.preparators, so a change to com.salesforce.op.stages.impl.preparators can break com.salesforce.op.dsl.RichNumericFeature, while a change to com.salesforce.op.dsl.RichNumericFeature can't break com.salesforce.op.stages.impl.preparators.
- Position
- Below the diagonal: com.salesforce.op.dsl.RichNumericFeature uses a module listed above it, which is the healthy direction.
34→13 com.salesforce.op.filters uses com.salesforce.op.features✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op.filters uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.filters.FeatureDistribution→com.salesforce.op.features.FeatureDistributionLikecom.salesforce.op.filters.FeatureDistribution→com.salesforce.op.features.FeatureDistributionTypecom.salesforce.op.filters.PreparedFeatures→com.salesforce.op.features.FeatureDistributionTypecom.salesforce.op.filters.RawFeatureFilter→com.salesforce.op.features.FeatureDistributionType
- Direction
- com.salesforce.op.filters uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op.filters, while a change to com.salesforce.op.filters can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op.filters uses a module listed above it, which is the healthy direction.
34→14 com.salesforce.op.filters uses com.salesforce.op.readers✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.filters uses a type in com.salesforce.op.readers.
- The types involved
com.salesforce.op.filters.RawFeatureFilter→com.salesforce.op.readers.Reader
- Direction
- com.salesforce.op.filters uses com.salesforce.op.readers, so a change to com.salesforce.op.readers can break com.salesforce.op.filters, while a change to com.salesforce.op.filters can't break com.salesforce.op.readers.
- Position
- Below the diagonal: com.salesforce.op.filters uses a module listed above it, which is the healthy direction.
34→27 com.salesforce.op.filters uses com.salesforce.op.stages.impl.feature✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.filters uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.filters.FeatureDistribution→com.salesforce.op.stages.impl.feature.TextStatscom.salesforce.op.filters.RawFeatureFilter→com.salesforce.op.stages.impl.feature.TimePeriod
- Direction
- com.salesforce.op.filters uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.filters, while a change to com.salesforce.op.filters can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op.filters uses a module listed above it, which is the healthy direction.
34→32 com.salesforce.op.filters uses com.salesforce.op.stages.impl.preparators✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.filters uses a type in com.salesforce.op.stages.impl.preparators.
- The types involved
com.salesforce.op.filters.RawFeatureFilter→com.salesforce.op.stages.impl.preparators.CorrelationTypecom.salesforce.op.filters.RawFeatureFilterConfig→com.salesforce.op.stages.impl.preparators.CorrelationType
- Direction
- com.salesforce.op.filters uses com.salesforce.op.stages.impl.preparators, so a change to com.salesforce.op.stages.impl.preparators can break com.salesforce.op.filters, while a change to com.salesforce.op.filters can't break com.salesforce.op.stages.impl.preparators.
- Position
- Below the diagonal: com.salesforce.op.filters uses a module listed above it, which is the healthy direction.
34→35 com.salesforce.op.filters uses com.salesforce.op part of a loop✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.filters uses a type in com.salesforce.op.
- The types involved
com.salesforce.op.filters.RawFeatureFilter→com.salesforce.op.OpParams
- Direction
- com.salesforce.op.filters uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.op.filters, while a change to com.salesforce.op.filters can't break com.salesforce.op.
- 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→3 com.salesforce.op uses com.salesforce.op.utils.json✕
- Connections
- 6 pairs of types, where a type in com.salesforce.op uses a type in com.salesforce.op.utils.json.
- The types involved
com.salesforce.op.FeatureHistory→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.GenderDetectionResults→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.OpParams→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.OpWorkflowRunnerConfig→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.ReaderParams→com.salesforce.op.utils.json.JsonLikecom.salesforce.op.SensitiveFeatureInformation→com.salesforce.op.utils.json.JsonLike
- Direction
- com.salesforce.op uses com.salesforce.op.utils.json, so a change to com.salesforce.op.utils.json can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.utils.json.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→9 com.salesforce.op uses com.salesforce.op.utils.spark✕
- Connections
- 1 pair of types, where a type in com.salesforce.op uses a type in com.salesforce.op.utils.spark.
- The types involved
com.salesforce.op.OpWorkflowRunner→com.salesforce.op.utils.spark.AppMetrics
- Direction
- com.salesforce.op uses com.salesforce.op.utils.spark, so a change to com.salesforce.op.utils.spark can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.utils.spark.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→12 com.salesforce.op uses com.salesforce.op.stages✕
- Connections
- 1 pair of types, where a type in com.salesforce.op uses a type in com.salesforce.op.stages.
- The types involved
com.salesforce.op.OpWorkflowModel→com.salesforce.op.stages.OpPipelineStage
- Direction
- com.salesforce.op uses com.salesforce.op.stages, so a change to com.salesforce.op.stages can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.stages.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→13 com.salesforce.op uses com.salesforce.op.features✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op uses a type in com.salesforce.op.features.
- The types involved
com.salesforce.op.OpWorkflowModel→com.salesforce.op.features.FeatureLikecom.salesforce.op.stages→com.salesforce.op.features.TransientFeature
- Direction
- com.salesforce.op uses com.salesforce.op.features, so a change to com.salesforce.op.features can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.features.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→14 com.salesforce.op uses com.salesforce.op.readers✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op uses a type in com.salesforce.op.readers.
- The types involved
com.salesforce.op.OpWorkflow→com.salesforce.op.readers.Readercom.salesforce.op.OpWorkflowCore→com.salesforce.op.readers.Readercom.salesforce.op.OpWorkflowRunner→com.salesforce.op.readers.Readercom.salesforce.op.OpWorkflowRunner→com.salesforce.op.readers.StreamingReader
- Direction
- com.salesforce.op uses com.salesforce.op.readers, so a change to com.salesforce.op.readers can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.readers.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→19 com.salesforce.op uses com.salesforce.op.evaluators✕
- Connections
- 4 pairs of types, where a type in com.salesforce.op uses a type in com.salesforce.op.evaluators.
- The types involved
com.salesforce.op.EvaluateResult→com.salesforce.op.evaluators.EvaluationMetricscom.salesforce.op.OpWorkflowModel→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.OpWorkflowRunner→com.salesforce.op.evaluators.OpEvaluatorBasecom.salesforce.op.ScoreResult→com.salesforce.op.evaluators.EvaluationMetrics
- Direction
- com.salesforce.op uses com.salesforce.op.evaluators, so a change to com.salesforce.op.evaluators can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.evaluators.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→23 com.salesforce.op uses com.salesforce.op.stages.impl.selector✕
- Connections
- 1 pair of types, where a type in com.salesforce.op uses a type in com.salesforce.op.stages.impl.selector.
- The types involved
com.salesforce.op.ModelInsights→com.salesforce.op.stages.impl.selector.ModelSelectorSummary
- Direction
- com.salesforce.op uses com.salesforce.op.stages.impl.selector, so a change to com.salesforce.op.stages.impl.selector can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.stages.impl.selector.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→27 com.salesforce.op uses com.salesforce.op.stages.impl.feature✕
- Connections
- 1 pair of types, where a type in com.salesforce.op uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.OpWorkflow→com.salesforce.op.stages.impl.feature.TimePeriod
- Direction
- com.salesforce.op uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→32 com.salesforce.op uses com.salesforce.op.stages.impl.preparators✕
- Connections
- 1 pair of types, where a type in com.salesforce.op uses a type in com.salesforce.op.stages.impl.preparators.
- The types involved
com.salesforce.op.OpWorkflow→com.salesforce.op.stages.impl.preparators.CorrelationType
- Direction
- com.salesforce.op uses com.salesforce.op.stages.impl.preparators, so a change to com.salesforce.op.stages.impl.preparators can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.stages.impl.preparators.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
35→34 com.salesforce.op uses com.salesforce.op.filters✕
- Connections
- 8 pairs of types, where a type in com.salesforce.op uses a type in com.salesforce.op.filters.
- The types involved
com.salesforce.op.FeatureInsights→com.salesforce.op.filters.ExclusionReasonscom.salesforce.op.FeatureInsights→com.salesforce.op.filters.FeatureDistributioncom.salesforce.op.FeatureInsights→com.salesforce.op.filters.RawFeatureFilterMetricscom.salesforce.op.OpWorkflow→com.salesforce.op.filters.FeatureDistributioncom.salesforce.op.OpWorkflow→com.salesforce.op.filters.RawFeatureFiltercom.salesforce.op.OpWorkflowCore→com.salesforce.op.filters.FeatureDistributioncom.salesforce.op.OpWorkflowCore→com.salesforce.op.filters.RawFeatureFilterResultscom.salesforce.op.OpWorkflowModelReader→com.salesforce.op.filters.RawFeatureFilterResults
- Direction
- com.salesforce.op uses com.salesforce.op.filters, so a change to com.salesforce.op.filters can break com.salesforce.op, while a change to com.salesforce.op can't break com.salesforce.op.filters.
- Position
- Below the diagonal: com.salesforce.op uses a module listed above it, which is the healthy direction.
36→14 com.salesforce.app.Simple uses com.salesforce.op.readers✕
- Connections
- 2 pairs of types, where a type in com.salesforce.app.Simple uses a type in com.salesforce.op.readers.
- The types involved
com.salesforce.app.Simple.ReaderWithHeaders→com.salesforce.op.readers.CSVAutoReadercom.salesforce.app.Simple.ReaderWithNoHeaders→com.salesforce.op.readers.CSVReader
- Direction
- com.salesforce.app.Simple uses com.salesforce.op.readers, so a change to com.salesforce.op.readers can break com.salesforce.app.Simple, while a change to com.salesforce.app.Simple can't break com.salesforce.op.readers.
- Position
- Below the diagonal: com.salesforce.app.Simple uses a module listed above it, which is the healthy direction.
36→35 com.salesforce.app.Simple uses com.salesforce.op✕
- Connections
- 2 pairs of types, where a type in com.salesforce.app.Simple uses a type in com.salesforce.op.
- The types involved
com.salesforce.app.Simple.ReaderWithHeaders→com.salesforce.op.OpParamscom.salesforce.app.Simple.ReaderWithNoHeaders→com.salesforce.op.OpParams
- Direction
- com.salesforce.app.Simple uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.app.Simple, while a change to com.salesforce.app.Simple can't break com.salesforce.op.
- Position
- Below the diagonal: com.salesforce.app.Simple uses a module listed above it, which is the healthy direction.
37→35 com.salesforce.hw.boston uses com.salesforce.op✕
- Connections
- 3 pairs of types, where a type in com.salesforce.hw.boston uses a type in com.salesforce.op.
- The types involved
com.salesforce.hw.boston.OpBoston→com.salesforce.op.OpAppWithRunnercom.salesforce.hw.boston.OpBoston→com.salesforce.op.OpParamscom.salesforce.hw.boston.OpBoston→com.salesforce.op.OpWorkflowRunner
- Direction
- com.salesforce.hw.boston uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.hw.boston, while a change to com.salesforce.hw.boston can't break com.salesforce.op.
- Position
- Below the diagonal: com.salesforce.hw.boston uses a module listed above it, which is the healthy direction.
38→35 com.salesforce.hw.iris uses com.salesforce.op✕
- Connections
- 3 pairs of types, where a type in com.salesforce.hw.iris uses a type in com.salesforce.op.
- The types involved
com.salesforce.hw.iris.OpIris→com.salesforce.op.OpAppWithRunnercom.salesforce.hw.iris.OpIris→com.salesforce.op.OpParamscom.salesforce.hw.iris.OpIris→com.salesforce.op.OpWorkflowRunner
- Direction
- com.salesforce.hw.iris uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.hw.iris, while a change to com.salesforce.hw.iris can't break com.salesforce.op.
- Position
- Below the diagonal: com.salesforce.hw.iris uses a module listed above it, which is the healthy direction.
39→1 com.salesforce.op.stages.impl.insights uses com.salesforce.op.features.types✕
- Connections
- 3 pairs of types, where a type in com.salesforce.op.stages.impl.insights uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.op.stages.impl.insights.Normalizer→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.insights.RecordInsightsLOCO→com.salesforce.op.features.types.OPVectorcom.salesforce.op.stages.impl.insights.RecordInsightsParser→com.salesforce.op.features.types.TextMap
- Direction
- com.salesforce.op.stages.impl.insights uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.op.stages.impl.insights, while a change to com.salesforce.op.stages.impl.insights can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.insights uses a module listed above it, which is the healthy direction.
39→9 com.salesforce.op.stages.impl.insights uses com.salesforce.op.utils.spark✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.insights uses a type in com.salesforce.op.utils.spark.
- The types involved
com.salesforce.op.stages.impl.insights.RecordInsightsLOCO→com.salesforce.op.utils.spark.OpVectorColumnHistorycom.salesforce.op.stages.impl.insights.RecordInsightsParser→com.salesforce.op.utils.spark.OpVectorColumnHistory
- Direction
- com.salesforce.op.stages.impl.insights uses com.salesforce.op.utils.spark, so a change to com.salesforce.op.utils.spark can break com.salesforce.op.stages.impl.insights, while a change to com.salesforce.op.stages.impl.insights can't break com.salesforce.op.utils.spark.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.insights uses a module listed above it, which is the healthy direction.
39→15 com.salesforce.op.stages.impl.insights uses com.salesforce.op.stages.base.binary✕
- Connections
- 2 pairs of types, where a type in com.salesforce.op.stages.impl.insights uses a type in com.salesforce.op.stages.base.binary.
- The types involved
com.salesforce.op.stages.impl.insights.RecordInsightsCorr→com.salesforce.op.stages.base.binary.BinaryEstimatorcom.salesforce.op.stages.impl.insights.RecordInsightsCorrModel→com.salesforce.op.stages.base.binary.BinaryModel
- Direction
- com.salesforce.op.stages.impl.insights uses com.salesforce.op.stages.base.binary, so a change to com.salesforce.op.stages.base.binary can break com.salesforce.op.stages.impl.insights, while a change to com.salesforce.op.stages.impl.insights can't break com.salesforce.op.stages.base.binary.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.insights uses a module listed above it, which is the healthy direction.
39→16 com.salesforce.op.stages.impl.insights uses com.salesforce.op.stages.base.unary✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.insights uses a type in com.salesforce.op.stages.base.unary.
- The types involved
com.salesforce.op.stages.impl.insights.RecordInsightsLOCO→com.salesforce.op.stages.base.unary.UnaryTransformer
- Direction
- com.salesforce.op.stages.impl.insights uses com.salesforce.op.stages.base.unary, so a change to com.salesforce.op.stages.base.unary can break com.salesforce.op.stages.impl.insights, while a change to com.salesforce.op.stages.impl.insights can't break com.salesforce.op.stages.base.unary.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.insights uses a module listed above it, which is the healthy direction.
39→27 com.salesforce.op.stages.impl.insights uses com.salesforce.op.stages.impl.feature✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.insights uses a type in com.salesforce.op.stages.impl.feature.
- The types involved
com.salesforce.op.stages.impl.insights.RecordInsightsLOCO→com.salesforce.op.stages.impl.feature.TimePeriod
- Direction
- com.salesforce.op.stages.impl.insights uses com.salesforce.op.stages.impl.feature, so a change to com.salesforce.op.stages.impl.feature can break com.salesforce.op.stages.impl.insights, while a change to com.salesforce.op.stages.impl.insights can't break com.salesforce.op.stages.impl.feature.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.insights uses a module listed above it, which is the healthy direction.
39→32 com.salesforce.op.stages.impl.insights uses com.salesforce.op.stages.impl.preparators✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.insights uses a type in com.salesforce.op.stages.impl.preparators.
- The types involved
com.salesforce.op.stages.impl.insights.RecordInsightsCorr→com.salesforce.op.stages.impl.preparators.CorrelationType
- Direction
- com.salesforce.op.stages.impl.insights uses com.salesforce.op.stages.impl.preparators, so a change to com.salesforce.op.stages.impl.preparators can break com.salesforce.op.stages.impl.insights, while a change to com.salesforce.op.stages.impl.insights can't break com.salesforce.op.stages.impl.preparators.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.insights uses a module listed above it, which is the healthy direction.
39→35 com.salesforce.op.stages.impl.insights uses com.salesforce.op✕
- Connections
- 1 pair of types, where a type in com.salesforce.op.stages.impl.insights uses a type in com.salesforce.op.
- The types involved
com.salesforce.op.stages.impl.insights.RecordInsightsParser→com.salesforce.op.Insights
- Direction
- com.salesforce.op.stages.impl.insights uses com.salesforce.op, so a change to com.salesforce.op can break com.salesforce.op.stages.impl.insights, while a change to com.salesforce.op.stages.impl.insights can't break com.salesforce.op.
- Position
- Below the diagonal: com.salesforce.op.stages.impl.insights uses a module listed above it, which is the healthy direction.
40→1 com.salesforce.hw.boston.BostonFeatures uses com.salesforce.op.features.types✕
- Connections
- 3 pairs of types, where a type in com.salesforce.hw.boston.BostonFeatures uses a type in com.salesforce.op.features.types.
- The types involved
com.salesforce.hw.boston.BostonFeatures.Chas→com.salesforce.op.features.types.PickListcom.salesforce.hw.boston.BostonFeatures.IntegralExtract→com.salesforce.op.features.types.Integralcom.salesforce.hw.boston.BostonFeatures.RealNNExtract→com.salesforce.op.features.types.RealNN
- Direction
- com.salesforce.hw.boston.BostonFeatures uses com.salesforce.op.features.types, so a change to com.salesforce.op.features.types can break com.salesforce.hw.boston.BostonFeatures, while a change to com.salesforce.hw.boston.BostonFeatures can't break com.salesforce.op.features.types.
- Position
- Below the diagonal: com.salesforce.hw.boston.BostonFeatures uses a module listed above it, which is the healthy direction.
40→37 com.salesforce.hw.boston.BostonFeatures uses com.salesforce.hw.boston✕
- Connections
- 3 pairs of types, where a type in com.salesforce.hw.boston.BostonFeatures uses a type in com.salesforce.hw.boston.
- The types involved
com.salesforce.hw.boston.BostonFeatures.Chas→com.salesforce.hw.boston.BostonHousecom.salesforce.hw.boston.BostonFeatures.IntegralExtract→com.salesforce.hw.boston.BostonHousecom.salesforce.hw.boston.BostonFeatures.RealNNExtract→com.salesforce.hw.boston.BostonHouse
- Direction
- com.salesforce.hw.boston.BostonFeatures uses com.salesforce.hw.boston, so a change to com.salesforce.hw.boston can break com.salesforce.hw.boston.BostonFeatures, while a change to com.salesforce.hw.boston.BostonFeatures can't break com.salesforce.hw.boston.
- Position
- Below the diagonal: com.salesforce.hw.boston.BostonFeatures uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 35 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED; Resolve the 310 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (3), spark.gradle (3), Maps.scala (2); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +6.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. | +4.4 pts | Medium | Architecture documentation |
| 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. | +4.2 pts | Medium | Nullable reference types |
| Resolve the 310 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (3), spark.gradle (3), Maps.scala (2). | +6.3 pts | High | Knowledge Freshness |
| Interpolated log message defeats structured logging | +2.5 pts | Medium | Structured logging |
| Enable Dependabot/Renovate or a dependency-review gate. | +2.0 pts | Medium | Security & performance tooling |
| Swallowed exception (empty catch) | +1.8 pts | Medium | Exception handling |
| Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with FeatureTypeFactory.newInstanceFn (cyclomatic 105), FeatureTypeSparkConverter.fromSparkFn (cyclomatic 34). | +1.2 pts | Medium | Cyclomatic Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| core/src/main/scala/com/salesforce/op/ModelInsights.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/com/salesforce/op/stages/impl/preparators/SanityChecker.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/com/salesforce/op/OpWorkflow.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/com/salesforce/op/stages/impl/feature/OPMapVectorizer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/test/scala/com/salesforce/op/filters/RawFeatureFilterTest.scala | 6.4 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/com/salesforce/op/stages/impl/feature/Transmogrifier.scala | 6.4 | Mixed | Explicit Debt: TodoComment |
| cli/src/test/scala/com/salesforce/op/cli/CliFullCycleTest.scala | 6.5 | Mixed | Explicit Debt: TodoComment |
| utils/src/main/scala/com/salesforce/op/utils/stats/OpStatistics.scala | 6.6 | Mixed | Explicit Debt: TodoComment |
| features/src/main/scala/com/salesforce/op/features/FeatureLike.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| utils/src/main/scala/com/salesforce/op/utils/spark/SequenceAggregators.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/com/salesforce/op/stages/impl/feature/PhoneNumberParser.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/com/salesforce/op/stages/impl/feature/OpCountVectorizer.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/com/salesforce/op/OpWorkflowModel.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| core/src/test/scala/com/salesforce/op/stages/impl/preparators/BadFeatureZooTest.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala | 7.0 | Mixed | God Classes: FileTooLong: dsl/RichMapFeature.scala |
| features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala | 7.0 | Mixed | Code Duplication: Near-duplicate member pair (54 shared lines) |
| core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala | 7.1 | Mixed | Code Duplication: Edited copy of a member (56 corresponding lines) |
| core/src/main/scala/com/salesforce/op/stages/impl/feature/MultiPickListMapVectorizer.scala | 7.1 | Mixed | Code Duplication: Edited copy of a member (27 corresponding lines) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 50 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 50 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 613 of 826 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Maven tree, and its score reflects currency alone.
- 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 313 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 9 of the 401 production source files in this repository: 88 are under the ~2,400-byte size floor this dimension measures over, and the remaining 304 have no attributable history left to measure.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `utils/src/main/scala/com/salesforce/op/utils/json/EnumEntrySerializer.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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FeatureTypeFactory.newInstanceFn at 105. A further 9 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 Transmogrifier.transmogrify at 54 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: core/src/main/scala/com/salesforce/op/stages/impl/feature/Transmogrifier.scala (Transmogrifier.transmogrify at 54), features/src/main/scala/com/salesforce/op/aggregators/MonoidAggregatorDefaults.scala (MonoidAggregatorDefaults.aggregatorOf at 54), features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala (FeatureSparkTypes.sparkTypeOf at 54), features/src/main/scala/com/salesforce/op/features/types/FeatureTypeDefaults.scala (FeatureTypeDefaults.default at 52), local/src/main/scala/com/salesforce/op/local/MLeapModelConverter.scala (MLeapModelConverter.modelToFunction at 37), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with FeatureTypeFactory.newInstanceFn (cyclomatic 105), FeatureTypeSparkConverter.fromSparkFn (cyclomatic 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.4 to about 8.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was FeatureTypeFactory.newInstanceFn at 155.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with FeatureTypeFactory.newInstanceFn (cognitive 155). — Refactoring it lifts Cognitive Complexity from 6.3 to about 7.3/10.
D3 · God Classes
7 god class(es) detected.
What to do
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with FeatureBuilder.scala, OpXGBoostClassifier.scala, OpXGBoostRegressor.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with ModelInsights.scala, RichMapFeature.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with FeatureTypeFactory.scala. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
35 duplicated block group(s) detected. 3.2 % of the production lines (1,781 of 55,548) are in a reported copy. A further 41 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with ModelInsights.scala, BinaryClassificationModelSelector.scala, MultiPickListMapVectorizer.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with SwQuaternaryEstimator.scala, RichNumericFeature.scala, FeatureSparkTypes.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with SwQuaternaryTransformer.scala, FeatureSparkTypes.scala, OpMultiClassificationEvaluator.scala. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
11 production modules (Gradle+Maven), 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; 1 module(s) off the main sequence, with abstractness counted on 9 of the 11 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
3 of 90 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with OpLDA.scala, OpCountVectorizer.scala, OpWorkflowModel.scala. — One of this dimension's main actionable groups (3 warning-level).
D12 · Dependency Hygiene
203 outdated artifact(s) of 237 resolved by the build, graded against Maven Central. The poms themselves state a version for only 60 of 104 declaration(s) — the rest are parent- or BOM-managed, which is why this is read from the resolved graph rather than from the manifests. 1 resolved artifact(s) could not be graded: Maven Central carries no such coordinate, or it publishes nothing but pre-releases. That is a definite answer and is counted, not charged. Whether any of these is DEPRECATED is not graded — Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Known CVEs in this graph are D30's question, read from the manifest there.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 39 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 11 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. 44 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
101 deducted task-comment markers across 55548 LoC (0.2/KLoC) → score 9.6. 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 101 TodoComment finding(s) in Explicit Debt — start with Transmogrifier.scala (14), RawFeatureFilterTest.scala (11), CliFullCycleTest.scala (6). — One of this dimension's main actionable groups (101 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 9 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
3 of 9 build units (Gradle, Maven) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
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)
semgrep found no security issues. semgrep hit a parse error in 3 file(s) — `gradlew` (lines 145–146, line 147, line 148, …), `helloworld/gradlew` (lines 145–146, line 147, line 148, …), `templates/simple/gradlew` (lines 145–146, line 147, line 148, …) — 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.
D30 · Dependency Vulnerabilities
32 finding(s): 11 critical, 15 high, 5 medium, 1 low.
What to do
- Resolve the 15 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-level).
- Resolve the 11 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
D34 · Knowledge Freshness
313 of 313 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/com/salesforce/op/dsl/RichMapFeature.scala. Counted over 313 of the 401 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 310 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (3), spark.gradle (3), Maps.scala (2). — One of this dimension's main actionable groups (310 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with RichMapFeature.scala, RichTextFeature.scala, ModelInsights.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.
D36 · Supply-chain Provenance & Signing
1/3 supply-chain integrity signals present (provenance, signing, SBOM).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 66 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
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
- `BaseStageMetrics` declares 25 abstract members: `numTasks`, `numAccumulables`, `executorRunTime`, `executorCpuTime`, `executorDeserializeTime`, `executorDeserializeCpuTime`, `resultSerializationTime`, `jvmGCTime`, `resultSizeBytes`, `numUpdatedBlockStatuses`, `diskBytesSpilled`, `memoryBytesSpilled`, `recordsRead`, `bytesRead`, `recordsWritten`, `bytesWritten`, `shuffleFetchWaitTime`, `shuffleTotalBytesRead`, `shuffleTotalBlocksFetched`, `shuffleLocalBlocksFetched`, `shuffleRemoteBlocksFetched`, `shuffleWriteTime`, `shuffleBytesWritten`, `shuffleRecordsWritten`, `duration`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — utils/src/main/scala/com/salesforce/op/utils/spark/OpSparkListener.scala:199
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX7 · Slice cohesion
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. (×12) — cli/src/main/scala/com/salesforce/op/cli/CliExec.scala:33, cli/src/main/scala/com/salesforce/op/cli/gen/templates/SampleObject.scala:33, core/src/main/scala/com/salesforce/op/dsl/RichNumericFeature.scala:468, …
- `ignore`'s body only throws NotImplementedError — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — cli/src/main/scala/com/salesforce/op/cli/gen/templates/SampleObject.scala:35
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×8) — core/src/test/scala/com/salesforce/op/evaluators/OpMultiClassificationEvaluatorTest.scala:292, core/src/test/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelectorTest.scala:136, core/src/test/scala/com/salesforce/op/stages/impl/classification/MultiClassificationModelSelectorTest.scala:194, …
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
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 4/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cli`, `helloworld`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` 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`. (×2) — utils/src/main/scala/com/salesforce/op/test/TestCommon.scala:108, utils/src/main/scala/com/salesforce/op/test/TestCommon.scala:135
- `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`. — cli/src/main/scala/com/salesforce/op/cli/gen/Ops.scala:94
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.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 201 is called with an argument built by `rawFeatures.map(_.name).mkString("…")` (line 202), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — readers/src/main/scala/com/salesforce/op/readers/JoinedDataReader.scala:201
- `debug` at line 270 is called with an argument built by `leftCols.mkString("…")` (line 270), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — readers/src/main/scala/com/salesforce/op/readers/JoinedDataReader.scala:270
- `debug` at line 288 is called with an argument built by `leftFeatures.map(_.name).mkString("…")` (line 289), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — readers/src/main/scala/com/salesforce/op/readers/JoinedDataReader.scala:288
What to do
- In Scala, put the construction behind the logger's own check (`if (log.isDebugEnabled)`), or log through a logger that takes the message by name or by macro and so builds it only when the level is on — scala-logging's `LazyLogging`/`StrictLogging` (`logger.debug(s"rows: ${rows.mkString(", ")}")` expands to that check), log4s or log4cats. Interpolating into an `s"…"` is not the fix on SLF4J or Akka's `LoggingAdapter`: their `debug` takes a `String`, so the interpolation and every `mkString` inside it run before the call is entered.
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — core/src/main/scala/com/salesforce/op/utils/text/LuceneTextAnalyzer.scala:117
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
- `debug` at line 385 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — features/src/main/scala/com/salesforce/op/features/FeatureLike.scala:385
- `info` at line 500 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/ModelInsights.scala:500
- `debug` at line 106 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/OpWorkflow.scala:106
- `info` at line 155 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/OpWorkflow.scala:155
- `error` at line 195 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/OpWorkflow.scala:195
- `info` at line 199 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/OpWorkflow.scala:199
- `debug` at line 220 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/OpWorkflow.scala:220
- `info` at line 153 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. (×2) — core/src/main/scala/com/salesforce/op/utils/stages/FitStagesUtil.scala:153, core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:153
- `info` at line 166 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:166
- `info` at line 211 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:211
- `info` at line 226 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:226
- `info` at line 237 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:237
- `info` at line 260 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:260
- `info` at line 105 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataCutter.scala:105
- `info` at line 168 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataCutter.scala:168
- `info` at line 80 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:80
- `info` at line 81 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:81
- `info` at line 82 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:82
- `info` at line 117 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:117
- `info` at line 322 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpValidator.scala:322
- `warn` at line 325 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpValidator.scala:325
- `info` at line 337 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpValidator.scala:337
- `info` at line 338 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpValidator.scala:338
- `warn` at line 99 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/stages/impl/tuning/Splitter.scala:99
- `info` at line 314 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/filters/RawFeatureFilter.scala:314
- `info` at line 154 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — core/src/main/scala/com/salesforce/op/evaluators/OpRegressionEvaluator.scala:154
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 392 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 | 56% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 57% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 69% | Adequate | Strongest area. |
| Security | 85% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not 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 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 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.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~42432 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .scala test runner
- 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 does not read sc yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 505 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 384 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java 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
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 27 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
- REDACTED
- REDACTED
Serious — 220 finding(s)
- TodoComment utils/src/main/scala/com/salesforce/op/utils/stats/OpStatistics.scala:83
- TodoComment utils/src/main/scala/com/salesforce/op/utils/stats/OpStatistics.scala:254
- TodoComment utils/src/main/scala/com/salesforce/op/utils/stats/OpStatistics.scala:255
- TodoComment utils/src/main/scala/com/salesforce/op/utils/stats/OpStatistics.scala:374
- TodoComment utils/src/main/scala/com/salesforce/op/utils/spark/OpSparkListener.scala:296
- TodoComment utils/src/main/scala/com/salesforce/op/utils/spark/SequenceAggregators.scala:45
- TodoComment testkit/src/main/scala/com/salesforce/op/testkit/RandomList.scala:107
- TodoComment testkit/src/main/scala/com/salesforce/op/test/FeatureAsserts.scala:82
- TodoComment readers/src/test/scala/com/salesforce/op/readers/DataReadersTest.scala:121
- TodoComment readers/src/main/scala/com/salesforce/op/readers/DataReader.scala:345
- TodoComment local/src/test/scala/com/salesforce/op/local/MLeapModelConverterTest.scala:46
- TodoComment local/src/main/scala/com/salesforce/op/local/MLeapModelConverter.scala:49
- TodoComment local/src/main/scala/com/salesforce/op/local/OpWorkflowModelLocal.scala:84
- TodoComment features/src/main/scala/com/salesforce/op/utils/spark/OpVectorColumnMetadata.scala:67
- TodoComment features/src/main/scala/com/salesforce/op/utils/spark/OpVectorMetadata.scala:55
- TodoComment features/src/main/scala/com/salesforce/op/utils/spark/RichDataset.scala:234
- TodoComment features/src/main/scala/com/salesforce/op/test/OpEstimatorSpec.scala:102
- TodoComment features/src/main/scala/com/salesforce/op/test/OpPipelineStageSpec.scala:129
- TodoComment features/src/main/scala/com/salesforce/op/stages/SparkStageParam.scala:171
- TodoComment features/src/main/scala/com/salesforce/op/features/FeatureJsonHelper.scala:121
- TodoComment features/src/main/scala/com/salesforce/op/features/FeatureLike.scala:294
- TodoComment features/src/main/scala/com/salesforce/op/features/types/Text.scala:85
- TodoComment features/src/main/scala/com/salesforce/op/features/types/Text.scala:87
- TodoComment features/src/main/scala/com/salesforce/op/aggregators/MonoidAggregatorDefaults.scala:51
- TodoComment features/src/main/scala/com/salesforce/op/aggregators/MonoidAggregatorDefaults.scala:92
- Duplicated block (6 lines × 2) core/src/main/scala/com/salesforce/op/ModelInsights.scala:704
- Duplicated block (6 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala:95
- Duplicated block (6 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/feature/MultiPickListMapVectorizer.scala:59
- Duplicated block (6 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/feature/DateMapToUnitCircleVectorizer.scala:122
- Duplicated block (6 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/feature/SmartTextMapVectorizer.scala:163
- Duplicated block (6 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/feature/IntegralVectorizer.scala:70
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: FeatureBuilder features/src/main/scala/com/salesforce/op/features/FeatureBuilder.scala:48
- TooManyMethods: OpXGBoostClassifier core/src/main/scala/com/salesforce/op/stages/impl/classification/OpXGBoostClassifier.scala:47
- TooManyMethods: OpXGBoostRegressor core/src/main/scala/com/salesforce/op/stages/impl/regression/OpXGBoostRegressor.scala:48
- TooManyMethods: SanityCheckerParams core/src/main/scala/com/salesforce/op/stages/impl/preparators/SanityChecker.scala:58
- Edited copy of a member (15 corresponding lines) core/src/main/scala/com/salesforce/op/stages/sparkwrappers/generic/SwQuaternaryEstimator.scala:92
- Edited copy of a member (15 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichNumericFeature.scala:324
- Edited copy of a member (15 corresponding lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:444
- Edited copy of a member (15 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/regression/RegressionModelSelector.scala:164
- Edited copy of a member (9 corresponding lines) core/src/main/scala/com/salesforce/op/stages/sparkwrappers/generic/SwQuaternaryTransformer.scala:70
- Edited copy of a member (9 corresponding lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:345
- Edited copy of a member (9 corresponding lines) core/src/main/scala/com/salesforce/op/evaluators/OpMultiClassificationEvaluator.scala:494
- Edited copy of a member (12 corresponding lines) core/src/main/scala/com/salesforce/op/stages/sparkwrappers/generic/SwSequenceEstimator.scala:75
- Edited copy of a member (12 corresponding lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:368
- Edited copy of a member (12 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/OPMapVectorizer.scala:125
- Edited copy of a member (11 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/DateMapToUnitCircleVectorizer.scala:122
- Edited copy of a member (11 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/IntegralVectorizer.scala:104
- Edited copy of a member (11 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:1049
- Edited copy of a member (13 corresponding lines) features/src/main/scala/com/salesforce/op/stages/base/binary/BinaryEstimator.scala:99
- Edited copy of a member (13 corresponding lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:470
- Edited copy of a member (13 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:101
- Duplicated block (15 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala:110
- Duplicated block (15 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/feature/TextMapLenEstimator.scala:52
- Duplicated block (15 lines × 2) features/src/main/scala/com/salesforce/op/OpParams.scala:178
- Low cohesion: OpLDA (LCOM4 8) core/src/main/scala/com/salesforce/op/stages/impl/feature/OpLDA.scala:41
- Low cohesion: OpCountVectorizer (LCOM4 5) core/src/main/scala/com/salesforce/op/stages/impl/feature/OpCountVectorizer.scala:44
- Low cohesion: OpWorkflowModel (LCOM4 4) core/src/main/scala/com/salesforce/op/OpWorkflowModel.scala:60
- Disposable created and abandoned in the function that made it utils/src/main/scala/com/salesforce/op/test/TestCommon.scala:108
- Disposable created and abandoned in the function that made it utils/src/main/scala/com/salesforce/op/test/TestCommon.scala:135
- Disposable created and abandoned in the function that made it cli/src/main/scala/com/salesforce/op/cli/gen/Ops.scala:94
- FileTooLong: op/ModelInsights.scala core/src/main/scala/com/salesforce/op/ModelInsights.scala
- FileTooLong: dsl/RichMapFeature.scala core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala
- Edited copies of one member (3 members, 17+ corresponding lines) core/src/main/scala/com/salesforce/op/evaluators/Evaluators.scala:130
- Edited copies of one member (3 members, 17+ corresponding lines) features/src/main/scala/com/salesforce/op/OpParams.scala:178
- Edited copy of a member (10 corresponding lines) utils/src/main/scala/com/salesforce/op/utils/spark/SequenceAggregators.scala:143
- Edited copy of a member (10 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/PhoneNumberParser.scala:149
- Edited copy of a member (20 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:608
- Edited copy of a member (20 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:163
- Edited copy of a member (8 corresponding lines) features/src/main/scala/com/salesforce/op/stages/base/sequence/BinarySequenceTransformer.scala:78
- Edited copy of a member (8 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/DropIndicesByTransformer.scala:65
- Edited copies of one member (3 members, 7+ corresponding lines) core/src/main/scala/com/salesforce/op/stages/sparkwrappers/generic/SwBinaryTransformer.scala:64
- Edited copies of one member (3 members, 7+ corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/GeolocationVectorizer.scala:117
- Duplicated block (14 lines × 2) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:614
- Duplicated block (14 lines × 2) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:174
- Duplicated block (12 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala:78
- Duplicated block (12 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataCutter.scala:151
- Duplicated block (10 lines × 2) helloworld/src/main/scala/com/salesforce/hw/OpBostonSimple.scala:150
- Duplicated block (10 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/feature/SmartTextMapVectorizer.scala:74
- Duplicated block (8 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/feature/MultiPickListMapVectorizer.scala:71
- Duplicated block (8 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/preparators/MinVarianceFilter.scala:114
- Duplicated block (7 lines × 2) core/src/main/scala/com/salesforce/op/ModelInsights.scala:811
- Duplicated block (7 lines × 2) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:164
- Duplicated block (5 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala:85
- Duplicated block (5 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/classification/MultiClassificationModelSelector.scala:103
- FeatureTypeFactory.newInstanceFn (cyclomatic 105) features/src/main/scala/com/salesforce/op/features/types/FeatureTypeFactory.scala:78
- FeatureTypeSparkConverter.fromSparkFn (cyclomatic 34) features/src/main/scala/com/salesforce/op/features/types/FeatureTypeSparkConverter.scala:142
- ModelInsights.getFeatureInsights (cyclomatic 20) core/src/main/scala/com/salesforce/op/ModelInsights.scala:571
- PreparedFeatures.prepareFeature (cyclomatic 20) core/src/main/scala/com/salesforce/op/filters/PreparedFeatures.scala:164
- ModelInsights.getModelContributions (cyclomatic 19) core/src/main/scala/com/salesforce/op/ModelInsights.scala:786
- SanityChecker.fitFn (cyclomatic 19) core/src/main/scala/com/salesforce/op/stages/impl/preparators/SanityChecker.scala:367
- NumericBucketizer.bucketize (cyclomatic 17) core/src/main/scala/com/salesforce/op/stages/impl/feature/NumericBucketizer.scala:219
- FeatureTypeFactory.newInstanceFn (cognitive 155) features/src/main/scala/com/salesforce/op/features/types/FeatureTypeFactory.scala:78
- OpWorkflowModelReader.loadJson (cognitive 45) core/src/main/scala/com/salesforce/op/OpWorkflowModelReader.scala:129
- ModelInsights.getFeatureInsights (cognitive 32) core/src/main/scala/com/salesforce/op/ModelInsights.scala:571
- MapHashingFun.makeVectorColumnMetadata (cognitive 31) core/src/main/scala/com/salesforce/op/stages/impl/feature/OPCollectionHashingVectorizer.scala:315
- FeatureTypeSparkConverter.fromSparkFn (cognitive 29) features/src/main/scala/com/salesforce/op/features/types/FeatureTypeSparkConverter.scala:142
- SanityChecker.fitFn (cognitive 25) core/src/main/scala/com/salesforce/op/stages/impl/preparators/SanityChecker.scala:367
- NumericBucketizer.bucketize (cognitive 24) core/src/main/scala/com/salesforce/op/stages/impl/feature/NumericBucketizer.scala:219
- OpBinaryClassificationEvaluator.evaluateAll (cognitive 23) core/src/main/scala/com/salesforce/op/evaluators/OpBinaryClassificationEvaluator.scala:67
- SanityChecker.categoricalTests (cognitive 19) core/src/main/scala/com/salesforce/op/stages/impl/preparators/SanityChecker.scala:252
- FeatureLike.parentStages (cognitive 19) features/src/main/scala/com/salesforce/op/features/FeatureLike.scala:370
- StreamingHistogramBuilder.flushHistogram (cognitive 19) utils/src/main/java/com/salesforce/op/utils/stats/StreamingHistogram.java:202
- ModelInsights.getModelContributions (cognitive 17) core/src/main/scala/com/salesforce/op/ModelInsights.scala:786
- DateListVectorizer.onGetMetadata (cognitive 17) core/src/main/scala/com/salesforce/op/stages/impl/feature/DateListVectorizer.scala:261
- MapHashingFun.hash (cognitive 17) core/src/main/scala/com/salesforce/op/stages/impl/feature/OPCollectionHashingVectorizer.scala:368
- OpWorkflow.setBlocklist (cognitive 16) core/src/main/scala/com/salesforce/op/OpWorkflow.scala:118
- HashingFun.prepare (cognitive 16) core/src/main/scala/com/salesforce/op/stages/impl/feature/OPCollectionHashingVectorizer.scala:284
- MethodTooLong: FeatureTypeFactory.newInstanceFn features/src/main/scala/com/salesforce/op/features/types/FeatureTypeFactory.scala:78
- Near-duplicate member pair (54 shared lines) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:126
- Edited copy of a member (56 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala:71
- Edited copy of a member (31 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:217
- Edited copy of a member (27 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/MultiPickListMapVectorizer.scala:58
- Edited copy of a member (22 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/MultiPickListMapVectorizer.scala:99
- Edited copy of a member (17 corresponding lines) features/src/main/scala/com/salesforce/op/stages/base/quaternary/QuaternaryEstimator.scala:115
- Edited copy of a member (28 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/TextMapLenEstimator.scala:48
- Edited copies of one member (3 members, 28+ corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:310
- Edited copy of a member (18 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:784
- Edited copies of one member (3 members, 6+ corresponding lines) features/src/main/scala/com/salesforce/op/stages/base/binary/BinaryTransformer.scala:78
- Edited copy of a member (6 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichDateFeature.scala:115
- Edited copies of one member (3 members, 14+ corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/feature/DateMapToUnitCircleVectorizer.scala:71
- Edited copies of one member (4 members, 15+ corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelector.scala:181
- Edited copy of a member (4 corresponding lines) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:1011
- Edited copy of a member (2 corresponding lines) core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:54
- Duplicated block (25 lines × 2) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:313
- Duplicated block (18 lines × 3) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:316
- Duplicated block (17–18 lines × 2) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:219
- Duplicated block (25–26 lines × 3) helloworld/src/main/scala/com/salesforce/hw/OpBostonSimple.scala:152
- Duplicated block (16 lines × 2) core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:786
- Duplicated block (12–13 lines × 2) core/src/main/scala/com/salesforce/op/evaluators/Evaluators.scala:136
- Duplicated block (11 lines × 2) core/src/main/scala/com/salesforce/op/dsl/RichNumericFeature.scala:328
- Duplicated block (8–9 lines × 3) core/src/main/scala/com/salesforce/op/evaluators/Evaluators.scala:133
- Duplicated block (9 lines × 2) core/src/main/scala/com/salesforce/op/evaluators/OpBinaryClassificationEvaluator.scala:74
- Duplicated block (8–9 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/feature/MultiPickListMapVectorizer.scala:99
- Duplicated block (33–35 lines × 2) features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:126
- Duplicated block (39 lines × 4) core/src/main/scala/com/salesforce/op/stages/impl/classification/OpDecisionTreeClassifier.scala:52
- Duplicated block (65 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/classification/OpGBTClassifier.scala:52
- Duplicated block (55 lines × 2) core/src/main/scala/com/salesforce/op/stages/impl/classification/OpRandomForestClassifier.scala:64
- Off the main sequence: transmogrifai:utils
- Swallowed exception (empty catch) core/src/main/scala/com/salesforce/op/utils/text/LuceneTextAnalyzer.scala:117
Minor — 376 finding(s)
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/feature/Transmogrifier.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/preparators/SanityChecker.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/filters/RawFeatureFilter.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/dsl/RichNumericFeature.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/evaluators/OpMultiClassificationEvaluator.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/OpWorkflow.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/utils/stages/NameDetectUtils.scala:1
- Orphaned file features/src/main/scala/com/salesforce/op/features/FeatureSparkTypes.scala:1
- Orphaned file features/src/main/scala/com/salesforce/op/features/FeatureBuilder.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/feature/SmartTextMapVectorizer.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/feature/SmartTextVectorizer.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/OpWorkflowModel.scala:1
- Orphaned file features/src/main/scala/com/salesforce/op/utils/spark/RichDataset.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/preparators/DerivedFeatureFilterUtils.scala:1
- Orphaned file utils/src/main/scala/com/salesforce/op/utils/stats/OpStatistics.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/OpWorkflowRunner.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/feature/PhoneNumberParser.scala:1
- Orphaned file features/src/main/scala/com/salesforce/op/stages/OpPipelineStages.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/feature/OPMapVectorizer.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/preparators/SanityCheckerMetadata.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/feature/OpOneHotVectorizer.scala:1
- Orphaned file readers/src/main/scala/com/salesforce/op/readers/JoinedDataReader.scala:1
- Orphaned file features/src/main/scala/com/salesforce/op/features/FeatureLike.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/classification/OpXGBoostClassifier.scala:1
- Orphaned file core/src/main/scala/com/salesforce/op/stages/impl/feature/OPCollectionHashingVectorizer.scala:1
- Interpolated log message defeats structured logging features/src/main/scala/com/salesforce/op/features/FeatureLike.scala:385
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/ModelInsights.scala:500
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/OpWorkflow.scala:106
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/OpWorkflow.scala:155
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/OpWorkflow.scala:195
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/OpWorkflow.scala:199
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/OpWorkflow.scala:220
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/utils/stages/FitStagesUtil.scala:153
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:153
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:166
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:211
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:226
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:237
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataBalancer.scala:260
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataCutter.scala:105
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/DataCutter.scala:168
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:80
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:81
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:82
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpCrossValidation.scala:117
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpValidator.scala:322
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpValidator.scala:325
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpValidator.scala:337
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/OpValidator.scala:338
- Interpolated log message defeats structured logging core/src/main/scala/com/salesforce/op/stages/impl/tuning/Splitter.scala:99
- Blanket warning suppression cli/src/main/scala/com/salesforce/op/cli/CliExec.scala:33
- Blanket warning suppression cli/src/main/scala/com/salesforce/op/cli/gen/templates/SampleObject.scala:33
- Blanket warning suppression core/src/main/scala/com/salesforce/op/dsl/RichNumericFeature.scala:468
- Blanket warning suppression core/src/main/scala/com/salesforce/op/stages/impl/feature/PhoneNumberParser.scala:324
- Blanket warning suppression features/src/main/scala/com/salesforce/op/aggregators/CutOffTime.scala:46
- Blanket warning suppression features/src/main/scala/com/salesforce/op/features/FeatureBuilder.scala:49
- Blanket warning suppression features/src/main/scala/com/salesforce/op/features/FeatureBuilderMacros.scala:43
- Blanket warning suppression features/src/main/scala/com/salesforce/op/features/types/Text.scala:88
- Blanket warning suppression utils/src/main/scala/com/fasterxml/jackson/module/scala/OpDefaultScalaModule.scala:26
- Blanket warning suppression utils/src/main/scala/com/fasterxml/jackson/module/scala/deser/OpSortedMapDeserializerModule.scala:38
- Blanket warning suppression utils/src/main/scala/com/fasterxml/jackson/module/scala/deser/OpUnsortedMapDeserializerModule.scala:37
- Blanket warning suppression utils/src/main/scala/com/salesforce/op/utils/json/SpecialDoubleSerializer.scala:39
- Disabled test core/src/test/scala/com/salesforce/op/evaluators/OpMultiClassificationEvaluatorTest.scala:292
- Disabled test core/src/test/scala/com/salesforce/op/stages/impl/classification/BinaryClassificationModelSelectorTest.scala:136
- Disabled test core/src/test/scala/com/salesforce/op/stages/impl/classification/MultiClassificationModelSelectorTest.scala:194
- Disabled test core/src/test/scala/com/salesforce/op/stages/impl/preparators/BadFeatureZooTest.scala:108
- Disabled test core/src/test/scala/com/salesforce/op/stages/impl/regression/RegressionModelSelectorTest.scala:174
- Disabled test core/src/test/scala/com/salesforce/op/stages/impl/regression/RegressionModelSelectorTest.scala:473
- Disabled test core/src/test/scala/com/salesforce/op/stages/impl/regression/RegressionModelSelectorTest.scala:492
- Disabled test core/src/test/scala/com/salesforce/op/stages/impl/regression/RegressionModelSelectorTest.scala:515
- Most significant orphaned file core/src/main/scala/com/salesforce/op/dsl/RichMapFeature.scala:1
- Most significant orphaned file core/src/main/scala/com/salesforce/op/dsl/RichTextFeature.scala:1
- Most significant orphaned file core/src/main/scala/com/salesforce/op/ModelInsights.scala:1
- Diagnostic log message is built whether or not it is wanted readers/src/main/scala/com/salesforce/op/readers/JoinedDataReader.scala:201
- Diagnostic log message is built whether or not it is wanted readers/src/main/scala/com/salesforce/op/readers/JoinedDataReader.scala:270
- Diagnostic log message is built whether or not it is wanted readers/src/main/scala/com/salesforce/op/readers/JoinedDataReader.scala:288
- Fat interface: BaseStageMetrics (25 abstract members) utils/src/main/scala/com/salesforce/op/utils/spark/OpSparkListener.scala:199
- No ADRs found REDACTED:36
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- Method throws NotImplementedError cli/src/main/scala/com/salesforce/op/cli/gen/templates/SampleObject.scala:35
- No ADRs
- Logging is not universal
- Scala's null is not held to the type system everywhere
Minor — 203 finding(s)
- Outdated (compile): org.scalanlp:breeze_2.11
- Outdated (compile): org.lz4:lz4-java
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): com.fasterxml.jackson.module:jackson-module-paranamer
- Outdated (compile): org.apache.parquet:parquet-column
- Outdated (compile): org.apache.commons:commons-compress
- Outdated (compile): org.typelevel:machinist_2.11
- Outdated (compile): org.scalameta:dialects_2.11
- Outdated (compile): org.glassfish.jersey.bundles.repackaged:jersey-guava
- Outdated (compile): org.apache.commons:commons-crypto
- Outdated (compile): org.yaml:snakeyaml
- Outdated (compile): commons-beanutils:commons-beanutils
- Outdated (compile): org.scalameta:inline_2.11
- Outdated (compile): xml-apis:xml-apis
- Outdated (compile): org.apache.orc:orc-shims
- Outdated (compile): org.scalameta:common_2.11
- Outdated (compile): com.trueaccord.lenses:lenses_2.11
- Outdated (compile): org.scalameta:scalameta_2.11
- Outdated (compile): org.glassfish.jersey.core:jersey-common
- Outdated (compile): com.googlecode.libphonenumber:carrier
- Outdated (compile): org.objenesis:objenesis
- Outdated (compile): com.beachape:enumeratum_2.11
- Outdated (compile): org.apache.orc:orc-mapreduce
- Outdated (compile): commons-net:commons-net
- Outdated (compile): org.apache.spark:spark-launcher_2.11
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-151967f0a64c48e8b86227986d28ef24/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-151967f0a64c48e8b86227986d28ef24/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude docs . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 32 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `utils/src/main/scala/com/salesforce/op/utils/json/EnumEntrySerializer.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |