Executive summary
awslabs/deequ is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no recorded design decisions and no architecture document or diagram, and 83 files are no longer known to anyone active in the project. It scores 61 out of 100, which the At risk rating leaves unchanged.
Maturity, at 55, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the two packages under a banned licence, worth about 4 points. Recording design decisions would lift Maturity itself, worth about 5 points. Raising Maturity to 70 would lift the score to about 66.
Thirteen known security holes in the packages the code depends on can be used by attackers. Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two packages carry licence risk. Updating the vulnerable packages, pinning each tool to an exact version and replacing or clearing the banned-licence packages would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the password or key in the code's history needs replacing, with the old one switched off.
The product code is 21,953 lines, about €51,000 to rebuild.
If Maturity rose from 55 to 70, the lowest score rated Strong, the score would rise from 61 to about 66.
New since the last survey: 19 findings
- Code Duplication · Edited copy of a member (18 corresponding lines) src/main/scala/com/amazon/deequ/dqdl/translation/rules/IsUniqueRule.scala
- Code Duplication · Edited copy of a member (27 corresponding lines) src/main/scala/com/amazon/deequ/constraints/Constraint.scala
- Code Duplication · Edited copy of a member (18 corresponding lines) src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala
- Code Duplication · Edited copy of a member (22 corresponding lines) src/main/scala/com/amazon/deequ/metrics/HistogramBinnedMetric.scala
- Code Duplication · Edited copy of a member (18 corresponding lines) src/main/scala/com/amazon/deequ/dqdl/execution/executors/RowCountMatchExecutor.scala
- Code Duplication · Edited copy of a member (14 corresponding lines) src/main/scala/com/amazon/deequ/analyzers/UniqueValueRatio.scala
- Code Duplication · Edited copy of a member (19 corresponding lines) src/main/scala/com/amazon/deequ/analyzers/catalyst/StatefulHyperloglogPlus.scala
- Code Duplication · Edited copy of a member (19 corresponding lines) src/main/scala/com/amazon/deequ/suggestions/rules/CategoricalRangeRule.scala
- Code Duplication · Edited copy of a member (12 corresponding lines) src/main/scala/com/amazon/deequ/analyzers/MaxLength.scala
- Code Duplication · Edited copy of a member (25 corresponding lines) src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunBuilder.scala
- Code Duplication · Edited copy of a member (16 corresponding lines) src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunner.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnCountRule.scala
- Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) src/main/scala/com/amazon/deequ/constraints/Constraint.scala
- Code Duplication · Edited copies of one member (5 members, 15+ corresponding lines) src/main/scala/com/amazon/deequ/analyzers/Correlation.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) src/main/scala/com/amazon/deequ/analyzers/StandardDeviation.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) src/main/scala/com/amazon/deequ/dqdl/translation/rules/SchemaMatchRule.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) src/main/scala/com/amazon/deequ/dqdl/execution/executors/ColumnDataTypeExecutor.scala
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (10–11 lines × 2) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnValuesRule.scala
- Code Duplication · Duplicated block (9 lines × 2) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnValuesRule.scala
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Change Coupling · Change coupling: ColumnProfiler.scala ↔ ConstraintSuggestionRunner.scala src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala
Rebuild cost: about €51,000 · Estimate
| Cost to rebuild | €17,000 to €85,000, for 281 to 892 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 21,953 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 com.amazon.deequ.VerificationResult | 2 com.amazon.deequ.analyzers.Distance | 3 com.amazon.deequ.analyzers.FilteredRowOutcome | 4 com.amazon.deequ.analyzers.Histogram | 5 com.amazon.deequ.analyzers.runners.AnalyzerContext | 6 com.amazon.deequ.anomalydetection.OnlineNormalStrategy | 7 com.amazon.deequ.anomalydetection.seasonal | 8 com.amazon.deequ.anomalydetection.seasonal.HoltWinters | 9 com.amazon.deequ.comparison | 10 com.amazon.deequ.constraints.AnalysisBasedConstraint | 11 com.amazon.deequ.io | 12 com.amazon.deequ.metrics | 13 com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy | 14 com.amazon.deequ.anomalydetection | 15 com.amazon.deequ.repository | 16 com.amazon.deequ.suggestions.rules.interval | 17 com.amazon.deequ.analyzers.runners | 18 com.amazon.deequ.analyzers | 19 com.amazon.deequ.analyzers.catalyst | 20 com.amazon.deequ.constraints | 21 com.amazon.deequ.profiles | 22 com.amazon.deequ.repository.fs | 23 com.amazon.deequ.repository.memory | 24 com.amazon.deequ.repository.sparktable | 25 org.apache.spark.sql | 26 org.apache.spark.sql.catalyst.expressions.aggregate | 27 com.amazon.deequ.analyzers.applicability | 28 com.amazon.deequ.checks | 29 com.amazon.deequ.suggestions.rules | 30 com.amazon.deequ | 31 com.amazon.deequ.dqdl.model | 32 com.amazon.deequ.dqdl | 33 com.amazon.deequ.dqdl.execution | 34 com.amazon.deequ.dqdl.execution.DQDLExecutor | 35 com.amazon.deequ.dqdl.execution.executors | 36 com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor | 37 com.amazon.deequ.dqdl.translation | 38 com.amazon.deequ.dqdl.util | 39 com.amazon.deequ.suggestions | 40 com.amazon.deequ.dqdl.translation.rules |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.amazon.deequ.VerificationResult | ||||||||||||||||||||||||||||||||||||||||
| 2 com.amazon.deequ.analyzers.Distance | ||||||||||||||||||||||||||||||||||||||||
| 3 com.amazon.deequ.analyzers.FilteredRowOutcome | ||||||||||||||||||||||||||||||||||||||||
| 4 com.amazon.deequ.analyzers.Histogram | ||||||||||||||||||||||||||||||||||||||||
| 5 com.amazon.deequ.analyzers.runners.AnalyzerContext | ||||||||||||||||||||||||||||||||||||||||
| 6 com.amazon.deequ.anomalydetection.OnlineNormalStrategy | ||||||||||||||||||||||||||||||||||||||||
| 7 com.amazon.deequ.anomalydetection.seasonal | ||||||||||||||||||||||||||||||||||||||||
| 8 com.amazon.deequ.anomalydetection.seasonal.HoltWinters | ||||||||||||||||||||||||||||||||||||||||
| 9 com.amazon.deequ.comparison | ||||||||||||||||||||||||||||||||||||||||
| 10 com.amazon.deequ.constraints.AnalysisBasedConstraint | ||||||||||||||||||||||||||||||||||||||||
| 11 com.amazon.deequ.io | ||||||||||||||||||||||||||||||||||||||||
| 12 com.amazon.deequ.metrics | ||||||||||||||||||||||||||||||||||||||||
| 13 com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy | ||||||||||||||||||||||||||||||||||||||||
| 14 com.amazon.deequ.anomalydetection | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 com.amazon.deequ.repository | 1 | 9 | 4 | 7 | ||||||||||||||||||||||||||||||||||||
| 16 com.amazon.deequ.suggestions.rules.interval | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 com.amazon.deequ.analyzers.runners | 4 | 7 | 18 | |||||||||||||||||||||||||||||||||||||
| 18 com.amazon.deequ.analyzers | 3 | 32 | 2 | |||||||||||||||||||||||||||||||||||||
| 19 com.amazon.deequ.analyzers.catalyst | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 com.amazon.deequ.constraints | 5 | 5 | ||||||||||||||||||||||||||||||||||||||
| 21 com.amazon.deequ.profiles | 9 | 7 | 2 | 4 | ||||||||||||||||||||||||||||||||||||
| 22 com.amazon.deequ.repository.fs | 6 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 com.amazon.deequ.repository.memory | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 com.amazon.deequ.repository.sparktable | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 org.apache.spark.sql | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 org.apache.spark.sql.catalyst.expressions.aggregate | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 com.amazon.deequ.analyzers.applicability | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 com.amazon.deequ.checks | 4 | 1 | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 29 com.amazon.deequ.suggestions.rules | 1 | 2 | 13 | 14 | ||||||||||||||||||||||||||||||||||||
| 30 com.amazon.deequ | 5 | 2 | 8 | 1 | 10 | 2 | 5 | |||||||||||||||||||||||||||||||||
| 31 com.amazon.deequ.dqdl.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 com.amazon.deequ.dqdl | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 com.amazon.deequ.dqdl.execution | 4 | |||||||||||||||||||||||||||||||||||||||
| 34 com.amazon.deequ.dqdl.execution.DQDLExecutor | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 com.amazon.deequ.dqdl.execution.executors | 29 | |||||||||||||||||||||||||||||||||||||||
| 36 com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 com.amazon.deequ.dqdl.translation | 4 | |||||||||||||||||||||||||||||||||||||||
| 38 com.amazon.deequ.dqdl.util | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 com.amazon.deequ.suggestions | 5 | 2 | 3 | 8 | 6 | 3 | ||||||||||||||||||||||||||||||||||
| 40 com.amazon.deequ.dqdl.translation.rules | 1 | 2 | 11 | 25 |
14→12 com.amazon.deequ.anomalydetection uses com.amazon.deequ.metrics✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.anomalydetection uses a type in com.amazon.deequ.metrics.
- The types involved
com.amazon.deequ.anomalydetection.HistoryUtils→com.amazon.deequ.metrics.Metric
- Direction
- com.amazon.deequ.anomalydetection uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ.anomalydetection, while a change to com.amazon.deequ.anomalydetection can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ.anomalydetection uses a module listed above it, which is the healthy direction.
15→4 com.amazon.deequ.repository uses com.amazon.deequ.analyzers.Histogram✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.repository uses a type in com.amazon.deequ.analyzers.Histogram.
- The types involved
com.amazon.deequ.repository.AnalyzerDeserializer→com.amazon.deequ.analyzers.Histogram.AggregateFunction
- Direction
- com.amazon.deequ.repository uses com.amazon.deequ.analyzers.Histogram, so a change to com.amazon.deequ.analyzers.Histogram can break com.amazon.deequ.repository, while a change to com.amazon.deequ.repository can't break com.amazon.deequ.analyzers.Histogram.
- Position
- Below the diagonal: com.amazon.deequ.repository uses a module listed above it, which is the healthy direction.
15→12 com.amazon.deequ.repository uses com.amazon.deequ.metrics✕
- Connections
- 9 pairs of types, where a type in com.amazon.deequ.repository uses a type in com.amazon.deequ.metrics.
- The types involved
com.amazon.deequ.repository.AnalyzerDeserializer→com.amazon.deequ.metrics.Metriccom.amazon.deequ.repository.BucketDistributionDeserializer→com.amazon.deequ.metrics.BucketDistributioncom.amazon.deequ.repository.BucketDistributionSerializer→com.amazon.deequ.metrics.BucketDistributioncom.amazon.deequ.repository.DistributionBinnedDeserializer→com.amazon.deequ.metrics.DistributionBinnedcom.amazon.deequ.repository.DistributionBinnedSerializer→com.amazon.deequ.metrics.DistributionBinnedcom.amazon.deequ.repository.DistributionDeserializer→com.amazon.deequ.metrics.Distributioncom.amazon.deequ.repository.DistributionSerializer→com.amazon.deequ.metrics.Distributioncom.amazon.deequ.repository.MetricDeserializer→com.amazon.deequ.metrics.Metriccom.amazon.deequ.repository.MetricSerializer→com.amazon.deequ.metrics.Metric
- Direction
- com.amazon.deequ.repository uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ.repository, while a change to com.amazon.deequ.repository can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ.repository uses a module listed above it, which is the healthy direction.
15→17 com.amazon.deequ.repository uses com.amazon.deequ.analyzers.runners part of a loop✕
- Connections
- 4 pairs of types, where a type in com.amazon.deequ.repository uses a type in com.amazon.deequ.analyzers.runners.
- The types involved
com.amazon.deequ.repository.AnalysisResult→com.amazon.deequ.analyzers.runners.AnalyzerContextcom.amazon.deequ.repository.AnalyzerContextDeserializer→com.amazon.deequ.analyzers.runners.AnalyzerContextcom.amazon.deequ.repository.AnalyzerContextSerializer→com.amazon.deequ.analyzers.runners.AnalyzerContextcom.amazon.deequ.repository.MetricsRepository→com.amazon.deequ.analyzers.runners.AnalyzerContext
- Direction
- com.amazon.deequ.repository uses com.amazon.deequ.analyzers.runners, so a change to com.amazon.deequ.analyzers.runners can break com.amazon.deequ.repository, while a change to com.amazon.deequ.repository can't break com.amazon.deequ.analyzers.runners.
- 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→18 com.amazon.deequ.repository uses com.amazon.deequ.analyzers part of a loop✕
- Connections
- 7 pairs of types, where a type in com.amazon.deequ.repository uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.repository.AnalyzerDeserializer→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.repository.AnalyzerDeserializer→com.amazon.deequ.analyzers.AnalyzerOptionscom.amazon.deequ.repository.AnalyzerDeserializer→com.amazon.deequ.analyzers.Statecom.amazon.deequ.repository.AnalyzerOptionsDeserializer→com.amazon.deequ.analyzers.AnalyzerOptionscom.amazon.deequ.repository.AnalyzerOptionsSerializer→com.amazon.deequ.analyzers.AnalyzerOptionscom.amazon.deequ.repository.AnalyzerSerializer→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.repository.MetricsRepositoryMultipleResultsLoader→com.amazon.deequ.analyzers.Analyzer
- Direction
- com.amazon.deequ.repository uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.repository, while a change to com.amazon.deequ.repository can't break com.amazon.deequ.analyzers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→13 com.amazon.deequ.suggestions.rules.interval uses com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy✕
- Connections
- 3 pairs of types, where a type in com.amazon.deequ.suggestions.rules.interval uses a type in com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy.
- The types involved
com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy→com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy.ConfidenceIntervalcom.amazon.deequ.suggestions.rules.interval.WaldIntervalStrategy→com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy.ConfidenceIntervalcom.amazon.deequ.suggestions.rules.interval.WilsonScoreIntervalStrategy→com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy.ConfidenceInterval
- Direction
- com.amazon.deequ.suggestions.rules.interval uses com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy, so a change to com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy can break com.amazon.deequ.suggestions.rules.interval, while a change to com.amazon.deequ.suggestions.rules.interval can't break com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy.
- Position
- Below the diagonal: com.amazon.deequ.suggestions.rules.interval uses a module listed above it, which is the healthy direction.
17→12 com.amazon.deequ.analyzers.runners uses com.amazon.deequ.metrics✕
- Connections
- 4 pairs of types, where a type in com.amazon.deequ.analyzers.runners uses a type in com.amazon.deequ.metrics.
- The types involved
com.amazon.deequ.analyzers.runners.AnalysisRunBuilder→com.amazon.deequ.metrics.Metriccom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.metrics.Metriccom.amazon.deequ.analyzers.runners.AnalyzerContext→com.amazon.deequ.metrics.Metriccom.amazon.deequ.analyzers.runners.KLLRunner→com.amazon.deequ.metrics.Metric
- Direction
- com.amazon.deequ.analyzers.runners uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ.analyzers.runners, while a change to com.amazon.deequ.analyzers.runners can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ.analyzers.runners uses a module listed above it, which is the healthy direction.
17→15 com.amazon.deequ.analyzers.runners uses com.amazon.deequ.repository✕
- Connections
- 7 pairs of types, where a type in com.amazon.deequ.analyzers.runners uses a type in com.amazon.deequ.repository.
- The types involved
com.amazon.deequ.analyzers.runners.AnalysisRunBuilder→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.analyzers.runners.AnalysisRunBuilder→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.analyzers.runners.AnalysisRunBuilderWithRepository→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.analyzers.runners.AnalysisRunnerRepositoryOptions→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.analyzers.runners.AnalysisRunnerRepositoryOptions→com.amazon.deequ.repository.ResultKey
- Direction
- com.amazon.deequ.analyzers.runners uses com.amazon.deequ.repository, so a change to com.amazon.deequ.repository can break com.amazon.deequ.analyzers.runners, while a change to com.amazon.deequ.analyzers.runners can't break com.amazon.deequ.repository.
- Position
- Below the diagonal: com.amazon.deequ.analyzers.runners uses a module listed above it, which is the healthy direction.
17→18 com.amazon.deequ.analyzers.runners uses com.amazon.deequ.analyzers part of a loop✕
- Connections
- 18 pairs of types, where a type in com.amazon.deequ.analyzers.runners uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.analyzers.runners.AnalysisRunBuilder→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.Analysiscom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.FrequenciesAndNumRowscom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.GroupingAnalyzercom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.ScanShareableAnalyzercom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.ScanShareableFrequencyBasedAnalyzercom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.Statecom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.StateLoadercom.amazon.deequ.analyzers.runners.AnalysisRunner→com.amazon.deequ.analyzers.StatePersistercom.amazon.deequ.analyzers.runners.AnalyzerContext→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.analyzers.runners.KLLRunner→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.analyzers.runners.KLLRunner→com.amazon.deequ.analyzers.KLLParameterscom.amazon.deequ.analyzers.runners.KLLRunner→com.amazon.deequ.analyzers.Statecom.amazon.deequ.analyzers.runners.KLLRunner→com.amazon.deequ.analyzers.StateLoadercom.amazon.deequ.analyzers.runners.KLLRunner→com.amazon.deequ.analyzers.StatePersistercom.amazon.deequ.analyzers.runners.UntypedQuantileNonSample→com.amazon.deequ.analyzers.KLLStatecom.amazon.deequ.analyzers.runners.UntypedQuantileNonSample→com.amazon.deequ.analyzers.QuantileNonSample
- Direction
- com.amazon.deequ.analyzers.runners uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.analyzers.runners, while a change to com.amazon.deequ.analyzers.runners can't break com.amazon.deequ.analyzers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→4 com.amazon.deequ.analyzers uses com.amazon.deequ.analyzers.Histogram✕
- Connections
- 3 pairs of types, where a type in com.amazon.deequ.analyzers uses a type in com.amazon.deequ.analyzers.Histogram.
- The types involved
com.amazon.deequ.analyzers.Histogram→com.amazon.deequ.analyzers.Histogram.AggregateFunctioncom.amazon.deequ.analyzers.HistogramBase→com.amazon.deequ.analyzers.Histogram.AggregateFunctioncom.amazon.deequ.analyzers.HistogramBinned→com.amazon.deequ.analyzers.Histogram.AggregateFunction
- Direction
- com.amazon.deequ.analyzers uses com.amazon.deequ.analyzers.Histogram, so a change to com.amazon.deequ.analyzers.Histogram can break com.amazon.deequ.analyzers, while a change to com.amazon.deequ.analyzers can't break com.amazon.deequ.analyzers.Histogram.
- Position
- Below the diagonal: com.amazon.deequ.analyzers uses a module listed above it, which is the healthy direction.
18→12 com.amazon.deequ.analyzers uses com.amazon.deequ.metrics✕
- Connections
- 32 pairs of types, where a type in com.amazon.deequ.analyzers uses a type in com.amazon.deequ.metrics. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.amazon.deequ.analyzers.Analysis→com.amazon.deequ.metrics.Metriccom.amazon.deequ.analyzers.Analyzers→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.ApproxQuantile→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.ApproxQuantiles→com.amazon.deequ.metrics.KeyedDoubleMetriccom.amazon.deequ.analyzers.ColumnCount→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.ColumnExists→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.Completeness→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.Compliance→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.CountDistinct→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.CustomAggregator→com.amazon.deequ.metrics.AttributeDoubleMetriccom.amazon.deequ.analyzers.CustomSql→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.DataType→com.amazon.deequ.metrics.HistogramMetriccom.amazon.deequ.analyzers.DatasetMatchAnalyzer→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.Distance→com.amazon.deequ.metrics.BucketValuecom.amazon.deequ.analyzers.Distinctness→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.DuplicateRowCount→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.Entropy→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.ExactQuantileState→com.amazon.deequ.metrics.FullColumncom.amazon.deequ.analyzers.FrequenciesAndNumRows→com.amazon.deequ.metrics.FullColumncom.amazon.deequ.analyzers.Histogram→com.amazon.deequ.metrics.HistogramMetriccom.amazon.deequ.analyzers.HistogramBinned→com.amazon.deequ.metrics.HistogramBinnedMetriccom.amazon.deequ.analyzers.KLLSketch→com.amazon.deequ.metrics.KLLMetriccom.amazon.deequ.analyzers.MaxState→com.amazon.deequ.metrics.FullColumncom.amazon.deequ.analyzers.Maximum→com.amazon.deequ.metrics.DoubleMetriccom.amazon.deequ.analyzers.MinState→com.amazon.deequ.metrics.FullColumn
- Direction
- com.amazon.deequ.analyzers uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ.analyzers, while a change to com.amazon.deequ.analyzers can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ.analyzers uses a module listed above it, which is the healthy direction.
18→17 com.amazon.deequ.analyzers uses com.amazon.deequ.analyzers.runners✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.analyzers uses a type in com.amazon.deequ.analyzers.runners.
- The types involved
com.amazon.deequ.analyzers.Analysis→com.amazon.deequ.analyzers.runners.AnalyzerContextcom.amazon.deequ.analyzers.Analyzers→com.amazon.deequ.analyzers.runners.EmptyStateException
- Direction
- com.amazon.deequ.analyzers uses com.amazon.deequ.analyzers.runners, so a change to com.amazon.deequ.analyzers.runners can break com.amazon.deequ.analyzers, while a change to com.amazon.deequ.analyzers can't break com.amazon.deequ.analyzers.runners.
- Position
- Below the diagonal: com.amazon.deequ.analyzers uses a module listed above it, which is the healthy direction.
19→18 com.amazon.deequ.analyzers.catalyst uses com.amazon.deequ.analyzers✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.analyzers.catalyst uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.analyzers.catalyst.KLLSketchSerializer→com.amazon.deequ.analyzers.NonSampleCompactorcom.amazon.deequ.analyzers.catalyst.KLLSketchSerializer→com.amazon.deequ.analyzers.QuantileNonSample
- Direction
- com.amazon.deequ.analyzers.catalyst uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.analyzers.catalyst, while a change to com.amazon.deequ.analyzers.catalyst can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.analyzers.catalyst uses a module listed above it, which is the healthy direction.
20→12 com.amazon.deequ.constraints uses com.amazon.deequ.metrics✕
- Connections
- 5 pairs of types, where a type in com.amazon.deequ.constraints uses a type in com.amazon.deequ.metrics.
- The types involved
com.amazon.deequ.constraints.AnalysisBasedConstraint→com.amazon.deequ.metrics.Metriccom.amazon.deequ.constraints.Constraint→com.amazon.deequ.metrics.Metriccom.amazon.deequ.constraints.ConstraintDecorator→com.amazon.deequ.metrics.Metriccom.amazon.deequ.constraints.ConstraintResult→com.amazon.deequ.metrics.Metriccom.amazon.deequ.constraints.DatasetMatchConstraint→com.amazon.deequ.metrics.Metric
- Direction
- com.amazon.deequ.constraints uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ.constraints, while a change to com.amazon.deequ.constraints can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ.constraints uses a module listed above it, which is the healthy direction.
20→18 com.amazon.deequ.constraints uses com.amazon.deequ.analyzers✕
- Connections
- 5 pairs of types, where a type in com.amazon.deequ.constraints uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.constraints.AnalysisBasedConstraint→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.constraints.Constraint→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.constraints.ConstraintDecorator→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.constraints.DatasetMatchConstraint→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.constraints.DatasetMatchConstraint→com.amazon.deequ.analyzers.DatasetMatchAnalyzer
- Direction
- com.amazon.deequ.constraints uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.constraints, while a change to com.amazon.deequ.constraints can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.constraints uses a module listed above it, which is the healthy direction.
21→12 com.amazon.deequ.profiles uses com.amazon.deequ.metrics✕
- Connections
- 9 pairs of types, where a type in com.amazon.deequ.profiles uses a type in com.amazon.deequ.metrics.
- The types involved
com.amazon.deequ.profiles.CategoricalColumnStatistics→com.amazon.deequ.metrics.Distributioncom.amazon.deequ.profiles.ColumnProfile→com.amazon.deequ.metrics.Distributioncom.amazon.deequ.profiles.ColumnProfiler→com.amazon.deequ.metrics.Distributioncom.amazon.deequ.profiles.ColumnProfiler→com.amazon.deequ.metrics.Metriccom.amazon.deequ.profiles.NumericColumnProfile→com.amazon.deequ.metrics.BucketDistributioncom.amazon.deequ.profiles.NumericColumnProfile→com.amazon.deequ.metrics.Distributioncom.amazon.deequ.profiles.NumericColumnStatistics→com.amazon.deequ.metrics.BucketDistributioncom.amazon.deequ.profiles.StandardColumnProfile→com.amazon.deequ.metrics.Distributioncom.amazon.deequ.profiles.StringColumnProfile→com.amazon.deequ.metrics.Distribution
- Direction
- com.amazon.deequ.profiles uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ.profiles, while a change to com.amazon.deequ.profiles can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ.profiles uses a module listed above it, which is the healthy direction.
21→15 com.amazon.deequ.profiles uses com.amazon.deequ.repository✕
- Connections
- 7 pairs of types, where a type in com.amazon.deequ.profiles uses a type in com.amazon.deequ.repository.
- The types involved
com.amazon.deequ.profiles.ColumnProfiler→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.profiles.ColumnProfiler→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.profiles.ColumnProfilerRunBuilder→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.profiles.ColumnProfilerRunBuilder→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.profiles.ColumnProfilerRunBuilderMetricsRepositoryOptions→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.profiles.ColumnProfilerRunBuilderMetricsRepositoryOptions→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.profiles.ColumnProfilerRunBuilderWithRepository→com.amazon.deequ.repository.ResultKey
- Direction
- com.amazon.deequ.profiles uses com.amazon.deequ.repository, so a change to com.amazon.deequ.repository can break com.amazon.deequ.profiles, while a change to com.amazon.deequ.profiles can't break com.amazon.deequ.repository.
- Position
- Below the diagonal: com.amazon.deequ.profiles uses a module listed above it, which is the healthy direction.
21→17 com.amazon.deequ.profiles uses com.amazon.deequ.analyzers.runners✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.profiles uses a type in com.amazon.deequ.analyzers.runners.
- The types involved
com.amazon.deequ.profiles.ColumnProfiler→com.amazon.deequ.analyzers.runners.AnalysisRunBuildercom.amazon.deequ.profiles.ColumnProfiler→com.amazon.deequ.analyzers.runners.AnalyzerContext
- Direction
- com.amazon.deequ.profiles uses com.amazon.deequ.analyzers.runners, so a change to com.amazon.deequ.analyzers.runners can break com.amazon.deequ.profiles, while a change to com.amazon.deequ.profiles can't break com.amazon.deequ.analyzers.runners.
- Position
- Below the diagonal: com.amazon.deequ.profiles uses a module listed above it, which is the healthy direction.
21→18 com.amazon.deequ.profiles uses com.amazon.deequ.analyzers✕
- Connections
- 4 pairs of types, where a type in com.amazon.deequ.profiles uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.profiles.ColumnProfiler→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.profiles.ColumnProfiler→com.amazon.deequ.analyzers.KLLParameterscom.amazon.deequ.profiles.ColumnProfilerRunBuilder→com.amazon.deequ.analyzers.KLLParameterscom.amazon.deequ.profiles.ColumnProfilerRunner→com.amazon.deequ.analyzers.KLLParameters
- Direction
- com.amazon.deequ.profiles uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.profiles, while a change to com.amazon.deequ.profiles can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.profiles uses a module listed above it, which is the healthy direction.
22→15 com.amazon.deequ.repository.fs uses com.amazon.deequ.repository✕
- Connections
- 6 pairs of types, where a type in com.amazon.deequ.repository.fs uses a type in com.amazon.deequ.repository.
- The types involved
com.amazon.deequ.repository.fs.FileSystemMetricsRepository→com.amazon.deequ.repository.AnalysisResultcom.amazon.deequ.repository.fs.FileSystemMetricsRepository→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.repository.fs.FileSystemMetricsRepository→com.amazon.deequ.repository.MetricsRepositoryMultipleResultsLoadercom.amazon.deequ.repository.fs.FileSystemMetricsRepository→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.repository.fs.FileSystemMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.repository.AnalysisResultcom.amazon.deequ.repository.fs.FileSystemMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.repository.MetricsRepositoryMultipleResultsLoader
- Direction
- com.amazon.deequ.repository.fs uses com.amazon.deequ.repository, so a change to com.amazon.deequ.repository can break com.amazon.deequ.repository.fs, while a change to com.amazon.deequ.repository.fs can't break com.amazon.deequ.repository.
- Position
- Below the diagonal: com.amazon.deequ.repository.fs uses a module listed above it, which is the healthy direction.
22→17 com.amazon.deequ.repository.fs uses com.amazon.deequ.analyzers.runners✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.repository.fs uses a type in com.amazon.deequ.analyzers.runners.
- The types involved
com.amazon.deequ.repository.fs.FileSystemMetricsRepository→com.amazon.deequ.analyzers.runners.AnalyzerContext
- Direction
- com.amazon.deequ.repository.fs uses com.amazon.deequ.analyzers.runners, so a change to com.amazon.deequ.analyzers.runners can break com.amazon.deequ.repository.fs, while a change to com.amazon.deequ.repository.fs can't break com.amazon.deequ.analyzers.runners.
- Position
- Below the diagonal: com.amazon.deequ.repository.fs uses a module listed above it, which is the healthy direction.
22→18 com.amazon.deequ.repository.fs uses com.amazon.deequ.analyzers✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.repository.fs uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.repository.fs.FileSystemMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.analyzers.Analyzer
- Direction
- com.amazon.deequ.repository.fs uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.repository.fs, while a change to com.amazon.deequ.repository.fs can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.repository.fs uses a module listed above it, which is the healthy direction.
23→15 com.amazon.deequ.repository.memory uses com.amazon.deequ.repository✕
- Connections
- 5 pairs of types, where a type in com.amazon.deequ.repository.memory uses a type in com.amazon.deequ.repository.
- The types involved
com.amazon.deequ.repository.memory.InMemoryMetricsRepository→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.repository.memory.InMemoryMetricsRepository→com.amazon.deequ.repository.MetricsRepositoryMultipleResultsLoadercom.amazon.deequ.repository.memory.InMemoryMetricsRepository→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.repository.memory.LimitedInMemoryMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.repository.AnalysisResultcom.amazon.deequ.repository.memory.LimitedInMemoryMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.repository.MetricsRepositoryMultipleResultsLoader
- Direction
- com.amazon.deequ.repository.memory uses com.amazon.deequ.repository, so a change to com.amazon.deequ.repository can break com.amazon.deequ.repository.memory, while a change to com.amazon.deequ.repository.memory can't break com.amazon.deequ.repository.
- Position
- Below the diagonal: com.amazon.deequ.repository.memory uses a module listed above it, which is the healthy direction.
23→17 com.amazon.deequ.repository.memory uses com.amazon.deequ.analyzers.runners✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.repository.memory uses a type in com.amazon.deequ.analyzers.runners.
- The types involved
com.amazon.deequ.repository.memory.InMemoryMetricsRepository→com.amazon.deequ.analyzers.runners.AnalyzerContext
- Direction
- com.amazon.deequ.repository.memory uses com.amazon.deequ.analyzers.runners, so a change to com.amazon.deequ.analyzers.runners can break com.amazon.deequ.repository.memory, while a change to com.amazon.deequ.repository.memory can't break com.amazon.deequ.analyzers.runners.
- Position
- Below the diagonal: com.amazon.deequ.repository.memory uses a module listed above it, which is the healthy direction.
23→18 com.amazon.deequ.repository.memory uses com.amazon.deequ.analyzers✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.repository.memory uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.repository.memory.LimitedInMemoryMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.analyzers.Analyzer
- Direction
- com.amazon.deequ.repository.memory uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.repository.memory, while a change to com.amazon.deequ.repository.memory can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.repository.memory uses a module listed above it, which is the healthy direction.
24→15 com.amazon.deequ.repository.sparktable uses com.amazon.deequ.repository✕
- Connections
- 5 pairs of types, where a type in com.amazon.deequ.repository.sparktable uses a type in com.amazon.deequ.repository.
- The types involved
com.amazon.deequ.repository.sparktable.SparkTableMetricsRepository→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.repository.sparktable.SparkTableMetricsRepository→com.amazon.deequ.repository.MetricsRepositoryMultipleResultsLoadercom.amazon.deequ.repository.sparktable.SparkTableMetricsRepository→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.repository.sparktable.SparkTableMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.repository.AnalysisResultcom.amazon.deequ.repository.sparktable.SparkTableMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.repository.MetricsRepositoryMultipleResultsLoader
- Direction
- com.amazon.deequ.repository.sparktable uses com.amazon.deequ.repository, so a change to com.amazon.deequ.repository can break com.amazon.deequ.repository.sparktable, while a change to com.amazon.deequ.repository.sparktable can't break com.amazon.deequ.repository.
- Position
- Below the diagonal: com.amazon.deequ.repository.sparktable uses a module listed above it, which is the healthy direction.
24→17 com.amazon.deequ.repository.sparktable uses com.amazon.deequ.analyzers.runners✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.repository.sparktable uses a type in com.amazon.deequ.analyzers.runners.
- The types involved
com.amazon.deequ.repository.sparktable.SparkTableMetricsRepository→com.amazon.deequ.analyzers.runners.AnalyzerContext
- Direction
- com.amazon.deequ.repository.sparktable uses com.amazon.deequ.analyzers.runners, so a change to com.amazon.deequ.analyzers.runners can break com.amazon.deequ.repository.sparktable, while a change to com.amazon.deequ.repository.sparktable can't break com.amazon.deequ.analyzers.runners.
- Position
- Below the diagonal: com.amazon.deequ.repository.sparktable uses a module listed above it, which is the healthy direction.
24→18 com.amazon.deequ.repository.sparktable uses com.amazon.deequ.analyzers✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.repository.sparktable uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.repository.sparktable.SparkTableMetricsRepositoryMultipleResultsLoader→com.amazon.deequ.analyzers.Analyzer
- Direction
- com.amazon.deequ.repository.sparktable uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.repository.sparktable, while a change to com.amazon.deequ.repository.sparktable can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.repository.sparktable uses a module listed above it, which is the healthy direction.
25→18 org.apache.spark.sql uses com.amazon.deequ.analyzers✕
- Connections
- 2 pairs of types, where a type in org.apache.spark.sql uses a type in com.amazon.deequ.analyzers.
- The types involved
org.apache.spark.sql.KLLAggregationBuffer→com.amazon.deequ.analyzers.QuantileNonSampleorg.apache.spark.sql.StatefulKLLSketch→com.amazon.deequ.analyzers.QuantileNonSample
- Direction
- org.apache.spark.sql uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break org.apache.spark.sql, while a change to org.apache.spark.sql can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: org.apache.spark.sql uses a module listed above it, which is the healthy direction.
26→18 org.apache.spark.sql.catalyst.expressions.aggregate uses com.amazon.deequ.analyzers✕
- Connections
- 1 pair of types, where a type in org.apache.spark.sql.catalyst.expressions.aggregate uses a type in com.amazon.deequ.analyzers.
- The types involved
org.apache.spark.sql.catalyst.expressions.aggregate.DeequHyperLogLogPlusPlusUtils→com.amazon.deequ.analyzers.ApproxCountDistinctState
- Direction
- org.apache.spark.sql.catalyst.expressions.aggregate uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break org.apache.spark.sql.catalyst.expressions.aggregate, while a change to org.apache.spark.sql.catalyst.expressions.aggregate can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: org.apache.spark.sql.catalyst.expressions.aggregate uses a module listed above it, which is the healthy direction.
27→20 com.amazon.deequ.analyzers.applicability uses com.amazon.deequ.constraints✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.analyzers.applicability uses a type in com.amazon.deequ.constraints.
- The types involved
com.amazon.deequ.analyzers.applicability.CheckApplicability→com.amazon.deequ.constraints.Constraint
- Direction
- com.amazon.deequ.analyzers.applicability uses com.amazon.deequ.constraints, so a change to com.amazon.deequ.constraints can break com.amazon.deequ.analyzers.applicability, while a change to com.amazon.deequ.analyzers.applicability can't break com.amazon.deequ.constraints.
- Position
- Below the diagonal: com.amazon.deequ.analyzers.applicability uses a module listed above it, which is the healthy direction.
28→12 com.amazon.deequ.checks uses com.amazon.deequ.metrics✕
- Connections
- 4 pairs of types, where a type in com.amazon.deequ.checks uses a type in com.amazon.deequ.metrics.
- The types involved
com.amazon.deequ.checks.Check→com.amazon.deequ.metrics.BucketDistributioncom.amazon.deequ.checks.Check→com.amazon.deequ.metrics.Distributioncom.amazon.deequ.checks.Check→com.amazon.deequ.metrics.DistributionBinnedcom.amazon.deequ.checks.Check→com.amazon.deequ.metrics.Metric
- Direction
- com.amazon.deequ.checks uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ.checks, while a change to com.amazon.deequ.checks can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ.checks uses a module listed above it, which is the healthy direction.
28→14 com.amazon.deequ.checks uses com.amazon.deequ.anomalydetection✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.checks uses a type in com.amazon.deequ.anomalydetection.
- The types involved
com.amazon.deequ.checks.Check→com.amazon.deequ.anomalydetection.AnomalyDetectionStrategy
- Direction
- com.amazon.deequ.checks uses com.amazon.deequ.anomalydetection, so a change to com.amazon.deequ.anomalydetection can break com.amazon.deequ.checks, while a change to com.amazon.deequ.checks can't break com.amazon.deequ.anomalydetection.
- Position
- Below the diagonal: com.amazon.deequ.checks uses a module listed above it, which is the healthy direction.
28→15 com.amazon.deequ.checks uses com.amazon.deequ.repository✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.checks uses a type in com.amazon.deequ.repository.
- The types involved
com.amazon.deequ.checks.Check→com.amazon.deequ.repository.MetricsRepository
- Direction
- com.amazon.deequ.checks uses com.amazon.deequ.repository, so a change to com.amazon.deequ.repository can break com.amazon.deequ.checks, while a change to com.amazon.deequ.checks can't break com.amazon.deequ.repository.
- Position
- Below the diagonal: com.amazon.deequ.checks uses a module listed above it, which is the healthy direction.
28→17 com.amazon.deequ.checks uses com.amazon.deequ.analyzers.runners✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.checks uses a type in com.amazon.deequ.analyzers.runners.
- The types involved
com.amazon.deequ.checks.Check→com.amazon.deequ.analyzers.runners.AnalyzerContext
- Direction
- com.amazon.deequ.checks uses com.amazon.deequ.analyzers.runners, so a change to com.amazon.deequ.analyzers.runners can break com.amazon.deequ.checks, while a change to com.amazon.deequ.checks can't break com.amazon.deequ.analyzers.runners.
- Position
- Below the diagonal: com.amazon.deequ.checks uses a module listed above it, which is the healthy direction.
28→18 com.amazon.deequ.checks uses com.amazon.deequ.analyzers✕
- Connections
- 3 pairs of types, where a type in com.amazon.deequ.checks uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.checks.Check→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.checks.Check→com.amazon.deequ.analyzers.AnalyzerOptionscom.amazon.deequ.checks.Check→com.amazon.deequ.analyzers.KLLParameters
- Direction
- com.amazon.deequ.checks uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.checks, while a change to com.amazon.deequ.checks can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.checks uses a module listed above it, which is the healthy direction.
28→20 com.amazon.deequ.checks uses com.amazon.deequ.constraints✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.checks uses a type in com.amazon.deequ.constraints.
- The types involved
com.amazon.deequ.checks.Check→com.amazon.deequ.constraints.Constraintcom.amazon.deequ.checks.CheckResult→com.amazon.deequ.constraints.ConstraintResult
- Direction
- com.amazon.deequ.checks uses com.amazon.deequ.constraints, so a change to com.amazon.deequ.constraints can break com.amazon.deequ.checks, while a change to com.amazon.deequ.checks can't break com.amazon.deequ.constraints.
- Position
- Below the diagonal: com.amazon.deequ.checks uses a module listed above it, which is the healthy direction.
29→12 com.amazon.deequ.suggestions.rules uses com.amazon.deequ.metrics✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.suggestions.rules uses a type in com.amazon.deequ.metrics.
- The types involved
com.amazon.deequ.suggestions.rules.FractionalCategoricalRangeRule→com.amazon.deequ.metrics.DistributionValue
- Direction
- com.amazon.deequ.suggestions.rules uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ.suggestions.rules, while a change to com.amazon.deequ.suggestions.rules can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ.suggestions.rules uses a module listed above it, which is the healthy direction.
29→16 com.amazon.deequ.suggestions.rules uses com.amazon.deequ.suggestions.rules.interval✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.suggestions.rules uses a type in com.amazon.deequ.suggestions.rules.interval.
- The types involved
com.amazon.deequ.suggestions.rules.FractionalCategoricalRangeRule→com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategycom.amazon.deequ.suggestions.rules.RetainCompletenessRule→com.amazon.deequ.suggestions.rules.interval.ConfidenceIntervalStrategy
- Direction
- com.amazon.deequ.suggestions.rules uses com.amazon.deequ.suggestions.rules.interval, so a change to com.amazon.deequ.suggestions.rules.interval can break com.amazon.deequ.suggestions.rules, while a change to com.amazon.deequ.suggestions.rules can't break com.amazon.deequ.suggestions.rules.interval.
- Position
- Below the diagonal: com.amazon.deequ.suggestions.rules uses a module listed above it, which is the healthy direction.
29→21 com.amazon.deequ.suggestions.rules uses com.amazon.deequ.profiles✕
- Connections
- 13 pairs of types, where a type in com.amazon.deequ.suggestions.rules uses a type in com.amazon.deequ.profiles.
- The types involved
com.amazon.deequ.suggestions.rules.CategoricalRangeRule→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.CompleteIfCompleteRule→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.FractionalCategoricalRangeRule→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.HasMax→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.HasMaxLength→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.HasMean→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.HasMin→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.HasMinLength→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.HasStandardDeviation→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.NonNegativeNumbersRule→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.RetainCompletenessRule→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.RetainTypeRule→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.rules.UniqueIfApproximatelyUniqueRule→com.amazon.deequ.profiles.ColumnProfile
- Direction
- com.amazon.deequ.suggestions.rules uses com.amazon.deequ.profiles, so a change to com.amazon.deequ.profiles can break com.amazon.deequ.suggestions.rules, while a change to com.amazon.deequ.suggestions.rules can't break com.amazon.deequ.profiles.
- Position
- Below the diagonal: com.amazon.deequ.suggestions.rules uses a module listed above it, which is the healthy direction.
29→39 com.amazon.deequ.suggestions.rules uses com.amazon.deequ.suggestions part of a loop✕
- Connections
- 14 pairs of types, where a type in com.amazon.deequ.suggestions.rules uses a type in com.amazon.deequ.suggestions.
- The types involved
com.amazon.deequ.suggestions.rules.CategoricalRangeRule→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.CompleteIfCompleteRule→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.ConstraintRule→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.FractionalCategoricalRangeRule→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.HasMax→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.HasMaxLength→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.HasMean→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.HasMin→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.HasMinLength→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.HasStandardDeviation→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.NonNegativeNumbersRule→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.RetainCompletenessRule→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.RetainTypeRule→com.amazon.deequ.suggestions.ConstraintSuggestioncom.amazon.deequ.suggestions.rules.UniqueIfApproximatelyUniqueRule→com.amazon.deequ.suggestions.ConstraintSuggestion
- Direction
- com.amazon.deequ.suggestions.rules uses com.amazon.deequ.suggestions, so a change to com.amazon.deequ.suggestions can break com.amazon.deequ.suggestions.rules, while a change to com.amazon.deequ.suggestions.rules can't break com.amazon.deequ.suggestions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→12 com.amazon.deequ uses com.amazon.deequ.metrics✕
- Connections
- 5 pairs of types, where a type in com.amazon.deequ uses a type in com.amazon.deequ.metrics.
- The types involved
com.amazon.deequ.VerificationResult→com.amazon.deequ.metrics.Metriccom.amazon.deequ.VerificationRunBuilder→com.amazon.deequ.metrics.Metriccom.amazon.deequ.VerificationRunBuilderHelper→com.amazon.deequ.metrics.Metriccom.amazon.deequ.VerificationRunBuilderWithRepository→com.amazon.deequ.metrics.Metriccom.amazon.deequ.VerificationSuite→com.amazon.deequ.metrics.Metric
- Direction
- com.amazon.deequ uses com.amazon.deequ.metrics, so a change to com.amazon.deequ.metrics can break com.amazon.deequ, while a change to com.amazon.deequ can't break com.amazon.deequ.metrics.
- Position
- Below the diagonal: com.amazon.deequ uses a module listed above it, which is the healthy direction.
30→14 com.amazon.deequ uses com.amazon.deequ.anomalydetection✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ uses a type in com.amazon.deequ.anomalydetection.
- The types involved
com.amazon.deequ.VerificationRunBuilderHelper→com.amazon.deequ.anomalydetection.AnomalyDetectionStrategycom.amazon.deequ.VerificationRunBuilderWithRepository→com.amazon.deequ.anomalydetection.AnomalyDetectionStrategy
- Direction
- com.amazon.deequ uses com.amazon.deequ.anomalydetection, so a change to com.amazon.deequ.anomalydetection can break com.amazon.deequ, while a change to com.amazon.deequ can't break com.amazon.deequ.anomalydetection.
- Position
- Below the diagonal: com.amazon.deequ uses a module listed above it, which is the healthy direction.
30→15 com.amazon.deequ uses com.amazon.deequ.repository✕
- Connections
- 8 pairs of types, where a type in com.amazon.deequ uses a type in com.amazon.deequ.repository.
- The types involved
com.amazon.deequ.VerificationMetricsRepositoryOptions→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.VerificationMetricsRepositoryOptions→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.VerificationRunBuilder→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.VerificationRunBuilder→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.VerificationRunBuilderHelper→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.VerificationRunBuilderWithRepository→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.VerificationSuite→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.VerificationSuite→com.amazon.deequ.repository.ResultKey
- Direction
- com.amazon.deequ uses com.amazon.deequ.repository, so a change to com.amazon.deequ.repository can break com.amazon.deequ, while a change to com.amazon.deequ can't break com.amazon.deequ.repository.
- Position
- Below the diagonal: com.amazon.deequ uses a module listed above it, which is the healthy direction.
30→17 com.amazon.deequ uses com.amazon.deequ.analyzers.runners✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ uses a type in com.amazon.deequ.analyzers.runners.
- The types involved
com.amazon.deequ.VerificationSuite→com.amazon.deequ.analyzers.runners.AnalyzerContext
- Direction
- com.amazon.deequ uses com.amazon.deequ.analyzers.runners, so a change to com.amazon.deequ.analyzers.runners can break com.amazon.deequ, while a change to com.amazon.deequ can't break com.amazon.deequ.analyzers.runners.
- Position
- Below the diagonal: com.amazon.deequ uses a module listed above it, which is the healthy direction.
30→18 com.amazon.deequ uses com.amazon.deequ.analyzers✕
- Connections
- 10 pairs of types, where a type in com.amazon.deequ uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.VerificationResult→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.VerificationRunBuilder→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.VerificationRunBuilder→com.amazon.deequ.analyzers.StateLoadercom.amazon.deequ.VerificationRunBuilder→com.amazon.deequ.analyzers.StatePersistercom.amazon.deequ.VerificationRunBuilderHelper→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.VerificationRunBuilderWithRepository→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.VerificationSuite→com.amazon.deequ.analyzers.Analysiscom.amazon.deequ.VerificationSuite→com.amazon.deequ.analyzers.Analyzercom.amazon.deequ.VerificationSuite→com.amazon.deequ.analyzers.StateLoadercom.amazon.deequ.VerificationSuite→com.amazon.deequ.analyzers.StatePersister
- Direction
- com.amazon.deequ uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ, while a change to com.amazon.deequ can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ uses a module listed above it, which is the healthy direction.
30→27 com.amazon.deequ uses com.amazon.deequ.analyzers.applicability✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ uses a type in com.amazon.deequ.analyzers.applicability.
- The types involved
com.amazon.deequ.VerificationSuite→com.amazon.deequ.analyzers.applicability.AnalyzersApplicabilitycom.amazon.deequ.VerificationSuite→com.amazon.deequ.analyzers.applicability.CheckApplicability
- Direction
- com.amazon.deequ uses com.amazon.deequ.analyzers.applicability, so a change to com.amazon.deequ.analyzers.applicability can break com.amazon.deequ, while a change to com.amazon.deequ can't break com.amazon.deequ.analyzers.applicability.
- Position
- Below the diagonal: com.amazon.deequ uses a module listed above it, which is the healthy direction.
30→28 com.amazon.deequ uses com.amazon.deequ.checks✕
- Connections
- 5 pairs of types, where a type in com.amazon.deequ uses a type in com.amazon.deequ.checks.
- The types involved
com.amazon.deequ.VerificationResult→com.amazon.deequ.checks.Checkcom.amazon.deequ.VerificationResult→com.amazon.deequ.checks.CheckResultcom.amazon.deequ.VerificationRunBuilder→com.amazon.deequ.checks.Checkcom.amazon.deequ.VerificationRunBuilderHelper→com.amazon.deequ.checks.Checkcom.amazon.deequ.VerificationSuite→com.amazon.deequ.checks.Check
- Direction
- com.amazon.deequ uses com.amazon.deequ.checks, so a change to com.amazon.deequ.checks can break com.amazon.deequ, while a change to com.amazon.deequ can't break com.amazon.deequ.checks.
- Position
- Below the diagonal: com.amazon.deequ uses a module listed above it, which is the healthy direction.
31→28 com.amazon.deequ.dqdl.model uses com.amazon.deequ.checks✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.dqdl.model uses a type in com.amazon.deequ.checks.
- The types involved
com.amazon.deequ.dqdl.model.DeequExecutableRule→com.amazon.deequ.checks.Check
- Direction
- com.amazon.deequ.dqdl.model uses com.amazon.deequ.checks, so a change to com.amazon.deequ.checks can break com.amazon.deequ.dqdl.model, while a change to com.amazon.deequ.dqdl.model can't break com.amazon.deequ.checks.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.model uses a module listed above it, which is the healthy direction.
32→31 com.amazon.deequ.dqdl uses com.amazon.deequ.dqdl.model✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.dqdl uses a type in com.amazon.deequ.dqdl.model.
- The types involved
com.amazon.deequ.dqdl.EvaluateDataQuality→com.amazon.deequ.dqdl.model.DeequExecutableRulecom.amazon.deequ.dqdl.EvaluateDataQuality→com.amazon.deequ.dqdl.model.ExecutableRule
- Direction
- com.amazon.deequ.dqdl uses com.amazon.deequ.dqdl.model, so a change to com.amazon.deequ.dqdl.model can break com.amazon.deequ.dqdl, while a change to com.amazon.deequ.dqdl can't break com.amazon.deequ.dqdl.model.
- Position
- Below the diagonal: com.amazon.deequ.dqdl uses a module listed above it, which is the healthy direction.
33→31 com.amazon.deequ.dqdl.execution uses com.amazon.deequ.dqdl.model✕
- Connections
- 4 pairs of types, where a type in com.amazon.deequ.dqdl.execution uses a type in com.amazon.deequ.dqdl.model.
- The types involved
com.amazon.deequ.dqdl.execution.DQDLExecutor→com.amazon.deequ.dqdl.model.ExecutableRulecom.amazon.deequ.dqdl.execution.DQDLExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.RowLevelResultHelper→com.amazon.deequ.dqdl.model.RowLevelOutcomecom.amazon.deequ.dqdl.execution.RowLevelResultHelper→com.amazon.deequ.dqdl.model.RuleOutcome
- Direction
- com.amazon.deequ.dqdl.execution uses com.amazon.deequ.dqdl.model, so a change to com.amazon.deequ.dqdl.model can break com.amazon.deequ.dqdl.execution, while a change to com.amazon.deequ.dqdl.execution can't break com.amazon.deequ.dqdl.model.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.execution uses a module listed above it, which is the healthy direction.
34→31 com.amazon.deequ.dqdl.execution.DQDLExecutor uses com.amazon.deequ.dqdl.model✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.dqdl.execution.DQDLExecutor uses a type in com.amazon.deequ.dqdl.model.
- The types involved
com.amazon.deequ.dqdl.execution.DQDLExecutor.RuleExecutor→com.amazon.deequ.dqdl.model.RuleOutcome
- Direction
- com.amazon.deequ.dqdl.execution.DQDLExecutor uses com.amazon.deequ.dqdl.model, so a change to com.amazon.deequ.dqdl.model can break com.amazon.deequ.dqdl.execution.DQDLExecutor, while a change to com.amazon.deequ.dqdl.execution.DQDLExecutor can't break com.amazon.deequ.dqdl.model.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.execution.DQDLExecutor uses a module listed above it, which is the healthy direction.
35→31 com.amazon.deequ.dqdl.execution.executors uses com.amazon.deequ.dqdl.model✕
- Connections
- 29 pairs of types, where a type in com.amazon.deequ.dqdl.execution.executors uses a type in com.amazon.deequ.dqdl.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.amazon.deequ.dqdl.execution.executors.AggregateMatchExecutor→com.amazon.deequ.dqdl.model.AggregateMatchExecutableRulecom.amazon.deequ.dqdl.execution.executors.AggregateMatchExecutor→com.amazon.deequ.dqdl.model.AggregateOperationcom.amazon.deequ.dqdl.execution.executors.AggregateMatchExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.ColumnDataTypeExecutor→com.amazon.deequ.dqdl.model.ColumnDataTypeExecutableRulecom.amazon.deequ.dqdl.execution.executors.ColumnDataTypeExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.ColumnNamesMatchPatternExecutor→com.amazon.deequ.dqdl.model.ColumnNamesMatchPatternExecutableRulecom.amazon.deequ.dqdl.execution.executors.ColumnNamesMatchPatternExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.CompositeRulesExecutor→com.amazon.deequ.dqdl.model.CompositeExecutableRulecom.amazon.deequ.dqdl.execution.executors.CompositeRulesExecutor→com.amazon.deequ.dqdl.model.ExecutableRulecom.amazon.deequ.dqdl.execution.executors.CompositeRulesExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.CustomSqlExecutionResult→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor→com.amazon.deequ.dqdl.model.CustomSqlRowLevelExecutableRulecom.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.DataFreshnessExecutor→com.amazon.deequ.dqdl.model.DataFreshnessExecutableRulecom.amazon.deequ.dqdl.execution.executors.DataFreshnessExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.DatasetMatchExecutor→com.amazon.deequ.dqdl.model.DatasetMatchExecutableRulecom.amazon.deequ.dqdl.execution.executors.DatasetMatchExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.DeequExecutionResult→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.DeequRulesExecutor→com.amazon.deequ.dqdl.model.DeequExecutableRulecom.amazon.deequ.dqdl.execution.executors.DeequRulesExecutor→com.amazon.deequ.dqdl.model.DeequMetricMappingcom.amazon.deequ.dqdl.execution.executors.DeequRulesExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.ReferentialIntegrityExecutor→com.amazon.deequ.dqdl.model.ReferentialIntegrityExecutableRulecom.amazon.deequ.dqdl.execution.executors.ReferentialIntegrityExecutor→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.execution.executors.RowCountMatchExecutor→com.amazon.deequ.dqdl.model.RowCountMatchExecutableRulecom.amazon.deequ.dqdl.execution.executors.RowCountMatchExecutor→com.amazon.deequ.dqdl.model.RuleOutcome
- Direction
- com.amazon.deequ.dqdl.execution.executors uses com.amazon.deequ.dqdl.model, so a change to com.amazon.deequ.dqdl.model can break com.amazon.deequ.dqdl.execution.executors, while a change to com.amazon.deequ.dqdl.execution.executors can't break com.amazon.deequ.dqdl.model.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.execution.executors uses a module listed above it, which is the healthy direction.
36→31 com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor uses com.amazon.deequ.dqdl.model✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor uses a type in com.amazon.deequ.dqdl.model.
- The types involved
com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor.SingleRuleResult→com.amazon.deequ.dqdl.model.RuleOutcome
- Direction
- com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor uses com.amazon.deequ.dqdl.model, so a change to com.amazon.deequ.dqdl.model can break com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor, while a change to com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor can't break com.amazon.deequ.dqdl.model.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.execution.executors.CustomSqlRowLevelExecutor uses a module listed above it, which is the healthy direction.
37→31 com.amazon.deequ.dqdl.translation uses com.amazon.deequ.dqdl.model✕
- Connections
- 4 pairs of types, where a type in com.amazon.deequ.dqdl.translation uses a type in com.amazon.deequ.dqdl.model.
- The types involved
com.amazon.deequ.dqdl.translation.DQDLRuleTranslator→com.amazon.deequ.dqdl.model.DeequExecutableRulecom.amazon.deequ.dqdl.translation.DQDLRuleTranslator→com.amazon.deequ.dqdl.model.ExecutableRulecom.amazon.deequ.dqdl.translation.DeequOutcomeTranslator→com.amazon.deequ.dqdl.model.RuleOutcomecom.amazon.deequ.dqdl.translation.RuleOutcomeTranslator→com.amazon.deequ.dqdl.model.RuleOutcome
- Direction
- com.amazon.deequ.dqdl.translation uses com.amazon.deequ.dqdl.model, so a change to com.amazon.deequ.dqdl.model can break com.amazon.deequ.dqdl.translation, while a change to com.amazon.deequ.dqdl.translation can't break com.amazon.deequ.dqdl.model.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.translation uses a module listed above it, which is the healthy direction.
38→18 com.amazon.deequ.dqdl.util uses com.amazon.deequ.analyzers✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.dqdl.util uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.dqdl.util.RuleEvaluationHelper→com.amazon.deequ.analyzers.FilteredRowOutcome
- Direction
- com.amazon.deequ.dqdl.util uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.dqdl.util, while a change to com.amazon.deequ.dqdl.util can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.util uses a module listed above it, which is the healthy direction.
38→28 com.amazon.deequ.dqdl.util uses com.amazon.deequ.checks✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.dqdl.util uses a type in com.amazon.deequ.checks.
- The types involved
com.amazon.deequ.dqdl.util.DQDLUtility→com.amazon.deequ.checks.Checkcom.amazon.deequ.dqdl.util.DQDLUtility→com.amazon.deequ.checks.CheckWithLastConstraintFilterable
- Direction
- com.amazon.deequ.dqdl.util uses com.amazon.deequ.checks, so a change to com.amazon.deequ.checks can break com.amazon.deequ.dqdl.util, while a change to com.amazon.deequ.dqdl.util can't break com.amazon.deequ.checks.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.util uses a module listed above it, which is the healthy direction.
38→31 com.amazon.deequ.dqdl.util uses com.amazon.deequ.dqdl.model✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.dqdl.util uses a type in com.amazon.deequ.dqdl.model.
- The types involved
com.amazon.deequ.dqdl.util.RuleEvaluationHelper→com.amazon.deequ.dqdl.model.RuleOutcome
- Direction
- com.amazon.deequ.dqdl.util uses com.amazon.deequ.dqdl.model, so a change to com.amazon.deequ.dqdl.model can break com.amazon.deequ.dqdl.util, while a change to com.amazon.deequ.dqdl.util can't break com.amazon.deequ.dqdl.model.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.util uses a module listed above it, which is the healthy direction.
39→15 com.amazon.deequ.suggestions uses com.amazon.deequ.repository✕
- Connections
- 5 pairs of types, where a type in com.amazon.deequ.suggestions uses a type in com.amazon.deequ.repository.
- The types involved
com.amazon.deequ.suggestions.ConstraintSuggestionMetricsRepositoryOptions→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.suggestions.ConstraintSuggestionMetricsRepositoryOptions→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.suggestions.ConstraintSuggestionRunBuilder→com.amazon.deequ.repository.MetricsRepositorycom.amazon.deequ.suggestions.ConstraintSuggestionRunBuilder→com.amazon.deequ.repository.ResultKeycom.amazon.deequ.suggestions.ConstraintSuggestionRunBuilderWithRepository→com.amazon.deequ.repository.ResultKey
- Direction
- com.amazon.deequ.suggestions uses com.amazon.deequ.repository, so a change to com.amazon.deequ.repository can break com.amazon.deequ.suggestions, while a change to com.amazon.deequ.suggestions can't break com.amazon.deequ.repository.
- Position
- Below the diagonal: com.amazon.deequ.suggestions uses a module listed above it, which is the healthy direction.
39→18 com.amazon.deequ.suggestions uses com.amazon.deequ.analyzers✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.suggestions uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.suggestions.ConstraintSuggestionRunBuilder→com.amazon.deequ.analyzers.KLLParameterscom.amazon.deequ.suggestions.ConstraintSuggestionRunner→com.amazon.deequ.analyzers.KLLParameters
- Direction
- com.amazon.deequ.suggestions uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.suggestions, while a change to com.amazon.deequ.suggestions can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.suggestions uses a module listed above it, which is the healthy direction.
39→20 com.amazon.deequ.suggestions uses com.amazon.deequ.constraints✕
- Connections
- 3 pairs of types, where a type in com.amazon.deequ.suggestions uses a type in com.amazon.deequ.constraints.
- The types involved
com.amazon.deequ.suggestions.CommonConstraintSuggestion→com.amazon.deequ.constraints.Constraintcom.amazon.deequ.suggestions.ConstraintSuggestion→com.amazon.deequ.constraints.Constraintcom.amazon.deequ.suggestions.ConstraintSuggestionWithValue→com.amazon.deequ.constraints.Constraint
- Direction
- com.amazon.deequ.suggestions uses com.amazon.deequ.constraints, so a change to com.amazon.deequ.constraints can break com.amazon.deequ.suggestions, while a change to com.amazon.deequ.suggestions can't break com.amazon.deequ.constraints.
- Position
- Below the diagonal: com.amazon.deequ.suggestions uses a module listed above it, which is the healthy direction.
39→21 com.amazon.deequ.suggestions uses com.amazon.deequ.profiles✕
- Connections
- 8 pairs of types, where a type in com.amazon.deequ.suggestions uses a type in com.amazon.deequ.profiles.
- The types involved
com.amazon.deequ.suggestions.CommonConstraintSuggestion→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.ConstraintSuggestion→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.ConstraintSuggestionResult→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.ConstraintSuggestionRunBuilder→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.ConstraintSuggestionRunner→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.ConstraintSuggestionRunner→com.amazon.deequ.profiles.ColumnProfilescom.amazon.deequ.suggestions.ConstraintSuggestionWithValue→com.amazon.deequ.profiles.ColumnProfilecom.amazon.deequ.suggestions.Rules→com.amazon.deequ.profiles.ColumnProfile
- Direction
- com.amazon.deequ.suggestions uses com.amazon.deequ.profiles, so a change to com.amazon.deequ.profiles can break com.amazon.deequ.suggestions, while a change to com.amazon.deequ.suggestions can't break com.amazon.deequ.profiles.
- Position
- Below the diagonal: com.amazon.deequ.suggestions uses a module listed above it, which is the healthy direction.
39→29 com.amazon.deequ.suggestions uses com.amazon.deequ.suggestions.rules✕
- Connections
- 6 pairs of types, where a type in com.amazon.deequ.suggestions uses a type in com.amazon.deequ.suggestions.rules.
- The types involved
com.amazon.deequ.suggestions.CommonConstraintSuggestion→com.amazon.deequ.suggestions.rules.ConstraintRulecom.amazon.deequ.suggestions.ConstraintSuggestion→com.amazon.deequ.suggestions.rules.ConstraintRulecom.amazon.deequ.suggestions.ConstraintSuggestionRunBuilder→com.amazon.deequ.suggestions.rules.ConstraintRulecom.amazon.deequ.suggestions.ConstraintSuggestionRunner→com.amazon.deequ.suggestions.rules.ConstraintRulecom.amazon.deequ.suggestions.ConstraintSuggestionWithValue→com.amazon.deequ.suggestions.rules.ConstraintRulecom.amazon.deequ.suggestions.Rules→com.amazon.deequ.suggestions.rules.ConstraintRule
- Direction
- com.amazon.deequ.suggestions uses com.amazon.deequ.suggestions.rules, so a change to com.amazon.deequ.suggestions.rules can break com.amazon.deequ.suggestions, while a change to com.amazon.deequ.suggestions can't break com.amazon.deequ.suggestions.rules.
- Position
- Below the diagonal: com.amazon.deequ.suggestions uses a module listed above it, which is the healthy direction.
39→30 com.amazon.deequ.suggestions uses com.amazon.deequ✕
- Connections
- 3 pairs of types, where a type in com.amazon.deequ.suggestions uses a type in com.amazon.deequ.
- The types involved
com.amazon.deequ.suggestions.ConstraintSuggestionResult→com.amazon.deequ.VerificationResultcom.amazon.deequ.suggestions.ConstraintSuggestionRunner→com.amazon.deequ.VerificationResultcom.amazon.deequ.suggestions.ConstraintSuggestions→com.amazon.deequ.VerificationResult
- Direction
- com.amazon.deequ.suggestions uses com.amazon.deequ, so a change to com.amazon.deequ can break com.amazon.deequ.suggestions, while a change to com.amazon.deequ.suggestions can't break com.amazon.deequ.
- Position
- Below the diagonal: com.amazon.deequ.suggestions uses a module listed above it, which is the healthy direction.
40→18 com.amazon.deequ.dqdl.translation.rules uses com.amazon.deequ.analyzers✕
- Connections
- 1 pair of types, where a type in com.amazon.deequ.dqdl.translation.rules uses a type in com.amazon.deequ.analyzers.
- The types involved
com.amazon.deequ.dqdl.translation.rules.DataFreshnessRule→com.amazon.deequ.analyzers.FilteredRowOutcome
- Direction
- com.amazon.deequ.dqdl.translation.rules uses com.amazon.deequ.analyzers, so a change to com.amazon.deequ.analyzers can break com.amazon.deequ.dqdl.translation.rules, while a change to com.amazon.deequ.dqdl.translation.rules can't break com.amazon.deequ.analyzers.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.translation.rules uses a module listed above it, which is the healthy direction.
40→28 com.amazon.deequ.dqdl.translation.rules uses com.amazon.deequ.checks✕
- Connections
- 2 pairs of types, where a type in com.amazon.deequ.dqdl.translation.rules uses a type in com.amazon.deequ.checks.
- The types involved
com.amazon.deequ.dqdl.translation.rules.ColumnLengthRule→com.amazon.deequ.checks.Checkcom.amazon.deequ.dqdl.translation.rules.ColumnValuesRule→com.amazon.deequ.checks.Check
- Direction
- com.amazon.deequ.dqdl.translation.rules uses com.amazon.deequ.checks, so a change to com.amazon.deequ.checks can break com.amazon.deequ.dqdl.translation.rules, while a change to com.amazon.deequ.dqdl.translation.rules can't break com.amazon.deequ.checks.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.translation.rules uses a module listed above it, which is the healthy direction.
40→31 com.amazon.deequ.dqdl.translation.rules uses com.amazon.deequ.dqdl.model✕
- Connections
- 11 pairs of types, where a type in com.amazon.deequ.dqdl.translation.rules uses a type in com.amazon.deequ.dqdl.model.
- The types involved
com.amazon.deequ.dqdl.translation.rules.AggregateMatchRule→com.amazon.deequ.dqdl.model.AggregateOperationcom.amazon.deequ.dqdl.translation.rules.AggregateMatchRule→com.amazon.deequ.dqdl.model.ExecutableRulecom.amazon.deequ.dqdl.translation.rules.ColumnDataTypeRule→com.amazon.deequ.dqdl.model.ColumnDataTypeExecutableRulecom.amazon.deequ.dqdl.translation.rules.ColumnNamesMatchPatternRule→com.amazon.deequ.dqdl.model.ColumnNamesMatchPatternExecutableRulecom.amazon.deequ.dqdl.translation.rules.ColumnValuesRule→com.amazon.deequ.dqdl.model.DeequMetricMappingcom.amazon.deequ.dqdl.translation.rules.CustomSqlRowLevelRule→com.amazon.deequ.dqdl.model.CustomSqlRowLevelExecutableRulecom.amazon.deequ.dqdl.translation.rules.DataFreshnessRule→com.amazon.deequ.dqdl.model.DataFreshnessExecutableRulecom.amazon.deequ.dqdl.translation.rules.DatasetMatchRule→com.amazon.deequ.dqdl.model.DatasetMatchExecutableRulecom.amazon.deequ.dqdl.translation.rules.ReferentialIntegrityRule→com.amazon.deequ.dqdl.model.ReferentialIntegrityExecutableRulecom.amazon.deequ.dqdl.translation.rules.RowCountMatchRule→com.amazon.deequ.dqdl.model.RowCountMatchExecutableRulecom.amazon.deequ.dqdl.translation.rules.SchemaMatchRule→com.amazon.deequ.dqdl.model.SchemaMatchExecutableRule
- Direction
- com.amazon.deequ.dqdl.translation.rules uses com.amazon.deequ.dqdl.model, so a change to com.amazon.deequ.dqdl.model can break com.amazon.deequ.dqdl.translation.rules, while a change to com.amazon.deequ.dqdl.translation.rules can't break com.amazon.deequ.dqdl.model.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.translation.rules uses a module listed above it, which is the healthy direction.
40→37 com.amazon.deequ.dqdl.translation.rules uses com.amazon.deequ.dqdl.translation✕
- Connections
- 25 pairs of types, where a type in com.amazon.deequ.dqdl.translation.rules uses a type in com.amazon.deequ.dqdl.translation.
- The types involved
com.amazon.deequ.dqdl.translation.rules.ColumnCorrelationRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.ColumnCountRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.ColumnExistsRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.ColumnLengthRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.ColumnValuesRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.CompletenessRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.CustomSqlRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.DistinctValuesCountRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.DuplicateRowCountRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.EntropyRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.InterquartileRangeRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.IsCompleteRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.IsPrimaryKeyRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.IsUniqueRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.KurtosisRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.MeanRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.RangeRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.RowCountRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.SkewnessRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.StandardDeviationRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.SumRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.UniqueValueRatioRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.UniquenessRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.VarianceRule→com.amazon.deequ.dqdl.translation.DQDLRuleConvertercom.amazon.deequ.dqdl.translation.rules.ZerosCountRule→com.amazon.deequ.dqdl.translation.DQDLRuleConverter
- Direction
- com.amazon.deequ.dqdl.translation.rules uses com.amazon.deequ.dqdl.translation, so a change to com.amazon.deequ.dqdl.translation can break com.amazon.deequ.dqdl.translation.rules, while a change to com.amazon.deequ.dqdl.translation.rules can't break com.amazon.deequ.dqdl.translation.
- Position
- Below the diagonal: com.amazon.deequ.dqdl.translation.rules uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 27 | High / Critical |
| A05:2025 — Injection | 6 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: 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; Resolve the 83 Orphaned file finding(s) in Knowledge Freshness — start with Distance.scala, DataSynchronization.scala, ConstraintSuggestionRunner.scala; Resolve the 2 Banned license finding(s) in License Compliance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Banned license finding(s) in License Compliance. | +3.5 pts | Low | License Compliance |
| 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. | +5.4 pts | Medium | Architecture documentation |
| Resolve the 83 Orphaned file finding(s) in Knowledge Freshness — start with Distance.scala, DataSynchronization.scala, ConstraintSuggestionRunner.scala. | +5.2 pts | Medium | Knowledge Freshness |
| Resolve the 2 Off-boarding risk finding(s) in Bus Factor. | +1.6 pts | Low | Bus Factor |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +2.1 pts | Medium | Security & performance tooling |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.4 pts | Medium | Release Hygiene |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.4 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/com/amazon/deequ/suggestions/rules/CategoricalRangeRule.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/com/amazon/deequ/analyzers/DataType.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/com/amazon/deequ/constraints/Constraint.scala | 7.1 | Mixed | God Classes: TooManyMethods: Constraint |
| src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnValuesRule.scala | 7.2 | Mixed | Cyclomatic Complexity: ColumnValuesRule.mkNumericCheck (cyclomatic 31) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnLengthRule.scala | 7.4 | Mixed | Cyclomatic Complexity: ColumnLengthRule.mkColumnLengthCheck (cyclomatic 17) |
| src/main/scala/com/amazon/deequ/dqdl/translation/DQDLRuleTranslator.scala | 7.8 | Mixed | Cyclomatic Complexity: DQDLRuleTranslator.toExecutableRule (cyclomatic 26) |
| src/main/scala/com/amazon/deequ/analyzers/HistogramBinned.scala | 7.8 | Mixed | Cyclomatic Complexity: HistogramBinned.computeStateFrom (cyclomatic 17) |
| src/scripts/generate_kb.py | 7.8 | Mixed | Cognitive Complexity: generate_kb.main (cognitive 25) |
| src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnDataTypeRule.scala | 7.8 | Mixed | Cognitive Complexity: ColumnDataTypeRule.toExecutableRule (cognitive 21) |
| src/main/scala/com/amazon/deequ/dqdl/execution/executors/RowCountMatchExecutor.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| src/main/scala/com/amazon/deequ/analyzers/UniqueValueRatio.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (14 corresponding lines) |
| src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunBuilder.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (25 corresponding lines) |
| src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunner.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 46 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 — 46 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, 204 of 381 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.
- 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. 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: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (21953 LoC, 370 module-visible types across 29 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- 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.
- 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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AnalyzerSerializer.serialize at 42. A further 2 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 HdfsStateProvider.persist at 22 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/main/scala/com/amazon/deequ/analyzers/StateProvider.scala (HdfsStateProvider.persist at 22). 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 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with AnalyzerSerializer.serialize (cyclomatic 42), AnalyzerDeserializer.deserialize (cyclomatic 40), ColumnValuesRule.mkNumericCheck (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was ColumnProfiler.extractNumericStatistics at 52.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with ColumnProfiler.extractNumericStatistics (cognitive 52), ColumnValuesRule.mkNumericCheck (cognitive 41). — 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 Cognitive Complexity from 7.5 to about 8.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with AnalysisResultSerde.scala, Constraint.scala, Check.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Constraint.scala. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
16 duplicated block group(s) detected. 3.2 % of the production lines (698 of 21,953) are in a reported copy. A further 17 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 3 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with IsUniqueRule.scala, AnalysisResultSerde.scala, RowCountMatchExecutor.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with CategoricalRangeRule.scala (2), UniqueValueRatio.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Maximum.scala, DfsUtils.scala, ColumnProfiler.scala. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
1 of 12 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with QuantileNonSample.scala. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
163 outdated artifact(s) of 180 resolved by the build, graded against Maven Central. 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
2 of 6 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 9 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
What to do
- Resolve the 2 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (2 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
13 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnValuesRule.scala. Counted over 86 of the 204 production source files in this repository: 89 are under the ~2,400-byte size floor this dimension measures over, and the remaining 29 have no attributable history left to measure.
What to do
- Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
17 deducted task-comment markers across 21953 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 17 TodoComment finding(s) in Explicit Debt — start with AnalysisResultSerde.scala (3), ColumnProfiler.scala (2), VerificationSuiteTest.scala. — One of this dimension's main actionable groups (17 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 4 high, 2 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
22 finding(s): 2 critical, 11 high, 8 medium, 1 low.
What to do
- Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
85 of 115 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/scala/com/amazon/deequ/analyzers/catalyst/HLLConstants.scala. Counted over 115 of the 204 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 83 Orphaned file finding(s) in Knowledge Freshness — start with Distance.scala, DataSynchronization.scala, ConstraintSuggestionRunner.scala. — One of this dimension's main actionable groups (83 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with HLLConstants.scala, Analyzer.scala. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Concentrated knowledge decay 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/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 15 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
AX4 · Dependency direction
AX6 · Interface segregation
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. (×2) — src/main/scala/com/amazon/deequ/analyzers/PatternMatch.scala:109, src/main/scala/com/amazon/deequ/analyzers/catalyst/HLLConstants.scala:19
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)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
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
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — src/test/scala/com/amazon/deequ/KLL/KLLBenchmark.java
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X5 · Nullable reference types
- No build over this repository's 202 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 | 70% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 55% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate | Acceptable, with room to improve. |
| Security | 70% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 80% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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 function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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 — ~24398 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
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its sibling member alignment rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .py, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Maven build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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): 209 value object(s); 2 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, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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: 203 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala, Java and Python were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 20 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: org.openjdk.jmh:jmh-core
- Banned license: org.openjdk.jmh:jmh-generator-annprocess
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 90 finding(s)
- TodoComment src/test/scala/com/amazon/deequ/VerificationSuiteTest.scala:227
- TodoComment src/test/scala/com/amazon/deequ/suggestions/ConstraintSuggestionResultTest.scala:32
- TodoComment src/test/scala/com/amazon/deequ/profiles/ColumnProfilerTest.scala:47
- TodoComment src/test/scala/com/amazon/deequ/KLL/KLLProfileTest.scala:48
- TodoComment src/test/scala/com/amazon/deequ/dqdl/EvaluateDataQualitySpec.scala:573
- TodoComment src/main/scala/com/amazon/deequ/suggestions/rules/CategoricalRangeRule.scala:48
- TodoComment src/main/scala/com/amazon/deequ/suggestions/rules/FractionalCategoricalRangeRule.scala:56
- TodoComment src/main/scala/com/amazon/deequ/suggestions/rules/UniqueIfApproximatelyUniqueRule.scala:35
- TodoComment src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala:783
- TodoComment src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala:843
- TodoComment src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala:870
- TodoComment src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala:83
- TodoComment src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala:463
- TodoComment src/main/scala/com/amazon/deequ/metrics/KLLMetric.scala:92
- TodoComment src/main/scala/com/amazon/deequ/analyzers/DataType.scala:92
- TodoComment src/main/scala/com/amazon/deequ/analyzers/InterquartileRange.scala:39
- TodoComment src/main/scala/com/amazon/deequ/analyzers/runners/KLLRunner.scala:142
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: repository/AnalysisResultSerde.scala src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala
- FileTooLong: constraints/Constraint.scala src/main/scala/com/amazon/deequ/constraints/Constraint.scala
- FileTooLong: checks/Check.scala src/main/scala/com/amazon/deequ/checks/Check.scala
- FileTooLong: profiles/ColumnProfiler.scala src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala
- Edited copy of a member (18 corresponding lines) src/main/scala/com/amazon/deequ/dqdl/translation/rules/IsUniqueRule.scala:29
- Edited copy of a member (18 corresponding lines) src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala:81
- Edited copy of a member (18 corresponding lines) src/main/scala/com/amazon/deequ/dqdl/execution/executors/RowCountMatchExecutor.scala:28
- Duplicated block (11 lines × 2) src/main/scala/com/amazon/deequ/analyzers/UniqueValueRatio.scala:41
- Duplicated block (11 lines × 2) src/main/scala/com/amazon/deequ/suggestions/rules/CategoricalRangeRule.scala:36
- Duplicated block (11 lines × 2) src/main/scala/com/amazon/deequ/suggestions/rules/CategoricalRangeRule.scala:57
- Duplicated block (7 lines × 2) src/main/scala/com/amazon/deequ/analyzers/Maximum.scala:67
- Duplicated block (7 lines × 2) src/main/scala/com/amazon/deequ/io/DfsUtils.scala:77
- Duplicated block (7 lines × 2) src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala:249
- REDACTED
- REDACTED
- Edited copy of a member (19 corresponding lines) src/main/scala/com/amazon/deequ/analyzers/catalyst/StatefulHyperloglogPlus.scala:121
- Edited copy of a member (19 corresponding lines) src/main/scala/com/amazon/deequ/suggestions/rules/CategoricalRangeRule.scala:35
- AnalyzerSerializer.serialize (cyclomatic 42) src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala:249
- AnalyzerDeserializer.deserialize (cyclomatic 40) src/main/scala/com/amazon/deequ/repository/AnalysisResultSerde.scala:503
- ColumnValuesRule.mkNumericCheck (cyclomatic 31) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnValuesRule.scala:60
- ColumnProfiler.extractNumericStatistics (cyclomatic 27) src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala:512
- DQDLRuleTranslator.toExecutableRule (cyclomatic 26) src/main/scala/com/amazon/deequ/dqdl/translation/DQDLRuleTranslator.scala:109
- HistogramBinned.computeStateFrom (cyclomatic 17) src/main/scala/com/amazon/deequ/analyzers/HistogramBinned.scala:127
- ColumnLengthRule.mkColumnLengthCheck (cyclomatic 17) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnLengthRule.scala:48
- ColumnProfiler.extractNumericStatistics (cognitive 52) src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala:512
- ColumnValuesRule.mkNumericCheck (cognitive 41) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnValuesRule.scala:60
- HistogramBinned.computeStateFrom (cognitive 28) src/main/scala/com/amazon/deequ/analyzers/HistogramBinned.scala:127
- ColumnValuesRule.constructComplianceCondition (cognitive 26) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnValuesRule.scala:236
- generate_kb.main (cognitive 25) src/scripts/generate_kb.py:103
- DQDLRuleTranslator.toExecutableRule (cognitive 22) src/main/scala/com/amazon/deequ/dqdl/translation/DQDLRuleTranslator.scala:109
- DataSynchronization.columnMatchRowLevel (cognitive 21) src/main/scala/com/amazon/deequ/comparison/DataSynchronization.scala:155
- ColumnDataTypeRule.toExecutableRule (cognitive 21) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnDataTypeRule.scala:45
- ColumnDataTypeRule.castColumnToSparkType (cognitive 20) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnDataTypeRule.scala:107
- generate_kb.summarize_tier2 (cognitive 20) src/scripts/generate_kb.py:63
- RuleEvaluationHelper.evaluateRuleAgainstColumn (cognitive 19) src/main/scala/com/amazon/deequ/dqdl/util/RuleEvaluationHelper.scala:29
- DataTypeHistogram.determineType (cognitive 17) src/main/scala/com/amazon/deequ/analyzers/DataType.scala:116
- ReferentialIntegrity.validateParameters (cognitive 17) src/main/scala/com/amazon/deequ/comparison/ReferentialIntegrity.scala:139
- ColumnValuesRule.validateDateOperandCount (cognitive 17) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnValuesRule.scala:299
- ColumnLengthRule.mkColumnLengthCheck (cognitive 16) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnLengthRule.scala:48
- TooManyMethods: Constraint src/main/scala/com/amazon/deequ/constraints/Constraint.scala:107
- REDACTED
- REDACTED
- Edited copy of a member (27 corresponding lines) src/main/scala/com/amazon/deequ/constraints/Constraint.scala:1216
- Edited copy of a member (22 corresponding lines) src/main/scala/com/amazon/deequ/metrics/HistogramBinnedMetric.scala:53
- Edited copy of a member (14 corresponding lines) src/main/scala/com/amazon/deequ/analyzers/UniqueValueRatio.scala:38
- Edited copy of a member (12 corresponding lines) src/main/scala/com/amazon/deequ/analyzers/MaxLength.scala:60
- Edited copy of a member (25 corresponding lines) src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunBuilder.scala:46
- Edited copy of a member (16 corresponding lines) src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunner.scala:92
- Edited copies of one member (3 members, 5+ corresponding lines) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnCountRule.scala:26
- Edited copies of one member (4 members, 14+ corresponding lines) src/main/scala/com/amazon/deequ/constraints/Constraint.scala:661
- Edited copies of one member (5 members, 15+ corresponding lines) src/main/scala/com/amazon/deequ/analyzers/Correlation.scala:81
- Edited copy of a member (8 corresponding lines) src/main/scala/com/amazon/deequ/analyzers/StandardDeviation.scala:37
- Edited copy of a member (6 corresponding lines) src/main/scala/com/amazon/deequ/dqdl/translation/rules/SchemaMatchRule.scala:27
- Edited copy of a member (15 corresponding lines) src/main/scala/com/amazon/deequ/dqdl/execution/executors/ColumnDataTypeExecutor.scala:28
- Duplicated block (16 lines × 2) src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunBuilder.scala:51
- Duplicated block (14 lines × 2) src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunner.scala:94
- Duplicated block (13 lines × 2) src/main/scala/com/amazon/deequ/dqdl/execution/executors/RowCountMatchExecutor.scala:33
- Duplicated block (12 lines × 2) src/main/scala/com/amazon/deequ/constraints/Constraint.scala:1217
- Duplicated block (9–10 lines × 2) src/main/scala/com/amazon/deequ/analyzers/Kurtosis.scala:46
- Duplicated block (10 lines × 2) src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnLengthRule.scala:97
- Duplicated block (6 lines × 2) src/main/scala/com/amazon/deequ/analyzers/Histogram.scala:105
- Duplicated block (4–5 lines × 3) src/main/scala/com/amazon/deequ/dqdl/translation/rules/IsPrimaryKeyRule.scala:31
- Duplicated block (5 lines × 2) src/main/scala/com/amazon/deequ/analyzers/Completeness.scala:35
- Duplicated block (15 lines × 2) src/main/scala/com/amazon/deequ/analyzers/runners/AnalysisRunner.scala:260
- Low cohesion: QuantileNonSample (LCOM4 5) src/main/scala/com/amazon/deequ/analyzers/QuantileNonSample.scala:25
Minor — 110 finding(s)
- Orphaned file src/main/scala/com/amazon/deequ/analyzers/Distance.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/comparison/DataSynchronization.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/suggestions/ConstraintSuggestionRunner.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/VerificationSuite.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/VerificationRunBuilder.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/suggestions/ConstraintSuggestionRunBuilder.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/analyzers/catalyst/StatefulHyperloglogPlus.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/anomalydetection/seasonal/HoltWinters.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/comparison/ReferentialIntegrity.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/profiles/ColumnProfilerRunBuilder.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/schema/RowLevelSchemaValidator.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/analyzers/applicability/Applicability.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/repository/fs/FileSystemMetricsRepository.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/VerificationResult.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/analyzers/runners/KLLRunner.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/constraints/AnalysisBasedConstraint.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/analyzers/DataType.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/analyzers/KLLSketch.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/anomalydetection/OnlineNormalStrategy.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/dqdl/translation/rules/ColumnLengthRule.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/analyzers/runners/AnalysisRunBuilder.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/dqdl/execution/DefaultOperandEvaluator.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/dqdl/translation/RuleOutcomeTranslator.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/repository/sparktable/SparkMetricsRepository.scala:1
- Orphaned file src/main/scala/com/amazon/deequ/analyzers/PatternMatch.scala:1
- Duplicated predicate src/main/scala/com/amazon/deequ/analyzers/Histogram.scala:106
- Duplicated predicate src/main/scala/com/amazon/deequ/repository/fs/FileSystemMetricsRepository.scala:158
- Duplicated predicate src/main/scala/com/amazon/deequ/anomalydetection/BatchNormalStrategy.scala:41
- Duplicated predicate src/main/scala/com/amazon/deequ/anomalydetection/BatchNormalStrategy.scala:38
- Duplicated predicate src/main/scala/com/amazon/deequ/suggestions/rules/CategoricalRangeRule.scala:36
- Duplicated predicate src/main/scala/com/amazon/deequ/analyzers/ApproxQuantile.scala:63
- Duplicated predicate src/main/scala/com/amazon/deequ/profiles/ColumnProfiler.scala:252
- Duplicated predicate src/main/scala/com/amazon/deequ/dqdl/translation/DQDLRuleTranslator.scala:118
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Most significant orphaned file src/main/scala/com/amazon/deequ/analyzers/catalyst/HLLConstants.scala:1
- Most significant orphaned file src/main/scala/com/amazon/deequ/analyzers/Analyzer.scala:1
- Blanket warning suppression src/main/scala/com/amazon/deequ/analyzers/PatternMatch.scala:109
- Blanket warning suppression src/main/scala/com/amazon/deequ/analyzers/catalyst/HLLConstants.scala:19
- Further sole-owners (lower concentration)
- REDACTED
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No changelog
- Benchmarks don't track allocations src/test/scala/com/amazon/deequ/KLL/KLLBenchmark.java
- Scala's null is not held to the type system everywhere
Minor — 161 finding(s)
- Outdated (compile): org.apache.spark:spark-streaming_2.12
- Outdated (compile): org.apache.orc:orc-mapreduce
- Outdated (compile): org.apache.spark:spark-tags_2.12
- Outdated (compile): com.clearspring.analytics:stream
- Outdated (compile): org.glassfish.hk2:hk2-locator
- Outdated (compile): org.glassfish.hk2:hk2-utils
- Outdated (compile): net.sf.py4j:py4j
- Outdated (compile): jakarta.servlet:jakarta.servlet-api
- Outdated (compile): com.thoughtworks.paranamer:paranamer
- Outdated (compile): io.netty:netty-handler
- Outdated (compile): com.fasterxml.jackson.core:jackson-core
- Outdated (compile): org.threeten:threeten-extra
- Outdated (compile): org.json4s:json4s-jackson_2.12
- Outdated (compile): com.google.code.findbugs:jsr305
- Outdated (compile): org.apache.commons:commons-lang3
- Outdated (compile): io.netty:netty-common
- Outdated (compile): org.objenesis:objenesis
- Outdated (compile): org.apache.spark:spark-network-common_2.12
- Outdated (compile): joda-time:joda-time
- Outdated (compile): jakarta.ws.rs:jakarta.ws.rs-api
- Outdated (compile): org.apache.orc:orc-shims
- Outdated (compile): org.glassfish.hk2.external:aopalliance-repackaged
- Outdated (compile): org.apache.spark:spark-sketch_2.12
- Outdated (compile): org.codehaus.janino:commons-compiler
- Outdated (compile): org.typelevel:algebra_2.12
- Outdated (test): org.scala-lang:scala-compiler
- Outdated (test): net.bytebuddy:byte-buddy-agent
- Outdated (test): org.scalamock:scalamock_2.12
- Outdated (test): org.scalatest:scalatest_2.12
- Outdated (test): org.apache.datasketches:datasketches-java
- Outdated (test): org.openjdk.jmh:jmh-core
- Outdated (test): org.scalactic:scalactic_2.12
- Outdated (test): net.bytebuddy:byte-buddy
- Outdated (test): net.sf.jopt-simple:jopt-simple
- Outdated (test): org.mockito:mockito-core
- Outdated (test): org.openjdk.jmh:jmh-generator-annprocess
- Outdated (test): org.apache.datasketches:datasketches-memory
- Outdated (test): org.apache.iceberg:iceberg-spark-runtime-3.3_2.12
- Outdated (runtime): org.apache.parquet:parquet-jackson
- Outdated (runtime): org.roaringbitmap:shims
- Outdated (runtime): commons-logging:commons-logging
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-d0c3dd2cdd3e47fb82a05389164c3989/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d0c3dd2cdd3e47fb82a05389164c3989/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 . | 6 | 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 . | 22 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |