Executive summary
airbnb/chronon is rated At risk because critical security findings are open. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 49 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 37, is the weakest lens and counts most in the score. The best first steps are adding automated security scanning and documenting the recovery plan, each worth about 7 points. Raising Production Readiness to 62 would lift the score to about 58.
Seventeen settings leave the servers or containers unsafe. Sixteen weaknesses in the code could be used by an attacker, and eight known security holes in the packages the code depends on can be used by attackers. Correcting the unsafe settings, fixing the weaknesses the scanner points to and updating the vulnerable packages would close these risks. Pinning each tool to an exact version would fix the three pipeline tools referenced by a changeable name, and the two pipeline steps that run downloads without checking them need each download checked against a known checksum first.
The product code is 33,780 lines, about €69,000 to rebuild.
If Production Readiness rose from 37 to 62, the lowest score rated Strong, the score would rise from 49 to about 58.
New since the last survey: 1 finding
- Dependency Vulnerabilities · REDACTED
Rebuild cost: about €69,000 · Estimate
| Cost to rebuild | €23,000 to €120,000, for 384 to 1,220 hours of work, about 0.5 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.7 at a score of 49. 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: 33,780 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 ai.chronon.aggregator.row.StatsGenerator | 2 ai.chronon.online.FetcherCache.BatchIrCache | 3 ai.chronon.online.KVStore | 4 api.py.ai.chronon.repo.join_backfill | 5 ai.chronon.api.Builders | 6 ai.chronon.api | 7 ai.chronon.online.FetcherModelUtils | 8 ai.chronon.online.Metrics | 9 ai.chronon.aggregator.base | 10 ai.chronon.api.Extensions | 11 ai.chronon.online.CatalystUtil | 12 ai.chronon.spark.catalog | 13 ai.chronon.aggregator.row | 14 ai.chronon.spark.Extensions | 15 ai.chronon.aggregator.windowing.TwoStackLiteAggregator | 16 ai.chronon.aggregator.windowing | 17 ai.chronon.online.FetcherCache | 18 ai.chronon.spark | 19 ai.chronon.online.serde | 20 ai.chronon.online.Extensions | 21 ai.chronon.online.Fetcher | 22 ai.chronon.online | 23 ai.chronon.flink.window | 24 ai.chronon.online.ExternalSourceRegistry | 25 ai.chronon.online.FetcherBase | 26 ai.chronon.quickstart.online | 27 ai.chronon.spark.Driver | 28 ai.chronon.spark.stats | 29 ai.chronon.spark.streaming.JoinSourceRunner | 30 ai.chronon.flink | 31 ai.chronon.spark.Driver.CompareJoinQuery | 32 ai.chronon.spark.Driver.DailyStats | 33 ai.chronon.spark.Driver.GroupByBackfill | 34 ai.chronon.spark.Driver.JoinBackfill | 35 ai.chronon.spark.Driver.JoinBackfillFinal | 36 ai.chronon.spark.Driver.JoinBackfillLeft | 37 ai.chronon.spark.Driver.LabelJoin | 38 ai.chronon.spark.Driver.LogFlattener | 39 ai.chronon.spark.Driver.LogStats | 40 ai.chronon.spark.streaming |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ai.chronon.aggregator.row.StatsGenerator | ||||||||||||||||||||||||||||||||||||||||
| 2 ai.chronon.online.FetcherCache.BatchIrCache | ||||||||||||||||||||||||||||||||||||||||
| 3 ai.chronon.online.KVStore | ||||||||||||||||||||||||||||||||||||||||
| 4 api.py.ai.chronon.repo.join_backfill | ||||||||||||||||||||||||||||||||||||||||
| 5 ai.chronon.api.Builders | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 ai.chronon.api | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 ai.chronon.online.FetcherModelUtils | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 ai.chronon.online.Metrics | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 ai.chronon.aggregator.base | 17 | |||||||||||||||||||||||||||||||||||||||
| 10 ai.chronon.api.Extensions | 17 | 8 | ||||||||||||||||||||||||||||||||||||||
| 11 ai.chronon.online.CatalystUtil | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 ai.chronon.spark.catalog | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 ai.chronon.aggregator.row | 1 | 2 | 16 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 ai.chronon.spark.Extensions | 4 | 2 | 5 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 ai.chronon.aggregator.windowing.TwoStackLiteAggregator | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 ai.chronon.aggregator.windowing | 2 | 5 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 17 ai.chronon.online.FetcherCache | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 ai.chronon.spark | 20 | 18 | 3 | 1 | 8 | 1 | 2 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||
| 19 ai.chronon.online.serde | 12 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 ai.chronon.online.Extensions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 ai.chronon.online.Fetcher | 1 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 ai.chronon.online | 1 | 2 | 13 | 11 | 1 | 5 | 2 | 1 | 1 | 3 | 4 | 1 | 4 | 14 | ||||||||||||||||||||||||||
| 23 ai.chronon.flink.window | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 ai.chronon.online.ExternalSourceRegistry | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 ai.chronon.online.FetcherBase | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 ai.chronon.quickstart.online | 3 | 1 | 4 | 12 | ||||||||||||||||||||||||||||||||||||
| 27 ai.chronon.spark.Driver | 3 | 19 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 ai.chronon.spark.stats | 1 | 1 | 2 | 3 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 ai.chronon.spark.streaming.JoinSourceRunner | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 ai.chronon.flink | 4 | 2 | 1 | 1 | 6 | 1 | ||||||||||||||||||||||||||||||||||
| 31 ai.chronon.spark.Driver.CompareJoinQuery | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 ai.chronon.spark.Driver.DailyStats | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 ai.chronon.spark.Driver.GroupByBackfill | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 34 ai.chronon.spark.Driver.JoinBackfill | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 35 ai.chronon.spark.Driver.JoinBackfillFinal | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 36 ai.chronon.spark.Driver.JoinBackfillLeft | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 37 ai.chronon.spark.Driver.LabelJoin | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 ai.chronon.spark.Driver.LogFlattener | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 ai.chronon.spark.Driver.LogStats | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 ai.chronon.spark.streaming | 3 | 3 | 2 | 1 | 11 | 1 |
5→6 ai.chronon.api.Builders uses ai.chronon.api part of a loop✕
- Connections
- 3 pairs of types, where a type in ai.chronon.api.Builders uses a type in ai.chronon.api.
- The types involved
ai.chronon.api.Builders.ContextualSource→ai.chronon.api.StructFieldai.chronon.api.Builders.ExternalSource→ai.chronon.api.DataTypeai.chronon.api.Builders.Model→ai.chronon.api.DataType
- Direction
- ai.chronon.api.Builders uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.api.Builders, while a change to ai.chronon.api.Builders can't break ai.chronon.api.
- 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.
6→5 ai.chronon.api uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.api uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.api.ExternalJoinPart→ai.chronon.api.Builders.JoinPart
- Direction
- ai.chronon.api uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.api, while a change to ai.chronon.api can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.api uses a module listed above it, which is the healthy direction.
7→5 ai.chronon.online.FetcherModelUtils uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.FetcherModelUtils uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.online.FetcherModelUtils.ModelTransformInput→ai.chronon.api.Builders.ModelTransform
- Direction
- ai.chronon.online.FetcherModelUtils uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.online.FetcherModelUtils, while a change to ai.chronon.online.FetcherModelUtils can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.online.FetcherModelUtils uses a module listed above it, which is the healthy direction.
8→5 ai.chronon.online.Metrics uses ai.chronon.api.Builders✕
- Connections
- 4 pairs of types, where a type in ai.chronon.online.Metrics uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.online.Metrics.Context→ai.chronon.api.Builders.GroupByai.chronon.online.Metrics.Context→ai.chronon.api.Builders.Joinai.chronon.online.Metrics.Context→ai.chronon.api.Builders.JoinPartai.chronon.online.Metrics.Context→ai.chronon.api.Builders.StagingQuery
- Direction
- ai.chronon.online.Metrics uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.online.Metrics, while a change to ai.chronon.online.Metrics can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.online.Metrics uses a module listed above it, which is the healthy direction.
8→22 ai.chronon.online.Metrics uses ai.chronon.online part of a loop✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.Metrics uses a type in ai.chronon.online.
- The types involved
ai.chronon.online.Metrics.Context→ai.chronon.online.TTLCache
- Direction
- ai.chronon.online.Metrics uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.online.Metrics, while a change to ai.chronon.online.Metrics can't break ai.chronon.online.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→6 ai.chronon.aggregator.base uses ai.chronon.api✕
- Connections
- 17 pairs of types, where a type in ai.chronon.aggregator.base uses a type in ai.chronon.api.
- The types involved
ai.chronon.aggregator.base.ApproxDistinctCount→ai.chronon.api.DataTypeai.chronon.aggregator.base.ApproxHistogram→ai.chronon.api.DataTypeai.chronon.aggregator.base.ApproxPercentiles→ai.chronon.api.DataTypeai.chronon.aggregator.base.Average→ai.chronon.api.DataTypeai.chronon.aggregator.base.BaseAggregator→ai.chronon.api.DataTypeai.chronon.aggregator.base.Count→ai.chronon.api.DataTypeai.chronon.aggregator.base.FrequentItems→ai.chronon.api.DataTypeai.chronon.aggregator.base.Histogram→ai.chronon.api.DataTypeai.chronon.aggregator.base.MomentAggregator→ai.chronon.api.DataTypeai.chronon.aggregator.base.Order→ai.chronon.api.DataTypeai.chronon.aggregator.base.OrderByLimit→ai.chronon.api.DataTypeai.chronon.aggregator.base.OrderByLimitTimed→ai.chronon.api.DataTypeai.chronon.aggregator.base.Sum→ai.chronon.api.DataTypeai.chronon.aggregator.base.TimeOrdered→ai.chronon.api.DataTypeai.chronon.aggregator.base.TimeTuple→ai.chronon.api.DataTypeai.chronon.aggregator.base.UniqueCount→ai.chronon.api.DataTypeai.chronon.aggregator.base.Variance→ai.chronon.api.DataType
- Direction
- ai.chronon.aggregator.base uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.aggregator.base, while a change to ai.chronon.aggregator.base can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.aggregator.base uses a module listed above it, which is the healthy direction.
10→5 ai.chronon.api.Extensions uses ai.chronon.api.Builders✕
- Connections
- 17 pairs of types, where a type in ai.chronon.api.Extensions uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.api.Extensions.AggregationOps→ai.chronon.api.Builders.AggregationPartai.chronon.api.Extensions.BootstrapPartOps→ai.chronon.api.Builders.BootstrapPartai.chronon.api.Extensions.BootstrapPartOps→ai.chronon.api.Builders.Joinai.chronon.api.Extensions.DerivationOps→ai.chronon.api.Builders.Derivationai.chronon.api.Extensions.ExternalPartOps→ai.chronon.api.Builders.ExternalPartai.chronon.api.Extensions.ExternalSourceOps→ai.chronon.api.Builders.ExternalSourceai.chronon.api.Extensions.GroupByOps→ai.chronon.api.Builders.Derivationai.chronon.api.Extensions.GroupByOps→ai.chronon.api.Builders.GroupByai.chronon.api.Extensions.GroupByOps→ai.chronon.api.Builders.Queryai.chronon.api.Extensions.GroupByOps→ai.chronon.api.Builders.Sourceai.chronon.api.Extensions.JoinPartOps→ai.chronon.api.Builders.JoinPartai.chronon.api.Extensions.LabelPartOps→ai.chronon.api.Builders.LabelPartai.chronon.api.Extensions.MetadataOps→ai.chronon.api.Builders.MetaDataai.chronon.api.Extensions.SourceOps→ai.chronon.api.Builders.Queryai.chronon.api.Extensions.SourceOps→ai.chronon.api.Builders.Sourceai.chronon.api.Extensions.UnpackedAggregations→ai.chronon.api.Builders.AggregationPartai.chronon.api.Extensions.WindowMapping→ai.chronon.api.Builders.AggregationPart
- Direction
- ai.chronon.api.Extensions uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.api.Extensions, while a change to ai.chronon.api.Extensions can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.api.Extensions uses a module listed above it, which is the healthy direction.
10→6 ai.chronon.api.Extensions uses ai.chronon.api✕
- Connections
- 8 pairs of types, where a type in ai.chronon.api.Extensions uses a type in ai.chronon.api.
- The types involved
ai.chronon.api.Extensions.DataFieldOps→ai.chronon.api.StructFieldai.chronon.api.Extensions.ExternalPartOps→ai.chronon.api.StructFieldai.chronon.api.Extensions.ExternalSourceOps→ai.chronon.api.StructFieldai.chronon.api.Extensions.GroupByOps→ai.chronon.api.DataModelai.chronon.api.Extensions.JoinPartOps→ai.chronon.api.StructFieldai.chronon.api.Extensions.ModelOps→ai.chronon.api.StructFieldai.chronon.api.Extensions.ModelTransformOps→ai.chronon.api.StructFieldai.chronon.api.Extensions.SourceOps→ai.chronon.api.DataModel
- Direction
- ai.chronon.api.Extensions uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.api.Extensions, while a change to ai.chronon.api.Extensions can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.api.Extensions uses a module listed above it, which is the healthy direction.
11→6 ai.chronon.online.CatalystUtil uses ai.chronon.api✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.CatalystUtil uses a type in ai.chronon.api.
- The types involved
ai.chronon.online.CatalystUtil.PoolKey→ai.chronon.api.StructType
- Direction
- ai.chronon.online.CatalystUtil uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.online.CatalystUtil, while a change to ai.chronon.online.CatalystUtil can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.online.CatalystUtil uses a module listed above it, which is the healthy direction.
12→5 ai.chronon.spark.catalog uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.catalog uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.catalog.TableUtils→ai.chronon.api.Builders.Query
- Direction
- ai.chronon.spark.catalog uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.catalog, while a change to ai.chronon.spark.catalog can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.catalog uses a module listed above it, which is the healthy direction.
12→6 ai.chronon.spark.catalog uses ai.chronon.api✕
- Connections
- 4 pairs of types, where a type in ai.chronon.spark.catalog uses a type in ai.chronon.api.
- The types involved
ai.chronon.spark.catalog.TableUtils→ai.chronon.api.DataTypeai.chronon.spark.catalog.TableUtils→ai.chronon.api.PartitionSpecai.chronon.spark.catalog.TableUtils→ai.chronon.api.Rowai.chronon.spark.catalog.TableUtils→ai.chronon.api.StructType
- Direction
- ai.chronon.spark.catalog uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.spark.catalog, while a change to ai.chronon.spark.catalog can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.spark.catalog uses a module listed above it, which is the healthy direction.
12→14 ai.chronon.spark.catalog uses ai.chronon.spark.Extensions part of a loop✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.catalog uses a type in ai.chronon.spark.Extensions.
- The types involved
ai.chronon.spark.catalog.TableUtils→ai.chronon.spark.Extensions.DfStats
- Direction
- ai.chronon.spark.catalog uses ai.chronon.spark.Extensions, so a change to ai.chronon.spark.Extensions can break ai.chronon.spark.catalog, while a change to ai.chronon.spark.catalog can't break ai.chronon.spark.Extensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→18 ai.chronon.spark.catalog uses ai.chronon.spark part of a loop✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.catalog uses a type in ai.chronon.spark.
- The types involved
ai.chronon.spark.catalog.TableUtils→ai.chronon.spark.PartitionRange
- Direction
- ai.chronon.spark.catalog uses ai.chronon.spark, so a change to ai.chronon.spark can break ai.chronon.spark.catalog, while a change to ai.chronon.spark.catalog can't break ai.chronon.spark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 ai.chronon.aggregator.row uses ai.chronon.aggregator.row.StatsGenerator✕
- Connections
- 1 pair of types, where a type in ai.chronon.aggregator.row uses a type in ai.chronon.aggregator.row.StatsGenerator.
- The types involved
ai.chronon.aggregator.row.StatsGenerator→ai.chronon.aggregator.row.StatsGenerator.MetricTransform
- Direction
- ai.chronon.aggregator.row uses ai.chronon.aggregator.row.StatsGenerator, so a change to ai.chronon.aggregator.row.StatsGenerator can break ai.chronon.aggregator.row, while a change to ai.chronon.aggregator.row can't break ai.chronon.aggregator.row.StatsGenerator.
- Position
- Below the diagonal: ai.chronon.aggregator.row uses a module listed above it, which is the healthy direction.
13→5 ai.chronon.aggregator.row uses ai.chronon.api.Builders✕
- Connections
- 2 pairs of types, where a type in ai.chronon.aggregator.row uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.aggregator.row.RowAggregator→ai.chronon.api.Builders.AggregationPartai.chronon.aggregator.row.StatsGenerator→ai.chronon.api.Builders.AggregationPart
- Direction
- ai.chronon.aggregator.row uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.aggregator.row, while a change to ai.chronon.aggregator.row can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.aggregator.row uses a module listed above it, which is the healthy direction.
13→6 ai.chronon.aggregator.row uses ai.chronon.api✕
- Connections
- 16 pairs of types, where a type in ai.chronon.aggregator.row uses a type in ai.chronon.api.
- The types involved
ai.chronon.aggregator.row.BucketedColumnAggregator→ai.chronon.api.Rowai.chronon.aggregator.row.ColumnAggregator→ai.chronon.api.DataTypeai.chronon.aggregator.row.ColumnAggregator→ai.chronon.api.Rowai.chronon.aggregator.row.DirectColumnAggregator→ai.chronon.api.DataTypeai.chronon.aggregator.row.DirectColumnAggregator→ai.chronon.api.Rowai.chronon.aggregator.row.Dispatcher→ai.chronon.api.Rowai.chronon.aggregator.row.ElementWiseAggregator→ai.chronon.api.Rowai.chronon.aggregator.row.ElementWiseAggregatorBase→ai.chronon.api.DataTypeai.chronon.aggregator.row.MapColumnAggregator→ai.chronon.api.Rowai.chronon.aggregator.row.MapColumnAggregatorBase→ai.chronon.api.DataTypeai.chronon.aggregator.row.RowAggregator→ai.chronon.api.DataTypeai.chronon.aggregator.row.RowAggregator→ai.chronon.api.Rowai.chronon.aggregator.row.SimpleDispatcher→ai.chronon.api.Rowai.chronon.aggregator.row.StatsGenerator→ai.chronon.api.StructTypeai.chronon.aggregator.row.TimedDispatcher→ai.chronon.api.Rowai.chronon.aggregator.row.VectorDispatcher→ai.chronon.api.Row
- Direction
- ai.chronon.aggregator.row uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.aggregator.row, while a change to ai.chronon.aggregator.row can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.aggregator.row uses a module listed above it, which is the healthy direction.
13→9 ai.chronon.aggregator.row uses ai.chronon.aggregator.base✕
- Connections
- 1 pair of types, where a type in ai.chronon.aggregator.row uses a type in ai.chronon.aggregator.base.
- The types involved
ai.chronon.aggregator.row.RowAggregator→ai.chronon.aggregator.base.SimpleAggregator
- Direction
- ai.chronon.aggregator.row uses ai.chronon.aggregator.base, so a change to ai.chronon.aggregator.base can break ai.chronon.aggregator.row, while a change to ai.chronon.aggregator.row can't break ai.chronon.aggregator.base.
- Position
- Below the diagonal: ai.chronon.aggregator.row uses a module listed above it, which is the healthy direction.
14→6 ai.chronon.spark.Extensions uses ai.chronon.api✕
- Connections
- 4 pairs of types, where a type in ai.chronon.spark.Extensions uses a type in ai.chronon.api.
- The types involved
ai.chronon.spark.Extensions.DataframeOps→ai.chronon.api.DataTypeai.chronon.spark.Extensions.InternalRowOps→ai.chronon.api.Rowai.chronon.spark.Extensions.InternalRowOps→ai.chronon.api.StructTypeai.chronon.spark.Extensions.StructTypeOps→ai.chronon.api.StructType
- Direction
- ai.chronon.spark.Extensions uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.spark.Extensions, while a change to ai.chronon.spark.Extensions can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.spark.Extensions uses a module listed above it, which is the healthy direction.
14→12 ai.chronon.spark.Extensions uses ai.chronon.spark.catalog✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark.Extensions uses a type in ai.chronon.spark.catalog.
- The types involved
ai.chronon.spark.Extensions.DataframeOps→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.Extensions.DfWithStats→ai.chronon.spark.catalog.TableUtils
- Direction
- ai.chronon.spark.Extensions uses ai.chronon.spark.catalog, so a change to ai.chronon.spark.catalog can break ai.chronon.spark.Extensions, while a change to ai.chronon.spark.Extensions can't break ai.chronon.spark.catalog.
- Position
- Below the diagonal: ai.chronon.spark.Extensions uses a module listed above it, which is the healthy direction.
14→18 ai.chronon.spark.Extensions uses ai.chronon.spark part of a loop✕
- Connections
- 5 pairs of types, where a type in ai.chronon.spark.Extensions uses a type in ai.chronon.spark.
- The types involved
ai.chronon.spark.Extensions.DataframeOps→ai.chronon.spark.PartitionRangeai.chronon.spark.Extensions.DataframeOps→ai.chronon.spark.TimeRangeai.chronon.spark.Extensions.DfStats→ai.chronon.spark.PartitionRangeai.chronon.spark.Extensions.DfWithStats→ai.chronon.spark.PartitionRangeai.chronon.spark.Extensions.DfWithStats→ai.chronon.spark.TimeRange
- Direction
- ai.chronon.spark.Extensions uses ai.chronon.spark, so a change to ai.chronon.spark can break ai.chronon.spark.Extensions, while a change to ai.chronon.spark.Extensions can't break ai.chronon.spark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→19 ai.chronon.spark.Extensions uses ai.chronon.online.serde part of a loop✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Extensions uses a type in ai.chronon.online.serde.
- The types involved
ai.chronon.spark.Extensions.StructTypeOps→ai.chronon.online.serde.AvroCodec
- Direction
- ai.chronon.spark.Extensions uses ai.chronon.online.serde, so a change to ai.chronon.online.serde can break ai.chronon.spark.Extensions, while a change to ai.chronon.spark.Extensions can't break ai.chronon.online.serde.
- 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→13 ai.chronon.aggregator.windowing.TwoStackLiteAggregator uses ai.chronon.aggregator.row✕
- Connections
- 1 pair of types, where a type in ai.chronon.aggregator.windowing.TwoStackLiteAggregator uses a type in ai.chronon.aggregator.row.
- The types involved
ai.chronon.aggregator.windowing.TwoStackLiteAggregator.PerWindowAggregator→ai.chronon.aggregator.row.RowAggregator
- Direction
- ai.chronon.aggregator.windowing.TwoStackLiteAggregator uses ai.chronon.aggregator.row, so a change to ai.chronon.aggregator.row can break ai.chronon.aggregator.windowing.TwoStackLiteAggregator, while a change to ai.chronon.aggregator.windowing.TwoStackLiteAggregator can't break ai.chronon.aggregator.row.
- Position
- Below the diagonal: ai.chronon.aggregator.windowing.TwoStackLiteAggregator uses a module listed above it, which is the healthy direction.
16→5 ai.chronon.aggregator.windowing uses ai.chronon.api.Builders✕
- Connections
- 2 pairs of types, where a type in ai.chronon.aggregator.windowing uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.aggregator.windowing.ResolutionUtils→ai.chronon.api.Builders.GroupByai.chronon.aggregator.windowing.SawtoothAggregator→ai.chronon.api.Builders.AggregationPart
- Direction
- ai.chronon.aggregator.windowing uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.aggregator.windowing, while a change to ai.chronon.aggregator.windowing can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.aggregator.windowing uses a module listed above it, which is the healthy direction.
16→6 ai.chronon.aggregator.windowing uses ai.chronon.api✕
- Connections
- 5 pairs of types, where a type in ai.chronon.aggregator.windowing uses a type in ai.chronon.api.
- The types involved
ai.chronon.aggregator.windowing.HopsAggregator→ai.chronon.api.Rowai.chronon.aggregator.windowing.SawtoothAggregator→ai.chronon.api.Rowai.chronon.aggregator.windowing.SawtoothMutationAggregator→ai.chronon.api.Rowai.chronon.aggregator.windowing.SawtoothOnlineAggregator→ai.chronon.api.Rowai.chronon.aggregator.windowing.TwoStackLiteAggregator→ai.chronon.api.Row
- Direction
- ai.chronon.aggregator.windowing uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.aggregator.windowing, while a change to ai.chronon.aggregator.windowing can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.aggregator.windowing uses a module listed above it, which is the healthy direction.
16→10 ai.chronon.aggregator.windowing uses ai.chronon.api.Extensions✕
- Connections
- 1 pair of types, where a type in ai.chronon.aggregator.windowing uses a type in ai.chronon.api.Extensions.
- The types involved
ai.chronon.aggregator.windowing.SawtoothAggregator→ai.chronon.api.Extensions.WindowMapping
- Direction
- ai.chronon.aggregator.windowing uses ai.chronon.api.Extensions, so a change to ai.chronon.api.Extensions can break ai.chronon.aggregator.windowing, while a change to ai.chronon.aggregator.windowing can't break ai.chronon.api.Extensions.
- Position
- Below the diagonal: ai.chronon.aggregator.windowing uses a module listed above it, which is the healthy direction.
16→13 ai.chronon.aggregator.windowing uses ai.chronon.aggregator.row✕
- Connections
- 1 pair of types, where a type in ai.chronon.aggregator.windowing uses a type in ai.chronon.aggregator.row.
- The types involved
ai.chronon.aggregator.windowing.TwoStackLiteAggregator→ai.chronon.aggregator.row.RowAggregator
- Direction
- ai.chronon.aggregator.windowing uses ai.chronon.aggregator.row, so a change to ai.chronon.aggregator.row can break ai.chronon.aggregator.windowing, while a change to ai.chronon.aggregator.windowing can't break ai.chronon.aggregator.row.
- Position
- Below the diagonal: ai.chronon.aggregator.windowing uses a module listed above it, which is the healthy direction.
16→15 ai.chronon.aggregator.windowing uses ai.chronon.aggregator.windowing.TwoStackLiteAggregator✕
- Connections
- 1 pair of types, where a type in ai.chronon.aggregator.windowing uses a type in ai.chronon.aggregator.windowing.TwoStackLiteAggregator.
- The types involved
ai.chronon.aggregator.windowing.TwoStackLiteAggregator→ai.chronon.aggregator.windowing.TwoStackLiteAggregator.PerWindowAggregator
- Direction
- ai.chronon.aggregator.windowing uses ai.chronon.aggregator.windowing.TwoStackLiteAggregator, so a change to ai.chronon.aggregator.windowing.TwoStackLiteAggregator can break ai.chronon.aggregator.windowing, while a change to ai.chronon.aggregator.windowing can't break ai.chronon.aggregator.windowing.TwoStackLiteAggregator.
- Position
- Below the diagonal: ai.chronon.aggregator.windowing uses a module listed above it, which is the healthy direction.
17→2 ai.chronon.online.FetcherCache uses ai.chronon.online.FetcherCache.BatchIrCache✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.FetcherCache uses a type in ai.chronon.online.FetcherCache.BatchIrCache.
- The types involved
ai.chronon.online.FetcherCache.BatchIrCache→ai.chronon.online.FetcherCache.BatchIrCache.Key
- Direction
- ai.chronon.online.FetcherCache uses ai.chronon.online.FetcherCache.BatchIrCache, so a change to ai.chronon.online.FetcherCache.BatchIrCache can break ai.chronon.online.FetcherCache, while a change to ai.chronon.online.FetcherCache can't break ai.chronon.online.FetcherCache.BatchIrCache.
- Position
- Below the diagonal: ai.chronon.online.FetcherCache uses a module listed above it, which is the healthy direction.
17→3 ai.chronon.online.FetcherCache uses ai.chronon.online.KVStore✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.FetcherCache uses a type in ai.chronon.online.KVStore.
- The types involved
ai.chronon.online.FetcherCache.KvStoreBatchResponse→ai.chronon.online.KVStore.TimedValue
- Direction
- ai.chronon.online.FetcherCache uses ai.chronon.online.KVStore, so a change to ai.chronon.online.KVStore can break ai.chronon.online.FetcherCache, while a change to ai.chronon.online.FetcherCache can't break ai.chronon.online.KVStore.
- Position
- Below the diagonal: ai.chronon.online.FetcherCache uses a module listed above it, which is the healthy direction.
17→16 ai.chronon.online.FetcherCache uses ai.chronon.aggregator.windowing✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.FetcherCache uses a type in ai.chronon.aggregator.windowing.
- The types involved
ai.chronon.online.FetcherCache.CachedFinalIrBatchResponse→ai.chronon.aggregator.windowing.FinalBatchIr
- Direction
- ai.chronon.online.FetcherCache uses ai.chronon.aggregator.windowing, so a change to ai.chronon.aggregator.windowing can break ai.chronon.online.FetcherCache, while a change to ai.chronon.online.FetcherCache can't break ai.chronon.aggregator.windowing.
- Position
- Below the diagonal: ai.chronon.online.FetcherCache uses a module listed above it, which is the healthy direction.
18→5 ai.chronon.spark uses ai.chronon.api.Builders✕
- Connections
- 20 pairs of types, where a type in ai.chronon.spark uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Analyzer→ai.chronon.api.Builders.GroupByai.chronon.spark.BootstrapInfo→ai.chronon.api.Builders.Joinai.chronon.spark.ExternalPartMetadata→ai.chronon.api.Builders.ExternalPartai.chronon.spark.GroupBy→ai.chronon.api.Builders.Aggregationai.chronon.spark.JoinBase→ai.chronon.api.Builders.JoinPartai.chronon.spark.JoinPartMetadata→ai.chronon.api.Builders.JoinPartai.chronon.spark.JoinUtils→ai.chronon.api.Builders.Joinai.chronon.spark.JoinUtils→ai.chronon.api.Builders.JoinPartai.chronon.spark.JoinUtils→ai.chronon.api.Builders.Sourceai.chronon.spark.LabelJoin→ai.chronon.api.Builders.JoinPartai.chronon.spark.LogUtils→ai.chronon.api.Builders.GroupByai.chronon.spark.MetadataExporter→ai.chronon.api.Builders.GroupByai.chronon.spark.ModelTransformBatchJob→ai.chronon.api.Builders.Joinai.chronon.spark.ModelTransformBatchJob→ai.chronon.api.Builders.ModelTransformai.chronon.spark.PartitionRange→ai.chronon.api.Builders.Queryai.chronon.spark.PySparkUtils→ai.chronon.api.Builders.GroupByai.chronon.spark.PySparkUtils→ai.chronon.api.Builders.Joinai.chronon.spark.PySparkUtils→ai.chronon.api.Builders.Sourceai.chronon.spark.PySparkUtils→ai.chronon.api.Builders.StagingQueryai.chronon.spark.SemanticHashUtils→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark uses a module listed above it, which is the healthy direction.
18→6 ai.chronon.spark uses ai.chronon.api✕
- Connections
- 18 pairs of types, where a type in ai.chronon.spark uses a type in ai.chronon.api.
- The types involved
ai.chronon.spark.BaseKvRdd→ai.chronon.api.StructFieldai.chronon.spark.BaseKvRdd→ai.chronon.api.StructTypeai.chronon.spark.BootstrapInfo→ai.chronon.api.StructFieldai.chronon.spark.EncoderUtil→ai.chronon.api.Rowai.chronon.spark.EncoderUtil→ai.chronon.api.StructTypeai.chronon.spark.ExternalPartMetadata→ai.chronon.api.StructFieldai.chronon.spark.FastHashing→ai.chronon.api.Rowai.chronon.spark.FastHashing→ai.chronon.api.StructTypeai.chronon.spark.GroupBy→ai.chronon.api.StructTypeai.chronon.spark.Join→ai.chronon.api.StructFieldai.chronon.spark.Join→ai.chronon.api.StructTypeai.chronon.spark.JoinPartMetadata→ai.chronon.api.StructFieldai.chronon.spark.KvRdd→ai.chronon.api.StructTypeai.chronon.spark.LogFlattenerJob→ai.chronon.api.Rowai.chronon.spark.LogFlattenerJob→ai.chronon.api.StructFieldai.chronon.spark.LoggingSchema→ai.chronon.api.StructFieldai.chronon.spark.LoggingSchema→ai.chronon.api.StructTypeai.chronon.spark.TimedKvRdd→ai.chronon.api.StructType
- Direction
- ai.chronon.spark uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.spark uses a module listed above it, which is the healthy direction.
18→8 ai.chronon.spark uses ai.chronon.online.Metrics✕
- Connections
- 3 pairs of types, where a type in ai.chronon.spark uses a type in ai.chronon.online.Metrics.
- The types involved
ai.chronon.spark.JoinBase→ai.chronon.online.Metrics.Contextai.chronon.spark.LogFlattenerJob→ai.chronon.online.Metrics.Contextai.chronon.spark.ModelTransformBatchJob→ai.chronon.online.Metrics.Context
- Direction
- ai.chronon.spark uses ai.chronon.online.Metrics, so a change to ai.chronon.online.Metrics can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.online.Metrics.
- Position
- Below the diagonal: ai.chronon.spark uses a module listed above it, which is the healthy direction.
18→9 ai.chronon.spark uses ai.chronon.aggregator.base✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark uses a type in ai.chronon.aggregator.base.
- The types involved
ai.chronon.spark.ItemsSketchKryoSerializer→ai.chronon.aggregator.base.ItemsSketchIR
- Direction
- ai.chronon.spark uses ai.chronon.aggregator.base, so a change to ai.chronon.aggregator.base can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.aggregator.base.
- Position
- Below the diagonal: ai.chronon.spark uses a module listed above it, which is the healthy direction.
18→12 ai.chronon.spark uses ai.chronon.spark.catalog✕
- Connections
- 8 pairs of types, where a type in ai.chronon.spark uses a type in ai.chronon.spark.catalog.
- The types involved
ai.chronon.spark.Analyzer→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.GroupByUpload→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.JoinUtils→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.LogFlattenerJob→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.PartitionRange→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.PySparkUtils→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.SemanticHashUtils→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.TimeRange→ai.chronon.spark.catalog.TableUtils
- Direction
- ai.chronon.spark uses ai.chronon.spark.catalog, so a change to ai.chronon.spark.catalog can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.spark.catalog.
- Position
- Below the diagonal: ai.chronon.spark uses a module listed above it, which is the healthy direction.
18→13 ai.chronon.spark uses ai.chronon.aggregator.row✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark uses a type in ai.chronon.aggregator.row.
- The types involved
ai.chronon.spark.GroupBy→ai.chronon.aggregator.row.RowAggregator
- Direction
- ai.chronon.spark uses ai.chronon.aggregator.row, so a change to ai.chronon.aggregator.row can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.aggregator.row.
- Position
- Below the diagonal: ai.chronon.spark uses a module listed above it, which is the healthy direction.
18→14 ai.chronon.spark uses ai.chronon.spark.Extensions✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark uses a type in ai.chronon.spark.Extensions.
- The types involved
ai.chronon.spark.Join→ai.chronon.spark.Extensions.DfWithStatsai.chronon.spark.JoinBase→ai.chronon.spark.Extensions.DfWithStats
- Direction
- ai.chronon.spark uses ai.chronon.spark.Extensions, so a change to ai.chronon.spark.Extensions can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.spark.Extensions.
- Position
- Below the diagonal: ai.chronon.spark uses a module listed above it, which is the healthy direction.
18→16 ai.chronon.spark uses ai.chronon.aggregator.windowing✕
- Connections
- 3 pairs of types, where a type in ai.chronon.spark uses a type in ai.chronon.aggregator.windowing.
- The types involved
ai.chronon.spark.GroupBy→ai.chronon.aggregator.windowing.Resolutionai.chronon.spark.GroupByUpload→ai.chronon.aggregator.windowing.Resolutionai.chronon.spark.PySparkUtils→ai.chronon.aggregator.windowing.Resolution
- Direction
- ai.chronon.spark uses ai.chronon.aggregator.windowing, so a change to ai.chronon.aggregator.windowing can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.aggregator.windowing.
- Position
- Below the diagonal: ai.chronon.spark uses a module listed above it, which is the healthy direction.
18→19 ai.chronon.spark uses ai.chronon.online.serde part of a loop✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark uses a type in ai.chronon.online.serde.
- The types involved
ai.chronon.spark.LoggingSchema→ai.chronon.online.serde.AvroCodec
- Direction
- ai.chronon.spark uses ai.chronon.online.serde, so a change to ai.chronon.online.serde can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.online.serde.
- 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→22 ai.chronon.spark uses ai.chronon.online part of a loop✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark uses a type in ai.chronon.online.
- The types involved
ai.chronon.spark.Driver→ai.chronon.online.Apiai.chronon.spark.ModelTransformBatchJob→ai.chronon.online.ModelBackend
- Direction
- ai.chronon.spark uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.spark, while a change to ai.chronon.spark can't break ai.chronon.online.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→6 ai.chronon.online.serde uses ai.chronon.api✕
- Connections
- 12 pairs of types, where a type in ai.chronon.online.serde uses a type in ai.chronon.api.
- The types involved
ai.chronon.online.serde.ArrayRow→ai.chronon.api.Rowai.chronon.online.serde.AvroCodec→ai.chronon.api.DataTypeai.chronon.online.serde.AvroCodec→ai.chronon.api.Rowai.chronon.online.serde.AvroConversions→ai.chronon.api.DataTypeai.chronon.online.serde.AvroConversions→ai.chronon.api.StructTypeai.chronon.online.serde.AvroSchemaTraverser→ai.chronon.api.SchemaTraverserai.chronon.online.serde.AvroSchemaTraverser→ai.chronon.api.StructFieldai.chronon.online.serde.FeatureRecord→ai.chronon.api.StructTypeai.chronon.online.serde.RowWrapper→ai.chronon.api.Rowai.chronon.online.serde.SparkConversions→ai.chronon.api.DataTypeai.chronon.online.serde.SparkConversions→ai.chronon.api.Rowai.chronon.online.serde.SparkConversions→ai.chronon.api.StructType
- Direction
- ai.chronon.online.serde uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.online.serde, while a change to ai.chronon.online.serde can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.online.serde uses a module listed above it, which is the healthy direction.
19→18 ai.chronon.online.serde uses ai.chronon.spark✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.serde uses a type in ai.chronon.spark.
- The types involved
ai.chronon.online.serde.AvroCodec→ai.chronon.spark.Field
- Direction
- ai.chronon.online.serde uses ai.chronon.spark, so a change to ai.chronon.spark can break ai.chronon.online.serde, while a change to ai.chronon.online.serde can't break ai.chronon.spark.
- Position
- Below the diagonal: ai.chronon.online.serde uses a module listed above it, which is the healthy direction.
20→6 ai.chronon.online.Extensions uses ai.chronon.api✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.Extensions uses a type in ai.chronon.api.
- The types involved
ai.chronon.online.Extensions.StructTypeOps→ai.chronon.api.StructType
- Direction
- ai.chronon.online.Extensions uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.online.Extensions, while a change to ai.chronon.online.Extensions can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.online.Extensions uses a module listed above it, which is the healthy direction.
20→19 ai.chronon.online.Extensions uses ai.chronon.online.serde✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.Extensions uses a type in ai.chronon.online.serde.
- The types involved
ai.chronon.online.Extensions.StructTypeOps→ai.chronon.online.serde.AvroCodec
- Direction
- ai.chronon.online.Extensions uses ai.chronon.online.serde, so a change to ai.chronon.online.serde can break ai.chronon.online.Extensions, while a change to ai.chronon.online.Extensions can't break ai.chronon.online.serde.
- Position
- Below the diagonal: ai.chronon.online.Extensions uses a module listed above it, which is the healthy direction.
21→5 ai.chronon.online.Fetcher uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.Fetcher uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.online.Fetcher.ExternalToJoinRequest→ai.chronon.api.Builders.ExternalPart
- Direction
- ai.chronon.online.Fetcher uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.online.Fetcher, while a change to ai.chronon.online.Fetcher can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.online.Fetcher uses a module listed above it, which is the healthy direction.
21→6 ai.chronon.online.Fetcher uses ai.chronon.api✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.Fetcher uses a type in ai.chronon.api.
- The types involved
ai.chronon.online.Fetcher.ExternalToJoinRequest→ai.chronon.api.KeyMissingException
- Direction
- ai.chronon.online.Fetcher uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.online.Fetcher, while a change to ai.chronon.online.Fetcher can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.online.Fetcher uses a module listed above it, which is the healthy direction.
21→8 ai.chronon.online.Fetcher uses ai.chronon.online.Metrics✕
- Connections
- 3 pairs of types, where a type in ai.chronon.online.Fetcher uses a type in ai.chronon.online.Metrics.
- The types involved
ai.chronon.online.Fetcher.ExternalToJoinRequest→ai.chronon.online.Metrics.Contextai.chronon.online.Fetcher.Request→ai.chronon.online.Metrics.Contextai.chronon.online.Fetcher.ResponseWithContext→ai.chronon.online.Metrics.Context
- Direction
- ai.chronon.online.Fetcher uses ai.chronon.online.Metrics, so a change to ai.chronon.online.Metrics can break ai.chronon.online.Fetcher, while a change to ai.chronon.online.Fetcher can't break ai.chronon.online.Metrics.
- Position
- Below the diagonal: ai.chronon.online.Fetcher uses a module listed above it, which is the healthy direction.
21→19 ai.chronon.online.Fetcher uses ai.chronon.online.serde✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.Fetcher uses a type in ai.chronon.online.serde.
- The types involved
ai.chronon.online.Fetcher.StructuredResponse→ai.chronon.online.serde.FeatureRecord
- Direction
- ai.chronon.online.Fetcher uses ai.chronon.online.serde, so a change to ai.chronon.online.serde can break ai.chronon.online.Fetcher, while a change to ai.chronon.online.Fetcher can't break ai.chronon.online.serde.
- Position
- Below the diagonal: ai.chronon.online.Fetcher uses a module listed above it, which is the healthy direction.
21→22 ai.chronon.online.Fetcher uses ai.chronon.online part of a loop✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.Fetcher uses a type in ai.chronon.online.
- The types involved
ai.chronon.online.Fetcher.ResponseWithContext→ai.chronon.online.JoinCodec
- Direction
- ai.chronon.online.Fetcher uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.online.Fetcher, while a change to ai.chronon.online.Fetcher can't break ai.chronon.online.
- 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.
22→2 ai.chronon.online uses ai.chronon.online.FetcherCache.BatchIrCache✕
- Connections
- 1 pair of types, where a type in ai.chronon.online uses a type in ai.chronon.online.FetcherCache.BatchIrCache.
- The types involved
ai.chronon.online.PoolMap→ai.chronon.online.FetcherCache.BatchIrCache.Key
- Direction
- ai.chronon.online uses ai.chronon.online.FetcherCache.BatchIrCache, so a change to ai.chronon.online.FetcherCache.BatchIrCache can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.online.FetcherCache.BatchIrCache.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→3 ai.chronon.online uses ai.chronon.online.KVStore✕
- Connections
- 2 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.online.KVStore.
- The types involved
ai.chronon.online.FetcherBase→ai.chronon.online.KVStore.TimedValueai.chronon.online.FetcherCache→ai.chronon.online.KVStore.GetRequest
- Direction
- ai.chronon.online uses ai.chronon.online.KVStore, so a change to ai.chronon.online.KVStore can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.online.KVStore.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→5 ai.chronon.online uses ai.chronon.api.Builders✕
- Connections
- 13 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.online.DataStream→ai.chronon.api.Builders.Queryai.chronon.online.DerivationUtils→ai.chronon.api.Builders.Derivationai.chronon.online.DerivationUtils→ai.chronon.api.Builders.Joinai.chronon.online.ExternalSourceFactory→ai.chronon.api.Builders.ExternalSourceai.chronon.online.ExternalSourceRegistry→ai.chronon.api.Builders.ExternalPartai.chronon.online.FetcherBase→ai.chronon.api.Builders.GroupByai.chronon.online.FetcherBase→ai.chronon.api.Builders.Joinai.chronon.online.FetcherCache→ai.chronon.api.Builders.GroupByai.chronon.online.MetadataStore→ai.chronon.api.Builders.Joinai.chronon.online.ModelBackend→ai.chronon.api.Builders.Joinai.chronon.online.ModelBackend→ai.chronon.api.Builders.ModelTransformai.chronon.online.RunModelInferenceRequest→ai.chronon.api.Builders.Modelai.chronon.online.TileCodec→ai.chronon.api.Builders.GroupBy
- Direction
- ai.chronon.online uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→6 ai.chronon.online uses ai.chronon.api✕
- Connections
- 11 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.api.
- The types involved
ai.chronon.online.DataStream→ai.chronon.api.DataModelai.chronon.online.DerivationUtils→ai.chronon.api.StructFieldai.chronon.online.DerivationUtils→ai.chronon.api.StructTypeai.chronon.online.GroupByServingInfoParsed→ai.chronon.api.StructFieldai.chronon.online.GroupByServingInfoParsed→ai.chronon.api.StructTypeai.chronon.online.JoinCodec→ai.chronon.api.StructFieldai.chronon.online.JoinCodec→ai.chronon.api.StructTypeai.chronon.online.Mutation→ai.chronon.api.StructTypeai.chronon.online.SparkInternalRowConversions→ai.chronon.api.DataTypeai.chronon.online.StreamDecoder→ai.chronon.api.StructTypeai.chronon.online.ThriftDecoder→ai.chronon.api.DataType
- Direction
- ai.chronon.online uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→7 ai.chronon.online uses ai.chronon.online.FetcherModelUtils✕
- Connections
- 1 pair of types, where a type in ai.chronon.online uses a type in ai.chronon.online.FetcherModelUtils.
- The types involved
ai.chronon.online.FetcherModelUtils→ai.chronon.online.FetcherModelUtils.ModelTransformInput
- Direction
- ai.chronon.online uses ai.chronon.online.FetcherModelUtils, so a change to ai.chronon.online.FetcherModelUtils can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.online.FetcherModelUtils.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→8 ai.chronon.online uses ai.chronon.online.Metrics✕
- Connections
- 5 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.online.Metrics.
- The types involved
ai.chronon.online.ExternalSourceRegistry→ai.chronon.online.Metrics.Contextai.chronon.online.Fetcher→ai.chronon.online.Metrics.Contextai.chronon.online.FetcherBase→ai.chronon.online.Metrics.Contextai.chronon.online.FetcherCache→ai.chronon.online.Metrics.Contextai.chronon.online.LRUCache→ai.chronon.online.Metrics.Context
- Direction
- ai.chronon.online uses ai.chronon.online.Metrics, so a change to ai.chronon.online.Metrics can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.online.Metrics.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→10 ai.chronon.online uses ai.chronon.api.Extensions✕
- Connections
- 2 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.api.Extensions.
- The types involved
ai.chronon.online.JoinCodec→ai.chronon.api.Extensions.JoinOpsai.chronon.online.MetadataStore→ai.chronon.api.Extensions.JoinOps
- Direction
- ai.chronon.online uses ai.chronon.api.Extensions, so a change to ai.chronon.api.Extensions can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.api.Extensions.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→11 ai.chronon.online uses ai.chronon.online.CatalystUtil✕
- Connections
- 1 pair of types, where a type in ai.chronon.online uses a type in ai.chronon.online.CatalystUtil.
- The types involved
ai.chronon.online.CatalystUtil→ai.chronon.online.CatalystUtil.PoolKey
- Direction
- ai.chronon.online uses ai.chronon.online.CatalystUtil, so a change to ai.chronon.online.CatalystUtil can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.online.CatalystUtil.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→13 ai.chronon.online uses ai.chronon.aggregator.row✕
- Connections
- 1 pair of types, where a type in ai.chronon.online uses a type in ai.chronon.aggregator.row.
- The types involved
ai.chronon.online.TileCodec→ai.chronon.aggregator.row.RowAggregator
- Direction
- ai.chronon.online uses ai.chronon.aggregator.row, so a change to ai.chronon.aggregator.row can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.aggregator.row.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→16 ai.chronon.online uses ai.chronon.aggregator.windowing✕
- Connections
- 3 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.aggregator.windowing.
- The types involved
ai.chronon.online.FetcherBase→ai.chronon.aggregator.windowing.FinalBatchIrai.chronon.online.FetcherCache→ai.chronon.aggregator.windowing.FinalBatchIrai.chronon.online.GroupByServingInfoParsed→ai.chronon.aggregator.windowing.SawtoothOnlineAggregator
- Direction
- ai.chronon.online uses ai.chronon.aggregator.windowing, so a change to ai.chronon.aggregator.windowing can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.aggregator.windowing.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→17 ai.chronon.online uses ai.chronon.online.FetcherCache✕
- Connections
- 4 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.online.FetcherCache.
- The types involved
ai.chronon.online.FetcherBase→ai.chronon.online.FetcherCache.BatchResponsesai.chronon.online.FetcherCache→ai.chronon.online.FetcherCache.BatchIrCacheai.chronon.online.FetcherCache→ai.chronon.online.FetcherCache.BatchResponsesai.chronon.online.FetcherCache→ai.chronon.online.FetcherCache.CachedBatchResponse
- Direction
- ai.chronon.online uses ai.chronon.online.FetcherCache, so a change to ai.chronon.online.FetcherCache can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.online.FetcherCache.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→18 ai.chronon.online uses ai.chronon.spark✕
- Connections
- 1 pair of types, where a type in ai.chronon.online uses a type in ai.chronon.spark.
- The types involved
ai.chronon.online.ApiSerializationCheck→ai.chronon.spark.Field
- Direction
- ai.chronon.online uses ai.chronon.spark, so a change to ai.chronon.spark can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.spark.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→19 ai.chronon.online uses ai.chronon.online.serde✕
- Connections
- 4 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.online.serde.
- The types involved
ai.chronon.online.GroupByServingInfoParsed→ai.chronon.online.serde.AvroCodecai.chronon.online.JavaFeatureRecord→ai.chronon.online.serde.FeatureRecordai.chronon.online.JoinCodec→ai.chronon.online.serde.AvroCodecai.chronon.online.MetadataStore→ai.chronon.online.serde.AvroCodec
- Direction
- ai.chronon.online uses ai.chronon.online.serde, so a change to ai.chronon.online.serde can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.online.serde.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
22→21 ai.chronon.online uses ai.chronon.online.Fetcher✕
- Connections
- 14 pairs of types, where a type in ai.chronon.online uses a type in ai.chronon.online.Fetcher.
- The types involved
ai.chronon.online.DerivationUtils→ai.chronon.online.Fetcher.Requestai.chronon.online.ExternalSourceRegistry→ai.chronon.online.Fetcher.Requestai.chronon.online.ExternalSourceRegistry→ai.chronon.online.Fetcher.Responseai.chronon.online.Fetcher→ai.chronon.online.Fetcher.Responseai.chronon.online.FetcherBase→ai.chronon.online.Fetcher.ColumnSpecai.chronon.online.FetcherBase→ai.chronon.online.Fetcher.Requestai.chronon.online.FetcherBase→ai.chronon.online.Fetcher.Responseai.chronon.online.FetcherBase→ai.chronon.online.Fetcher.StructuredResponseai.chronon.online.FetcherModelUtils→ai.chronon.online.Fetcher.ResponseWithContextai.chronon.online.FetcherResponseWithTs→ai.chronon.online.Fetcher.Responseai.chronon.online.JavaFetcher→ai.chronon.online.Fetcher.Requestai.chronon.online.JavaFetcher→ai.chronon.online.Fetcher.Responseai.chronon.online.JavaFetcher→ai.chronon.online.Fetcher.StructuredResponseai.chronon.online.JoinCodec→ai.chronon.online.Fetcher.ResponseWithContext
- Direction
- ai.chronon.online uses ai.chronon.online.Fetcher, so a change to ai.chronon.online.Fetcher can break ai.chronon.online, while a change to ai.chronon.online can't break ai.chronon.online.Fetcher.
- Position
- Below the diagonal: ai.chronon.online uses a module listed above it, which is the healthy direction.
23→5 ai.chronon.flink.window uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.flink.window uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.flink.window.KeySelector→ai.chronon.api.Builders.GroupBy
- Direction
- ai.chronon.flink.window uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.flink.window, while a change to ai.chronon.flink.window can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.flink.window uses a module listed above it, which is the healthy direction.
23→6 ai.chronon.flink.window uses ai.chronon.api✕
- Connections
- 1 pair of types, where a type in ai.chronon.flink.window uses a type in ai.chronon.api.
- The types involved
ai.chronon.flink.window.FlinkRowAggregationFunction→ai.chronon.api.Row
- Direction
- ai.chronon.flink.window uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.flink.window, while a change to ai.chronon.flink.window can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.flink.window uses a module listed above it, which is the healthy direction.
23→8 ai.chronon.flink.window uses ai.chronon.online.Metrics✕
- Connections
- 1 pair of types, where a type in ai.chronon.flink.window uses a type in ai.chronon.online.Metrics.
- The types involved
ai.chronon.flink.window.FlinkRowAggProcessFunction→ai.chronon.online.Metrics.Context
- Direction
- ai.chronon.flink.window uses ai.chronon.online.Metrics, so a change to ai.chronon.online.Metrics can break ai.chronon.flink.window, while a change to ai.chronon.flink.window can't break ai.chronon.online.Metrics.
- Position
- Below the diagonal: ai.chronon.flink.window uses a module listed above it, which is the healthy direction.
23→13 ai.chronon.flink.window uses ai.chronon.aggregator.row✕
- Connections
- 1 pair of types, where a type in ai.chronon.flink.window uses a type in ai.chronon.aggregator.row.
- The types involved
ai.chronon.flink.window.FlinkRowAggregationFunction→ai.chronon.aggregator.row.RowAggregator
- Direction
- ai.chronon.flink.window uses ai.chronon.aggregator.row, so a change to ai.chronon.aggregator.row can break ai.chronon.flink.window, while a change to ai.chronon.flink.window can't break ai.chronon.aggregator.row.
- Position
- Below the diagonal: ai.chronon.flink.window uses a module listed above it, which is the healthy direction.
23→22 ai.chronon.flink.window uses ai.chronon.online✕
- Connections
- 1 pair of types, where a type in ai.chronon.flink.window uses a type in ai.chronon.online.
- The types involved
ai.chronon.flink.window.FlinkRowAggProcessFunction→ai.chronon.online.TileCodec
- Direction
- ai.chronon.flink.window uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.flink.window, while a change to ai.chronon.flink.window can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.flink.window uses a module listed above it, which is the healthy direction.
24→21 ai.chronon.online.ExternalSourceRegistry uses ai.chronon.online.Fetcher✕
- Connections
- 2 pairs of types, where a type in ai.chronon.online.ExternalSourceRegistry uses a type in ai.chronon.online.Fetcher.
- The types involved
ai.chronon.online.ExternalSourceRegistry.ContextualHandler→ai.chronon.online.Fetcher.Requestai.chronon.online.ExternalSourceRegistry.ContextualHandler→ai.chronon.online.Fetcher.Response
- Direction
- ai.chronon.online.ExternalSourceRegistry uses ai.chronon.online.Fetcher, so a change to ai.chronon.online.Fetcher can break ai.chronon.online.ExternalSourceRegistry, while a change to ai.chronon.online.ExternalSourceRegistry can't break ai.chronon.online.Fetcher.
- Position
- Below the diagonal: ai.chronon.online.ExternalSourceRegistry uses a module listed above it, which is the healthy direction.
24→22 ai.chronon.online.ExternalSourceRegistry uses ai.chronon.online✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.ExternalSourceRegistry uses a type in ai.chronon.online.
- The types involved
ai.chronon.online.ExternalSourceRegistry.ContextualHandler→ai.chronon.online.ExternalSourceHandler
- Direction
- ai.chronon.online.ExternalSourceRegistry uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.online.ExternalSourceRegistry, while a change to ai.chronon.online.ExternalSourceRegistry can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.online.ExternalSourceRegistry uses a module listed above it, which is the healthy direction.
25→3 ai.chronon.online.FetcherBase uses ai.chronon.online.KVStore✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.FetcherBase uses a type in ai.chronon.online.KVStore.
- The types involved
ai.chronon.online.FetcherBase.GroupByRequestMeta→ai.chronon.online.KVStore.GetRequest
- Direction
- ai.chronon.online.FetcherBase uses ai.chronon.online.KVStore, so a change to ai.chronon.online.KVStore can break ai.chronon.online.FetcherBase, while a change to ai.chronon.online.FetcherBase can't break ai.chronon.online.KVStore.
- Position
- Below the diagonal: ai.chronon.online.FetcherBase uses a module listed above it, which is the healthy direction.
25→8 ai.chronon.online.FetcherBase uses ai.chronon.online.Metrics✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.FetcherBase uses a type in ai.chronon.online.Metrics.
- The types involved
ai.chronon.online.FetcherBase.GroupByRequestMeta→ai.chronon.online.Metrics.Context
- Direction
- ai.chronon.online.FetcherBase uses ai.chronon.online.Metrics, so a change to ai.chronon.online.Metrics can break ai.chronon.online.FetcherBase, while a change to ai.chronon.online.FetcherBase can't break ai.chronon.online.Metrics.
- Position
- Below the diagonal: ai.chronon.online.FetcherBase uses a module listed above it, which is the healthy direction.
25→22 ai.chronon.online.FetcherBase uses ai.chronon.online✕
- Connections
- 1 pair of types, where a type in ai.chronon.online.FetcherBase uses a type in ai.chronon.online.
- The types involved
ai.chronon.online.FetcherBase.GroupByRequestMeta→ai.chronon.online.GroupByServingInfoParsed
- Direction
- ai.chronon.online.FetcherBase uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.online.FetcherBase, while a change to ai.chronon.online.FetcherBase can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.online.FetcherBase uses a module listed above it, which is the healthy direction.
26→3 ai.chronon.quickstart.online uses ai.chronon.online.KVStore✕
- Connections
- 3 pairs of types, where a type in ai.chronon.quickstart.online uses a type in ai.chronon.online.KVStore.
- The types involved
ai.chronon.quickstart.online.MongoKvStore→ai.chronon.online.KVStore.GetRequestai.chronon.quickstart.online.MongoKvStore→ai.chronon.online.KVStore.GetResponseai.chronon.quickstart.online.MongoKvStore→ai.chronon.online.KVStore.PutRequest
- Direction
- ai.chronon.quickstart.online uses ai.chronon.online.KVStore, so a change to ai.chronon.online.KVStore can break ai.chronon.quickstart.online, while a change to ai.chronon.quickstart.online can't break ai.chronon.online.KVStore.
- Position
- Below the diagonal: ai.chronon.quickstart.online uses a module listed above it, which is the healthy direction.
26→5 ai.chronon.quickstart.online uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.quickstart.online uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.quickstart.online.QuickstartMutationDecoder→ai.chronon.api.Builders.GroupBy
- Direction
- ai.chronon.quickstart.online uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.quickstart.online, while a change to ai.chronon.quickstart.online can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.quickstart.online uses a module listed above it, which is the healthy direction.
26→6 ai.chronon.quickstart.online uses ai.chronon.api✕
- Connections
- 4 pairs of types, where a type in ai.chronon.quickstart.online uses a type in ai.chronon.api.
- The types involved
ai.chronon.quickstart.online.CDCDecoder→ai.chronon.api.StructTypeai.chronon.quickstart.online.EventDecoder→ai.chronon.api.StructTypeai.chronon.quickstart.online.QuickstartMutationDecoder→ai.chronon.api.StructTypeai.chronon.quickstart.online.StreamingEventDecoder→ai.chronon.api.StructType
- Direction
- ai.chronon.quickstart.online uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.quickstart.online, while a change to ai.chronon.quickstart.online can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.quickstart.online uses a module listed above it, which is the healthy direction.
26→22 ai.chronon.quickstart.online uses ai.chronon.online✕
- Connections
- 12 pairs of types, where a type in ai.chronon.quickstart.online uses a type in ai.chronon.online.
- The types involved
ai.chronon.quickstart.online.CDCDecoder→ai.chronon.online.Mutationai.chronon.quickstart.online.ChrononMongoOnlineImpl→ai.chronon.online.Apiai.chronon.quickstart.online.ChrononMongoOnlineImpl→ai.chronon.online.ExternalSourceRegistryai.chronon.quickstart.online.ChrononMongoOnlineImpl→ai.chronon.online.GroupByServingInfoParsedai.chronon.quickstart.online.ChrononMongoOnlineImpl→ai.chronon.online.KVStoreai.chronon.quickstart.online.ChrononMongoOnlineImpl→ai.chronon.online.LoggableResponseai.chronon.quickstart.online.ChrononMongoOnlineImpl→ai.chronon.online.StreamDecoderai.chronon.quickstart.online.EventDecoder→ai.chronon.online.Mutationai.chronon.quickstart.online.MongoKvStore→ai.chronon.online.KVStoreai.chronon.quickstart.online.QuickstartMutationDecoder→ai.chronon.online.Mutationai.chronon.quickstart.online.QuickstartMutationDecoder→ai.chronon.online.StreamDecoderai.chronon.quickstart.online.StreamingEventDecoder→ai.chronon.online.Mutation
- Direction
- ai.chronon.quickstart.online uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.quickstart.online, while a change to ai.chronon.quickstart.online can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.quickstart.online uses a module listed above it, which is the healthy direction.
27→12 ai.chronon.spark.Driver uses ai.chronon.spark.catalog✕
- Connections
- 3 pairs of types, where a type in ai.chronon.spark.Driver uses a type in ai.chronon.spark.catalog.
- The types involved
ai.chronon.spark.Driver.LocalExportTableAbility→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.Driver.OfflineSubcommand→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.Driver.ResultValidationAbility→ai.chronon.spark.catalog.TableUtils
- Direction
- ai.chronon.spark.Driver uses ai.chronon.spark.catalog, so a change to ai.chronon.spark.catalog can break ai.chronon.spark.Driver, while a change to ai.chronon.spark.Driver can't break ai.chronon.spark.catalog.
- Position
- Below the diagonal: ai.chronon.spark.Driver uses a module listed above it, which is the healthy direction.
27→18 ai.chronon.spark.Driver uses ai.chronon.spark✕
- Connections
- 19 pairs of types, where a type in ai.chronon.spark.Driver uses a type in ai.chronon.spark.
- The types involved
ai.chronon.spark.Driver.Analyzer→ai.chronon.spark.Argsai.chronon.spark.Driver.CompareJoinQuery→ai.chronon.spark.Argsai.chronon.spark.Driver.ConsistencyMetricsCompute→ai.chronon.spark.Argsai.chronon.spark.Driver.DailyStats→ai.chronon.spark.Argsai.chronon.spark.Driver.FetcherCli→ai.chronon.spark.Argsai.chronon.spark.Driver.GroupByBackfill→ai.chronon.spark.Argsai.chronon.spark.Driver.GroupByStreaming→ai.chronon.spark.Argsai.chronon.spark.Driver.GroupByUploader→ai.chronon.spark.Argsai.chronon.spark.Driver.JoinBackfill→ai.chronon.spark.Argsai.chronon.spark.Driver.JoinBackfillFinal→ai.chronon.spark.Argsai.chronon.spark.Driver.JoinBackfillLeft→ai.chronon.spark.Argsai.chronon.spark.Driver.LabelJoin→ai.chronon.spark.Argsai.chronon.spark.Driver.LocalExportTableAbility→ai.chronon.spark.LocalTableExporterai.chronon.spark.Driver.LogFlattener→ai.chronon.spark.Argsai.chronon.spark.Driver.LogStats→ai.chronon.spark.Argsai.chronon.spark.Driver.MetadataExport→ai.chronon.spark.Argsai.chronon.spark.Driver.MetadataUploader→ai.chronon.spark.Argsai.chronon.spark.Driver.ModelTransformBatch→ai.chronon.spark.Argsai.chronon.spark.Driver.StagingQueryBackfill→ai.chronon.spark.Args
- Direction
- ai.chronon.spark.Driver uses ai.chronon.spark, so a change to ai.chronon.spark can break ai.chronon.spark.Driver, while a change to ai.chronon.spark.Driver can't break ai.chronon.spark.
- Position
- Below the diagonal: ai.chronon.spark.Driver uses a module listed above it, which is the healthy direction.
27→22 ai.chronon.spark.Driver uses ai.chronon.online✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark.Driver uses a type in ai.chronon.online.
- The types involved
ai.chronon.spark.Driver.FetcherCli→ai.chronon.online.Fetcherai.chronon.spark.Driver.OnlineSubcommand→ai.chronon.online.Api
- Direction
- ai.chronon.spark.Driver uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.spark.Driver, while a change to ai.chronon.spark.Driver can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.spark.Driver uses a module listed above it, which is the healthy direction.
28→1 ai.chronon.spark.stats uses ai.chronon.aggregator.row.StatsGenerator✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.stats uses a type in ai.chronon.aggregator.row.StatsGenerator.
- The types involved
ai.chronon.spark.stats.CompareMetrics→ai.chronon.aggregator.row.StatsGenerator.MetricTransform
- Direction
- ai.chronon.spark.stats uses ai.chronon.aggregator.row.StatsGenerator, so a change to ai.chronon.aggregator.row.StatsGenerator can break ai.chronon.spark.stats, while a change to ai.chronon.spark.stats can't break ai.chronon.aggregator.row.StatsGenerator.
- Position
- Below the diagonal: ai.chronon.spark.stats uses a module listed above it, which is the healthy direction.
28→5 ai.chronon.spark.stats uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.stats uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.stats.ConsistencyJob→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark.stats uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.stats, while a change to ai.chronon.spark.stats can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.stats uses a module listed above it, which is the healthy direction.
28→6 ai.chronon.spark.stats uses ai.chronon.api✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark.stats uses a type in ai.chronon.api.
- The types involved
ai.chronon.spark.stats.CompareBaseJob→ai.chronon.api.DataTypeai.chronon.spark.stats.CompareMetrics→ai.chronon.api.StructField
- Direction
- ai.chronon.spark.stats uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.spark.stats, while a change to ai.chronon.spark.stats can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.spark.stats uses a module listed above it, which is the healthy direction.
28→12 ai.chronon.spark.stats uses ai.chronon.spark.catalog✕
- Connections
- 3 pairs of types, where a type in ai.chronon.spark.stats uses a type in ai.chronon.spark.catalog.
- The types involved
ai.chronon.spark.stats.CompareBaseJob→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.stats.ConsistencyJob→ai.chronon.spark.catalog.TableUtilsai.chronon.spark.stats.SummaryJob→ai.chronon.spark.catalog.TableUtils
- Direction
- ai.chronon.spark.stats uses ai.chronon.spark.catalog, so a change to ai.chronon.spark.catalog can break ai.chronon.spark.stats, while a change to ai.chronon.spark.stats can't break ai.chronon.spark.catalog.
- Position
- Below the diagonal: ai.chronon.spark.stats uses a module listed above it, which is the healthy direction.
28→13 ai.chronon.spark.stats uses ai.chronon.aggregator.row✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark.stats uses a type in ai.chronon.aggregator.row.
- The types involved
ai.chronon.spark.stats.CompareMetrics→ai.chronon.aggregator.row.RowAggregatorai.chronon.spark.stats.StatsCompute→ai.chronon.aggregator.row.RowAggregator
- Direction
- ai.chronon.spark.stats uses ai.chronon.aggregator.row, so a change to ai.chronon.aggregator.row can break ai.chronon.spark.stats, while a change to ai.chronon.spark.stats can't break ai.chronon.aggregator.row.
- Position
- Below the diagonal: ai.chronon.spark.stats uses a module listed above it, which is the healthy direction.
28→18 ai.chronon.spark.stats uses ai.chronon.spark✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.stats uses a type in ai.chronon.spark.
- The types involved
ai.chronon.spark.stats.StatsCompute→ai.chronon.spark.TimedKvRdd
- Direction
- ai.chronon.spark.stats uses ai.chronon.spark, so a change to ai.chronon.spark can break ai.chronon.spark.stats, while a change to ai.chronon.spark.stats can't break ai.chronon.spark.
- Position
- Below the diagonal: ai.chronon.spark.stats uses a module listed above it, which is the healthy direction.
28→22 ai.chronon.spark.stats uses ai.chronon.online✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.stats uses a type in ai.chronon.online.
- The types involved
ai.chronon.spark.stats.ConsistencyJob→ai.chronon.online.DataMetrics
- Direction
- ai.chronon.spark.stats uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.spark.stats, while a change to ai.chronon.spark.stats can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.spark.stats uses a module listed above it, which is the healthy direction.
29→3 ai.chronon.spark.streaming.JoinSourceRunner uses ai.chronon.online.KVStore✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.streaming.JoinSourceRunner uses a type in ai.chronon.online.KVStore.
- The types involved
ai.chronon.spark.streaming.JoinSourceRunner.PutRequestHelper→ai.chronon.online.KVStore.PutRequest
- Direction
- ai.chronon.spark.streaming.JoinSourceRunner uses ai.chronon.online.KVStore, so a change to ai.chronon.online.KVStore can break ai.chronon.spark.streaming.JoinSourceRunner, while a change to ai.chronon.spark.streaming.JoinSourceRunner can't break ai.chronon.online.KVStore.
- Position
- Below the diagonal: ai.chronon.spark.streaming.JoinSourceRunner uses a module listed above it, which is the healthy direction.
29→6 ai.chronon.spark.streaming.JoinSourceRunner uses ai.chronon.api✕
- Connections
- 3 pairs of types, where a type in ai.chronon.spark.streaming.JoinSourceRunner uses a type in ai.chronon.api.
- The types involved
ai.chronon.spark.streaming.JoinSourceRunner.PutRequestHelper→ai.chronon.api.Rowai.chronon.spark.streaming.JoinSourceRunner.PutRequestHelper→ai.chronon.api.StructTypeai.chronon.spark.streaming.JoinSourceRunner.Schemas→ai.chronon.api.StructType
- Direction
- ai.chronon.spark.streaming.JoinSourceRunner uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.spark.streaming.JoinSourceRunner, while a change to ai.chronon.spark.streaming.JoinSourceRunner can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.spark.streaming.JoinSourceRunner uses a module listed above it, which is the healthy direction.
29→22 ai.chronon.spark.streaming.JoinSourceRunner uses ai.chronon.online✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.streaming.JoinSourceRunner uses a type in ai.chronon.online.
- The types involved
ai.chronon.spark.streaming.JoinSourceRunner.Schemas→ai.chronon.online.JoinCodec
- Direction
- ai.chronon.spark.streaming.JoinSourceRunner uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.spark.streaming.JoinSourceRunner, while a change to ai.chronon.spark.streaming.JoinSourceRunner can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.spark.streaming.JoinSourceRunner uses a module listed above it, which is the healthy direction.
30→3 ai.chronon.flink uses ai.chronon.online.KVStore✕
- Connections
- 4 pairs of types, where a type in ai.chronon.flink uses a type in ai.chronon.online.KVStore.
- The types involved
ai.chronon.flink.AsyncKVStoreWriter→ai.chronon.online.KVStore.PutRequestai.chronon.flink.AvroCodecFn→ai.chronon.online.KVStore.PutRequestai.chronon.flink.TiledAvroCodecFn→ai.chronon.online.KVStore.PutRequestai.chronon.flink.WriteResponse→ai.chronon.online.KVStore.PutRequest
- Direction
- ai.chronon.flink uses ai.chronon.online.KVStore, so a change to ai.chronon.online.KVStore can break ai.chronon.flink, while a change to ai.chronon.flink can't break ai.chronon.online.KVStore.
- Position
- Below the diagonal: ai.chronon.flink uses a module listed above it, which is the healthy direction.
30→5 ai.chronon.flink uses ai.chronon.api.Builders✕
- Connections
- 2 pairs of types, where a type in ai.chronon.flink uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.flink.BaseAvroCodecFn→ai.chronon.api.Builders.Queryai.chronon.flink.SparkExpressionEvalFn→ai.chronon.api.Builders.Query
- Direction
- ai.chronon.flink uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.flink, while a change to ai.chronon.flink can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.flink uses a module listed above it, which is the healthy direction.
30→6 ai.chronon.flink uses ai.chronon.api✕
- Connections
- 1 pair of types, where a type in ai.chronon.flink uses a type in ai.chronon.api.
- The types involved
ai.chronon.flink.SparkExpressionEvalFn→ai.chronon.api.StructType
- Direction
- ai.chronon.flink uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.flink, while a change to ai.chronon.flink can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.flink uses a module listed above it, which is the healthy direction.
30→9 ai.chronon.flink uses ai.chronon.aggregator.base✕
- Connections
- 1 pair of types, where a type in ai.chronon.flink uses a type in ai.chronon.aggregator.base.
- The types involved
ai.chronon.flink.SparkExpressionEvalFn→ai.chronon.aggregator.base.Histogram
- Direction
- ai.chronon.flink uses ai.chronon.aggregator.base, so a change to ai.chronon.aggregator.base can break ai.chronon.flink, while a change to ai.chronon.flink can't break ai.chronon.aggregator.base.
- Position
- Below the diagonal: ai.chronon.flink uses a module listed above it, which is the healthy direction.
30→22 ai.chronon.flink uses ai.chronon.online✕
- Connections
- 6 pairs of types, where a type in ai.chronon.flink uses a type in ai.chronon.online.
- The types involved
ai.chronon.flink.AsyncKVStoreWriter→ai.chronon.online.DataStreamai.chronon.flink.AvroCodecFn→ai.chronon.online.GroupByServingInfoParsedai.chronon.flink.BaseAvroCodecFn→ai.chronon.online.GroupByServingInfoParsedai.chronon.flink.FlinkSource→ai.chronon.online.DataStreamai.chronon.flink.SparkExpressionEvalFn→ai.chronon.online.CatalystUtilai.chronon.flink.TiledAvroCodecFn→ai.chronon.online.GroupByServingInfoParsed
- Direction
- ai.chronon.flink uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.flink, while a change to ai.chronon.flink can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.flink uses a module listed above it, which is the healthy direction.
30→23 ai.chronon.flink uses ai.chronon.flink.window✕
- Connections
- 1 pair of types, where a type in ai.chronon.flink uses a type in ai.chronon.flink.window.
- The types involved
ai.chronon.flink.TiledAvroCodecFn→ai.chronon.flink.window.TimestampedTile
- Direction
- ai.chronon.flink uses ai.chronon.flink.window, so a change to ai.chronon.flink.window can break ai.chronon.flink, while a change to ai.chronon.flink can't break ai.chronon.flink.window.
- Position
- Below the diagonal: ai.chronon.flink uses a module listed above it, which is the healthy direction.
31→5 ai.chronon.spark.Driver.CompareJoinQuery uses ai.chronon.api.Builders✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark.Driver.CompareJoinQuery uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.CompareJoinQuery.Args→ai.chronon.api.Builders.Joinai.chronon.spark.Driver.CompareJoinQuery.Args→ai.chronon.api.Builders.StagingQuery
- Direction
- ai.chronon.spark.Driver.CompareJoinQuery uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.CompareJoinQuery, while a change to ai.chronon.spark.Driver.CompareJoinQuery can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.CompareJoinQuery uses a module listed above it, which is the healthy direction.
31→27 ai.chronon.spark.Driver.CompareJoinQuery uses ai.chronon.spark.Driver✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.CompareJoinQuery uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.CompareJoinQuery.Args→ai.chronon.spark.Driver.OfflineSubcommand
- Direction
- ai.chronon.spark.Driver.CompareJoinQuery uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.CompareJoinQuery, while a change to ai.chronon.spark.Driver.CompareJoinQuery can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.CompareJoinQuery uses a module listed above it, which is the healthy direction.
32→5 ai.chronon.spark.Driver.DailyStats uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.DailyStats uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.DailyStats.Args→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark.Driver.DailyStats uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.DailyStats, while a change to ai.chronon.spark.Driver.DailyStats can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.DailyStats uses a module listed above it, which is the healthy direction.
32→27 ai.chronon.spark.Driver.DailyStats uses ai.chronon.spark.Driver✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.DailyStats uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.DailyStats.Args→ai.chronon.spark.Driver.OfflineSubcommand
- Direction
- ai.chronon.spark.Driver.DailyStats uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.DailyStats, while a change to ai.chronon.spark.Driver.DailyStats can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.DailyStats uses a module listed above it, which is the healthy direction.
33→5 ai.chronon.spark.Driver.GroupByBackfill uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.GroupByBackfill uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.GroupByBackfill.Args→ai.chronon.api.Builders.GroupBy
- Direction
- ai.chronon.spark.Driver.GroupByBackfill uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.GroupByBackfill, while a change to ai.chronon.spark.Driver.GroupByBackfill can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.GroupByBackfill uses a module listed above it, which is the healthy direction.
33→27 ai.chronon.spark.Driver.GroupByBackfill uses ai.chronon.spark.Driver✕
- Connections
- 3 pairs of types, where a type in ai.chronon.spark.Driver.GroupByBackfill uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.GroupByBackfill.Args→ai.chronon.spark.Driver.LocalExportTableAbilityai.chronon.spark.Driver.GroupByBackfill.Args→ai.chronon.spark.Driver.OfflineSubcommandai.chronon.spark.Driver.GroupByBackfill.Args→ai.chronon.spark.Driver.ResultValidationAbility
- Direction
- ai.chronon.spark.Driver.GroupByBackfill uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.GroupByBackfill, while a change to ai.chronon.spark.Driver.GroupByBackfill can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.GroupByBackfill uses a module listed above it, which is the healthy direction.
34→5 ai.chronon.spark.Driver.JoinBackfill uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.JoinBackfill uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.JoinBackfill.Args→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark.Driver.JoinBackfill uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.JoinBackfill, while a change to ai.chronon.spark.Driver.JoinBackfill can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.JoinBackfill uses a module listed above it, which is the healthy direction.
34→27 ai.chronon.spark.Driver.JoinBackfill uses ai.chronon.spark.Driver✕
- Connections
- 4 pairs of types, where a type in ai.chronon.spark.Driver.JoinBackfill uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.JoinBackfill.Args→ai.chronon.spark.Driver.JoinBackfillSubcommandai.chronon.spark.Driver.JoinBackfill.Args→ai.chronon.spark.Driver.LocalExportTableAbilityai.chronon.spark.Driver.JoinBackfill.Args→ai.chronon.spark.Driver.OfflineSubcommandai.chronon.spark.Driver.JoinBackfill.Args→ai.chronon.spark.Driver.ResultValidationAbility
- Direction
- ai.chronon.spark.Driver.JoinBackfill uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.JoinBackfill, while a change to ai.chronon.spark.Driver.JoinBackfill can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.JoinBackfill uses a module listed above it, which is the healthy direction.
35→5 ai.chronon.spark.Driver.JoinBackfillFinal uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.JoinBackfillFinal uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.JoinBackfillFinal.Args→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark.Driver.JoinBackfillFinal uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.JoinBackfillFinal, while a change to ai.chronon.spark.Driver.JoinBackfillFinal can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.JoinBackfillFinal uses a module listed above it, which is the healthy direction.
35→27 ai.chronon.spark.Driver.JoinBackfillFinal uses ai.chronon.spark.Driver✕
- Connections
- 4 pairs of types, where a type in ai.chronon.spark.Driver.JoinBackfillFinal uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.JoinBackfillFinal.Args→ai.chronon.spark.Driver.JoinBackfillSubcommandai.chronon.spark.Driver.JoinBackfillFinal.Args→ai.chronon.spark.Driver.LocalExportTableAbilityai.chronon.spark.Driver.JoinBackfillFinal.Args→ai.chronon.spark.Driver.OfflineSubcommandai.chronon.spark.Driver.JoinBackfillFinal.Args→ai.chronon.spark.Driver.ResultValidationAbility
- Direction
- ai.chronon.spark.Driver.JoinBackfillFinal uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.JoinBackfillFinal, while a change to ai.chronon.spark.Driver.JoinBackfillFinal can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.JoinBackfillFinal uses a module listed above it, which is the healthy direction.
36→5 ai.chronon.spark.Driver.JoinBackfillLeft uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.JoinBackfillLeft uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.JoinBackfillLeft.Args→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark.Driver.JoinBackfillLeft uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.JoinBackfillLeft, while a change to ai.chronon.spark.Driver.JoinBackfillLeft can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.JoinBackfillLeft uses a module listed above it, which is the healthy direction.
36→27 ai.chronon.spark.Driver.JoinBackfillLeft uses ai.chronon.spark.Driver✕
- Connections
- 4 pairs of types, where a type in ai.chronon.spark.Driver.JoinBackfillLeft uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.JoinBackfillLeft.Args→ai.chronon.spark.Driver.JoinBackfillSubcommandai.chronon.spark.Driver.JoinBackfillLeft.Args→ai.chronon.spark.Driver.LocalExportTableAbilityai.chronon.spark.Driver.JoinBackfillLeft.Args→ai.chronon.spark.Driver.OfflineSubcommandai.chronon.spark.Driver.JoinBackfillLeft.Args→ai.chronon.spark.Driver.ResultValidationAbility
- Direction
- ai.chronon.spark.Driver.JoinBackfillLeft uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.JoinBackfillLeft, while a change to ai.chronon.spark.Driver.JoinBackfillLeft can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.JoinBackfillLeft uses a module listed above it, which is the healthy direction.
37→5 ai.chronon.spark.Driver.LabelJoin uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.LabelJoin uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.LabelJoin.Args→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark.Driver.LabelJoin uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.LabelJoin, while a change to ai.chronon.spark.Driver.LabelJoin can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.LabelJoin uses a module listed above it, which is the healthy direction.
37→27 ai.chronon.spark.Driver.LabelJoin uses ai.chronon.spark.Driver✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark.Driver.LabelJoin uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.LabelJoin.Args→ai.chronon.spark.Driver.LocalExportTableAbilityai.chronon.spark.Driver.LabelJoin.Args→ai.chronon.spark.Driver.OfflineSubcommand
- Direction
- ai.chronon.spark.Driver.LabelJoin uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.LabelJoin, while a change to ai.chronon.spark.Driver.LabelJoin can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.LabelJoin uses a module listed above it, which is the healthy direction.
38→5 ai.chronon.spark.Driver.LogFlattener uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.LogFlattener uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.LogFlattener.Args→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark.Driver.LogFlattener uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.LogFlattener, while a change to ai.chronon.spark.Driver.LogFlattener can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.LogFlattener uses a module listed above it, which is the healthy direction.
38→27 ai.chronon.spark.Driver.LogFlattener uses ai.chronon.spark.Driver✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.LogFlattener uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.LogFlattener.Args→ai.chronon.spark.Driver.OfflineSubcommand
- Direction
- ai.chronon.spark.Driver.LogFlattener uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.LogFlattener, while a change to ai.chronon.spark.Driver.LogFlattener can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.LogFlattener uses a module listed above it, which is the healthy direction.
39→5 ai.chronon.spark.Driver.LogStats uses ai.chronon.api.Builders✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.LogStats uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.Driver.LogStats.Args→ai.chronon.api.Builders.Join
- Direction
- ai.chronon.spark.Driver.LogStats uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.Driver.LogStats, while a change to ai.chronon.spark.Driver.LogStats can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.Driver.LogStats uses a module listed above it, which is the healthy direction.
39→27 ai.chronon.spark.Driver.LogStats uses ai.chronon.spark.Driver✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.Driver.LogStats uses a type in ai.chronon.spark.Driver.
- The types involved
ai.chronon.spark.Driver.LogStats.Args→ai.chronon.spark.Driver.OfflineSubcommand
- Direction
- ai.chronon.spark.Driver.LogStats uses ai.chronon.spark.Driver, so a change to ai.chronon.spark.Driver can break ai.chronon.spark.Driver.LogStats, while a change to ai.chronon.spark.Driver.LogStats can't break ai.chronon.spark.Driver.
- Position
- Below the diagonal: ai.chronon.spark.Driver.LogStats uses a module listed above it, which is the healthy direction.
40→3 ai.chronon.spark.streaming uses ai.chronon.online.KVStore✕
- Connections
- 3 pairs of types, where a type in ai.chronon.spark.streaming uses a type in ai.chronon.online.KVStore.
- The types involved
ai.chronon.spark.streaming.DataWriter→ai.chronon.online.KVStore.PutRequestai.chronon.spark.streaming.GroupBy→ai.chronon.online.KVStore.PutRequestai.chronon.spark.streaming.StreamingStats→ai.chronon.online.KVStore.PutRequest
- Direction
- ai.chronon.spark.streaming uses ai.chronon.online.KVStore, so a change to ai.chronon.online.KVStore can break ai.chronon.spark.streaming, while a change to ai.chronon.spark.streaming can't break ai.chronon.online.KVStore.
- Position
- Below the diagonal: ai.chronon.spark.streaming uses a module listed above it, which is the healthy direction.
40→5 ai.chronon.spark.streaming uses ai.chronon.api.Builders✕
- Connections
- 3 pairs of types, where a type in ai.chronon.spark.streaming uses a type in ai.chronon.api.Builders.
- The types involved
ai.chronon.spark.streaming.CheckpointConfig→ai.chronon.api.Builders.GroupByai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.api.Builders.Queryai.chronon.spark.streaming.PushModeConfig→ai.chronon.api.Builders.GroupBy
- Direction
- ai.chronon.spark.streaming uses ai.chronon.api.Builders, so a change to ai.chronon.api.Builders can break ai.chronon.spark.streaming, while a change to ai.chronon.spark.streaming can't break ai.chronon.api.Builders.
- Position
- Below the diagonal: ai.chronon.spark.streaming uses a module listed above it, which is the healthy direction.
40→6 ai.chronon.spark.streaming uses ai.chronon.api✕
- Connections
- 2 pairs of types, where a type in ai.chronon.spark.streaming uses a type in ai.chronon.api.
- The types involved
ai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.api.Rowai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.api.StructType
- Direction
- ai.chronon.spark.streaming uses ai.chronon.api, so a change to ai.chronon.api can break ai.chronon.spark.streaming, while a change to ai.chronon.spark.streaming can't break ai.chronon.api.
- Position
- Below the diagonal: ai.chronon.spark.streaming uses a module listed above it, which is the healthy direction.
40→8 ai.chronon.spark.streaming uses ai.chronon.online.Metrics✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.streaming uses a type in ai.chronon.online.Metrics.
- The types involved
ai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.online.Metrics.Context
- Direction
- ai.chronon.spark.streaming uses ai.chronon.online.Metrics, so a change to ai.chronon.online.Metrics can break ai.chronon.spark.streaming, while a change to ai.chronon.spark.streaming can't break ai.chronon.online.Metrics.
- Position
- Below the diagonal: ai.chronon.spark.streaming uses a module listed above it, which is the healthy direction.
40→22 ai.chronon.spark.streaming uses ai.chronon.online✕
- Connections
- 11 pairs of types, where a type in ai.chronon.spark.streaming uses a type in ai.chronon.online.
- The types involved
ai.chronon.spark.streaming.DataWriter→ai.chronon.online.KVStoreai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.online.DataStreamai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.online.Fetcherai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.online.GroupByServingInfoParsedai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.online.StreamBuilderai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.online.TopicInfoai.chronon.spark.streaming.KafkaStreamBuilder→ai.chronon.online.DataStreamai.chronon.spark.streaming.KafkaStreamBuilder→ai.chronon.online.StreamBuilderai.chronon.spark.streaming.KafkaStreamBuilder→ai.chronon.online.TopicInfoai.chronon.spark.streaming.LocalIOCache→ai.chronon.online.Fetcherai.chronon.spark.streaming.LocalIOCache→ai.chronon.online.KVStore
- Direction
- ai.chronon.spark.streaming uses ai.chronon.online, so a change to ai.chronon.online can break ai.chronon.spark.streaming, while a change to ai.chronon.spark.streaming can't break ai.chronon.online.
- Position
- Below the diagonal: ai.chronon.spark.streaming uses a module listed above it, which is the healthy direction.
40→29 ai.chronon.spark.streaming uses ai.chronon.spark.streaming.JoinSourceRunner✕
- Connections
- 1 pair of types, where a type in ai.chronon.spark.streaming uses a type in ai.chronon.spark.streaming.JoinSourceRunner.
- The types involved
ai.chronon.spark.streaming.JoinSourceRunner→ai.chronon.spark.streaming.JoinSourceRunner.Schemas
- Direction
- ai.chronon.spark.streaming uses ai.chronon.spark.streaming.JoinSourceRunner, so a change to ai.chronon.spark.streaming.JoinSourceRunner can break ai.chronon.spark.streaming, while a change to ai.chronon.spark.streaming can't break ai.chronon.spark.streaming.JoinSourceRunner.
- Position
- Below the diagonal: ai.chronon.spark.streaming uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 30 | High / Critical |
| A05:2025 — Injection | 24 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 17 | High / Critical |
Roadmap
First, integrate automated security scanning into the CI pipeline to block regressions before they land. Second, formalize disaster recovery by codifying backups and recovery procedures in infrastructure as code. Third, enforce strict null safety in Scala to eliminate runtime errors and reduce defensive coding. Fourth, replace interpolated log messages with structured logging for better observability. Finally, add health checks to deployment configurations and ensure image tags are immutable to enable reliable rollbacks.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +6.6 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +6.6 pts | Medium | DR & Backup |
| 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. | +2.7 pts | Medium | Nullable reference types |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.3 pts | Low | ADR Quality |
| Interpolated log message defeats structured logging | +2.3 pts | Medium | Structured logging |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +2.0 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.0 pts | Medium | Release Hygiene |
| Bring the 49 bodies over 15 down to 15 or less in Cognitive Complexity — start with LineageParser.parse_join (cognitive 56), group_by.validate_group_by (cognitive 52), ColumnAggregator.construct (cognitive 49). | +1.9 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.8 | Slop | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| REDACTED | 0.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| online/src/main/scala/ai/chronon/online/Fetcher.scala | 5.7 | Mixed | Cyclomatic Complexity: Fetcher.logResponseInternal (cyclomatic 20) |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| api/py/ai/chronon/group_by.py | 6.0 | Mixed | Explicit Debt: TodoComment |
| spark/src/main/scala/ai/chronon/spark/FastHashing.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| online/src/main/scala/ai/chronon/online/FetcherBase.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| spark/src/main/scala/ai/chronon/spark/Analyzer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| api/py/ai/chronon/join.py | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 67 of 67 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 67 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, 371 of 404 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala, .py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala, .py) and this repository declares an sbt build (repository root, 97 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/REDACTED (pip/uv/Poetry), but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (project/plugins.sbt), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 2 | >>> FROM openjdk:8-jre-slim 3 | 4 | # Set this manually before building the image, requires a local build of the jar -------------------- ERROR: failed to solve: openjdk:8-jre-slim: failed to resolve source metadata for docker.io/library/openjdk:8-jre-slim: failed to do request: Head "https://registry-1.docker.io/v2/library/openjdk/manifests/8-jre-slim": Forbidden; runtime evidence skipped.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 231 further occurrence(s) are not listed individually; the score already reflects all 271.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ColumnAggregator.construct at 106. A further 6 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 Driver.main at 21 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: spark/src/main/scala/ai/chronon/spark/Driver.scala (Driver.main at 21), api/src/main/scala/ai/chronon/api/DataType.scala (DataType.fromTDataType at 18), online/src/main/scala/ai/chronon/online/serde/AvroConversions.scala (AvroConversions.toChrononSchema at 17), online/src/main/scala/ai/chronon/online/serde/SparkConversions.scala (SparkConversions.fromChrononType at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ColumnAggregator.construct (cyclomatic 106), group_by.validate_group_by (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.4 to about 7.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
49 method(s) exceeded the cognitive complexity threshold of 15; the worst was LineageParser.parse_join at 56.
What to do
- Bring the 49 bodies over 15 down to 15 or less in Cognitive Complexity — start with LineageParser.parse_join (cognitive 56), group_by.validate_group_by (cognitive 52), ColumnAggregator.construct (cognitive 49). — 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 49 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
14 god class(es) detected.
What to do
- Resolve the 11 FileTooLong finding(s) in God Classes — start with Driver.scala, REDACTED, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with JoinSourceRunner.scala, JoinBase.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with Row.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
22 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with FlinkJob.scala, CatalystUtil.scala, lineage_parser.py. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with GroupBy.scala, JoinBase.scala, Analyzer.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with FetcherBase.scala, group_by_dag_constructor.py. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
15 production modules (Python+sbt+Bazel), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence, with abstractness counted on 8 of the 15 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
6 of 55 classes have LCOM4 above 3.
What to do
- Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED (3), SimpleAggregators.scala, TimedAggregators.scala. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
547 test methods: 544 unit, 3 integration, 0 BDD, 0 e2e. The Python suite contributes 150 test function(s) across 18 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Scala suite contributes 389 test case(s) across 66 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D12 · Dependency Hygiene
17 outdated direct sbt declarations. An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 18 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 4 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 1 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares a Python pyproject.toml/REDACTED (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: spark/src/main/scala/ai/chronon/spark/FastHashing.scala (2×28=56)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with FastHashing.scala. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 129 of the 212 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
51 deducted task-comment markers across 33780 LoC (0.1/KLoC) → score 9.7. 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 51 TodoComment finding(s) in Explicit Debt — start with GroupBy.scala (4), GroupByUpload.scala (3), CompareMetrics.scala (3). — One of this dimension's main actionable groups (51 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 35 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Python, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
24 finding(s): 0 critical, 21 high, 1 medium, 2 low.
What to do
- Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (16 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D30 · Dependency Vulnerabilities
14 finding(s): 1 critical, 7 high, 6 medium, 0 low.
What to do
- Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
30 finding(s): 0 critical, 17 high, 11 medium, 2 low.
What to do
- Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (13), REDACTED (4). — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
79 of 129 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is api/py/ai/chronon/join.py. Counted over 129 of the 212 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 76 Orphaned file finding(s) in Knowledge Freshness — start with executables.py, utils.py, REDACTED. — One of this dimension's main actionable groups (76 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with SimpleAggregators.scala, ColumnAggregator.scala, join.py. — One of this dimension's main actionable groups (3 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/3 supply-chain integrity signals present (provenance, signing, SBOM).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 38 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
- `inversePrepare` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:126
- `deleteColumn` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:128
- `bulkPut` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/MongoKvStore.scala:54
- `decode` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/QuickstartMutationDecoder.scala:87
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `TimedDispatcher` has 2 unfinished members out of 4 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented. — aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:118
- `inversePrepare` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:126
- `deleteColumn` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:128
- `bulkPut` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/MongoKvStore.scala:54
- `decode` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/QuickstartMutationDecoder.scala:87
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 26/31 types (84%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 14378 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 9 use(s) across 29,360 production line(s) (~0.3/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
- `size` is read from the bytes being parsed at line 69 (`readInt`), then used to size a `new Array[Byte]` at line 70 — and nowhere in its scope is `size` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `size` against the bytes actually remaining and a maximum the format allows before allocating. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:70
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `add_join_to_flow` is public and takes `join: dict` from its caller, and it calls itself at line 110 (`self.add_join_to_flow`) with a piece of `join` — and nowhere in `add_join_to_flow` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `add_join_to_flow` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — api/py/ai/chronon/repo/join_backfill.py:110
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 81 is called with an argument built by `accumulatorIr.ir.mkString("…")` (line 83), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — flink/src/main/scala/ai/chronon/flink/window/FlinkRowAggregators.scala:81
- `debug` at line 92 is called with an argument built by `v.mkString("…")` (line 93), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — flink/src/main/scala/ai/chronon/flink/window/FlinkRowAggregators.scala:92
What to do
- In Scala, put the construction behind the logger's own check (`if (log.isDebugEnabled)`), or log through a logger that takes the message by name or by macro and so builds it only when the level is on — scala-logging's `LazyLogging`/`StrictLogging` (`logger.debug(s"rows: ${rows.mkString(", ")}")` expands to that check), log4s or log4cats. Interpolating into an `s"…"` is not the fix on SLF4J or Akka's `LoggingAdapter`: their `debug` takes a `String`, so the interpolation and every `mkString` inside it run before the call is entered.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:524, spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:536
- `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — REDACTED:1011, online/src/main/scala/ai/chronon/online/ExternalSourceRegistry.scala:167
- `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — api/py/ai/chronon/pyspark/jupyter.py:240
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error` at line 39 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — api/py/ai/chronon/repo/extract_objects.py:39
- `info` at line 292 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:292
- `info` at line 120 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — api/py/ai/chronon/lineage/lineage_parser.py:120
- `exception` at line 124 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — api/py/ai/chronon/lineage/lineage_parser.py:124
- `info` at line 128 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — api/py/ai/chronon/lineage/lineage_parser.py:128
- `info` at line 133 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — api/py/ai/chronon/lineage/lineage_parser.py:133
- `warning` at line 146 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — airflow/helpers.py:146
- `warning` at line 379 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — airflow/helpers.py:379
- `warning` at line 382 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — airflow/helpers.py:382
- `info` at line 71 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:71
- `info` at line 74 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:74
- `info` at line 77 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:77
- `info` at line 114 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:114
- `warn` at line 263 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:263
- `warn` at line 378 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:378
- `info` at line 396 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:396
- `info` at line 527 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:527
- `info` at line 533 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:533
- `info` at line 541 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:541
- `info` at line 544 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:544
- `info` at line 547 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:547
- `info` at line 549 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:549
- `info` at line 550 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:550
- `info` at line 582 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:582
- `info` at line 628 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:628
- `info` at line 668 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:668
- `info` at line 675 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:675
- `info` at line 695 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:695
- `error` at line 962 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:962
- `error` at line 963 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:963
- `error` at line 1007 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Analyzer.scala:1007
- `info` at line 85 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/BootstrapInfo.scala:85
- `info` at line 123 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/BootstrapInfo.scala:123
- `info` at line 184 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/BootstrapInfo.scala:184
- `info` at line 206 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/BootstrapInfo.scala:206
- `info` at line 316 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/BootstrapInfo.scala:316
- `info` at line 357 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/BootstrapInfo.scala:357
- `info` at line 133 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Comparison.scala:133
- `info` at line 385 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Driver.scala:385
- `info` at line 403 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — spark/src/main/scala/ai/chronon/spark/Driver.scala:403
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 134 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 | 51% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 70% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 37% | Weak — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 57% | Adequate — gated by D29, D30, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 78% | Strong | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 48 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 2 | >>> FROM openjdk:8-jre-slim 3 | 4 | # Set this manually before building the image, requires a local build of the jar -------------------- ERROR: failed to solve: openjdk:8-jre-slim: failed to resolve source metadata for docker.io/library/openjdk:8-jre-slim: failed to do request: Head "https://registry-1.docker.io/v2/library/openjdk/manifests/8-jre-slim": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~29059 lines of test source are present (.scala, .py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, Python, Scala, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .py, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 53 value object(s)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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 — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala, Java and Python were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 46 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 199 finding(s)
- TodoComment spark/src/test/scala/ai/chronon/spark/test/FetcherTest.scala:1128
- TodoComment spark/src/test/scala/ai/chronon/spark/test/OnlineUtils.scala:118
- TodoComment spark/src/test/scala/ai/chronon/spark/test/OnlineUtils.scala:143
- TodoComment spark/src/main/scala/ai/chronon/spark/Analyzer.scala:239
- TodoComment spark/src/main/scala/ai/chronon/spark/Analyzer.scala:630
- TodoComment spark/src/main/scala/ai/chronon/spark/BootstrapInfo.scala:101
- TodoComment spark/src/main/scala/ai/chronon/spark/FastHashing.scala:27
- TodoComment spark/src/main/scala/ai/chronon/spark/GroupBy.scala:408
- TodoComment spark/src/main/scala/ai/chronon/spark/GroupBy.scala:464
- TodoComment spark/src/main/scala/ai/chronon/spark/GroupBy.scala:512
- TodoComment spark/src/main/scala/ai/chronon/spark/GroupByUpload.scala:121
- TodoComment spark/src/main/scala/ai/chronon/spark/GroupByUpload.scala:138
- TodoComment spark/src/main/scala/ai/chronon/spark/GroupByUpload.scala:288
- TodoComment spark/src/main/scala/ai/chronon/spark/Join.scala:532
- TodoComment spark/src/main/scala/ai/chronon/spark/JoinBase.scala:649
- TodoComment spark/src/main/scala/ai/chronon/spark/JoinBase.scala:650
- TodoComment spark/src/main/scala/ai/chronon/spark/KvRdd.scala:119
- TodoComment spark/src/main/scala/ai/chronon/spark/SemanticHashUtils.scala:144
- TodoComment spark/src/main/scala/ai/chronon/spark/streaming/GroupBy.scala:83
- TodoComment spark/src/main/scala/ai/chronon/spark/stats/CompareMetrics.scala:159
- TodoComment spark/src/main/scala/ai/chronon/spark/stats/CompareMetrics.scala:160
- TodoComment spark/src/main/scala/ai/chronon/spark/stats/CompareMetrics.scala:185
- TodoComment REDACTED:442
- TodoComment REDACTED:675
- TodoComment REDACTED:1077
- FileTooLong: spark/Driver.scala spark/src/main/scala/ai/chronon/spark/Driver.scala
- FileTooLong: api/Extensions.scala api/src/main/scala/ai/chronon/api/Extensions.scala
- FileTooLong: REDACTED REDACTED
- FileTooLong: spark/GroupBy.scala spark/src/main/scala/ai/chronon/spark/GroupBy.scala
- FileTooLong: spark/Analyzer.scala spark/src/main/scala/ai/chronon/spark/Analyzer.scala
- FileTooLong: online/Fetcher.scala online/src/main/scala/ai/chronon/online/Fetcher.scala
- FileTooLong: base/SimpleAggregators.scala aggregator/src/main/scala/ai/chronon/aggregator/base/SimpleAggregators.scala
- FileTooLong: streaming/JoinSourceRunner.scala spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala
- FileTooLong: online/FetcherBase.scala online/src/main/scala/ai/chronon/online/FetcherBase.scala
- FileTooLong: repo/compile.py api/py/ai/chronon/repo/compile.py
- FileTooLong: REDACTED REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: SourceOps (LCOM4 8) api/src/main/scala/ai/chronon/api/Extensions.scala:312
- Low cohesion: GroupByOps (LCOM4 8) api/src/main/scala/ai/chronon/api/Extensions.scala:446
- Low cohesion: FrequentItems (LCOM4 6) aggregator/src/main/scala/ai/chronon/aggregator/base/SimpleAggregators.scala:376
- Low cohesion: DataframeOps (LCOM4 6) REDACTED:96
- Low cohesion: OrderByLimitTimed (LCOM4 4) aggregator/src/main/scala/ai/chronon/aggregator/base/TimedAggregators.scala:117
- Low cohesion: Fetcher (LCOM4 4) online/src/main/scala/ai/chronon/online/Fetcher.scala:93
- Unfinished stub — body is `???` aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:126
- Unfinished stub — body is `???` aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:128
- Unfinished stub — body is `???` quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/MongoKvStore.scala:54
- Unfinished stub — body is `???` quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/QuickstartMutationDecoder.scala:87
- Unfinished stub — body is ??? / NotImplementedError aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:126
- Unfinished stub — body is ??? / NotImplementedError aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:128
- Unfinished stub — body is ??? / NotImplementedError quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/MongoKvStore.scala:54
- Unfinished stub — body is ??? / NotImplementedError quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/QuickstartMutationDecoder.scala:87
- Duplicated block (9 lines × 2) flink/src/main/scala/ai/chronon/flink/FlinkJob.scala:91
- Duplicated block (9 lines × 2) online/src/main/scala/ai/chronon/online/CatalystUtil.scala:224
- Duplicated block (9 lines × 2) api/py/ai/chronon/lineage/lineage_parser.py:206
- Duplicated block (5 lines × 2) spark/src/main/scala/ai/chronon/spark/GroupBy.scala:821
- Duplicated block (5 lines × 2) spark/src/main/scala/ai/chronon/spark/JoinBase.scala:547
- Duplicated block (5 lines × 2) spark/src/main/scala/ai/chronon/spark/Analyzer.scala:287
- Swallowed exception (caught, then discarded) REDACTED:1011
- Swallowed exception (caught, then discarded) online/src/main/scala/ai/chronon/online/ExternalSourceRegistry.scala:167
- Swallowed exception (caught, then discarded) api/py/ai/chronon/pyspark/jupyter.py:240
- ClassTooLong: JoinSourceRunner spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:91
- ClassTooLong: JoinBase spark/src/main/scala/ai/chronon/spark/JoinBase.scala:39
- Duplicated block (10 lines × 2) online/src/main/scala/ai/chronon/online/FetcherBase.scala:151
- Duplicated block (10 lines × 2) airflow/group_by_dag_constructor.py:8
- Duplicated block (8 lines × 2) quickstart/mongo-online-impl/src/main/scala/ai/chronon/quickstart/online/QuickstartMutationDecoder.scala:47
- Duplicated block (8 lines × 2) api/py/ai/chronon/repo/compile.py:676
- Duplicated block (7 lines × 2) api/src/main/scala/ai/chronon/api/Extensions.scala:624
- Duplicated block (7 lines × 2) spark/src/main/scala/ai/chronon/spark/JoinBase.scala:540
- Swallowed exception (empty catch) spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:524
- Swallowed exception (empty catch) spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:536
- ColumnAggregator.construct (cyclomatic 106) aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:227
- group_by.validate_group_by (cyclomatic 33) api/py/ai/chronon/group_by.py:221
- FastHashing.generateKeyBuilder (cyclomatic 28) spark/src/main/scala/ai/chronon/spark/FastHashing.scala:48
- SparkInternalRowConversions.to (cyclomatic 26) online/src/main/scala/ai/chronon/online/SparkInternalRowConversions.scala:130
- Row.to (cyclomatic 25) api/src/main/scala/ai/chronon/api/Row.scala:130
- FetcherBase.fetchGroupBys (cyclomatic 24) online/src/main/scala/ai/chronon/online/FetcherBase.scala:353
- compile.extract_and_convert (cyclomatic 24) api/py/ai/chronon/repo/compile.py:90
- run.set_runtime_env (cyclomatic 24) REDACTED:239
- FetcherBase.constructGroupByResponse (cyclomatic 21) online/src/main/scala/ai/chronon/online/FetcherBase.scala:59
- Analyzer.analyzeJoin (cyclomatic 21) spark/src/main/scala/ai/chronon/spark/Analyzer.scala:343
- LineageParser.parse_join (cyclomatic 21) api/py/ai/chronon/lineage/lineage_parser.py:429
- Fetcher.logResponseInternal (cyclomatic 20) online/src/main/scala/ai/chronon/online/Fetcher.scala:498
- Runner.run (cyclomatic 19) REDACTED:411
- utils.get_modes_tables (cyclomatic 19) api/py/ai/chronon/utils.py:473
- join.Join (cyclomatic 18) api/py/ai/chronon/join.py:392
- PlatformInterface.set_metadata (cyclomatic 18) api/py/ai/chronon/pyspark/executables.py:839
- FetcherBase.fetchJoin (cyclomatic 17) online/src/main/scala/ai/chronon/online/FetcherBase.scala:611
- TwoStackLiteAggregator.slidingSawtoothWindow (cyclomatic 16) aggregator/src/main/scala/ai/chronon/aggregator/windowing/TwoStackLiteAggregator.scala:66
- Analyzer.runDataAvailabilityCheck (cyclomatic 16) spark/src/main/scala/ai/chronon/spark/Analyzer.scala:641
- JoinSourceRunner.enrichBaseJoin (cyclomatic 16) spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:494
- Hotspot: spark/src/main/scala/ai/chronon/spark/FastHashing.scala spark/src/main/scala/ai/chronon/spark/FastHashing.scala:48
- LineageParser.parse_join (cognitive 56) api/py/ai/chronon/lineage/lineage_parser.py:429
- group_by.validate_group_by (cognitive 52) api/py/ai/chronon/group_by.py:221
- ColumnAggregator.construct (cognitive 49) aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:227
- run.set_runtime_env (cognitive 48) REDACTED:239
- compile.extract_and_convert (cognitive 43) api/py/ai/chronon/repo/compile.py:90
- FetcherBase.constructGroupByResponse (cognitive 40) online/src/main/scala/ai/chronon/online/FetcherBase.scala:59
- Fetcher.logResponseInternal (cognitive 34) online/src/main/scala/ai/chronon/online/Fetcher.scala:498
- SparkInternalRowConversions.to (cognitive 34) online/src/main/scala/ai/chronon/online/SparkInternalRowConversions.scala:130
- LineageParser.parse_group_by (cognitive 34) api/py/ai/chronon/lineage/lineage_parser.py:625
- Analyzer.analyzeJoin (cognitive 33) spark/src/main/scala/ai/chronon/spark/Analyzer.scala:343
- FastHashing.generateKeyBuilder (cognitive 33) spark/src/main/scala/ai/chronon/spark/FastHashing.scala:48
- LineageParser.build_join_sql (cognitive 33) api/py/ai/chronon/lineage/lineage_parser.py:340
- Analyzer.runDataAvailabilityCheck (cognitive 32) spark/src/main/scala/ai/chronon/spark/Analyzer.scala:641
- FetcherBase.fetchGroupBys (cognitive 31) online/src/main/scala/ai/chronon/online/FetcherBase.scala:353
- helpers.walk_and_define_tasks (cognitive 30) airflow/helpers.py:315
- PlatformInterface.set_metadata (cognitive 28) api/py/ai/chronon/pyspark/executables.py:839
- utils.get_modes_tables (cognitive 28) api/py/ai/chronon/utils.py:473
- Runner.run (cognitive 27) REDACTED:411
- TwoStackLiteAggregator.slidingSawtoothWindow (cognitive 26) aggregator/src/main/scala/ai/chronon/aggregator/windowing/TwoStackLiteAggregator.scala:66
- SawtoothAggregator.cumulate (cognitive 24) aggregator/src/main/scala/ai/chronon/aggregator/windowing/SawtoothAggregator.scala:97
- EditDistance.between (cognitive 24) spark/src/main/scala/ai/chronon/spark/stats/EditDistance.scala:54
- JoinBase.computeJoinOpt (cognitive 23) spark/src/main/scala/ai/chronon/spark/JoinBase.scala:609
- JoinSourceRunner.enrichBaseJoin (cognitive 23) spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:494
- join.Join (cognitive 23) api/py/ai/chronon/join.py:392
- ChrononRepoValidator._validate_derivations (cognitive 22) api/py/ai/chronon/repo/validator.py:348
- BootstrapInfo.from (cognitive 21) spark/src/main/scala/ai/chronon/spark/BootstrapInfo.scala:78
- TableUtils.repartitionAndWriteInternal (cognitive 21) REDACTED:726
- helpers.should_schedule (cognitive 21) airflow/helpers.py:116
- helpers.task_names (cognitive 21) airflow/helpers.py:284
- helpers.dag_names (cognitive 20) airflow/helpers.py:253
- Row.from (cognitive 18) api/src/main/scala/ai/chronon/api/Row.scala:75
- FetcherCli.run (cognitive 18) spark/src/main/scala/ai/chronon/spark/Driver.scala:810
- SawtoothMutationAggregator.mergeTailHops (cognitive 17) aggregator/src/main/scala/ai/chronon/aggregator/windowing/SawtoothMutationAggregator.scala:147
- FetcherBase.fetchJoin (cognitive 17) online/src/main/scala/ai/chronon/online/FetcherBase.scala:611
- Analyzer.analyzeGroupBy (cognitive 17) spark/src/main/scala/ai/chronon/spark/Analyzer.scala:241
- GroupBy.computeBackfill (cognitive 17) spark/src/main/scala/ai/chronon/spark/GroupBy.scala:989
- Join.computeRange (cognitive 17) spark/src/main/scala/ai/chronon/spark/Join.scala:264
- PySparkExecutable._execute_underlying_join_sources (cognitive 17) api/py/ai/chronon/pyspark/executables.py:103
- explore.enrich_with_joins (cognitive 17) REDACTED:267
- DerivationUtils.applyDerivation (cognitive 16) online/src/main/scala/ai/chronon/online/DerivationUtils.scala:130
- Fetcher.fetchDerivations (cognitive 16) online/src/main/scala/ai/chronon/online/Fetcher.scala:334
- JoinSourceRunner.writeToKVStore (cognitive 16) spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:725
- TBaseDecoderFactory.build (cognitive 16) online/src/main/java/ai/chronon/online/TBaseDecoderFactory.java:57
- LineageParser.get_join_key_columns (cognitive 16) api/py/ai/chronon/lineage/lineage_parser.py:410
- explore.prettify_entry (cognitive 16) REDACTED:220
- extract_objects.import_module_set_name (cognitive 16) api/py/ai/chronon/repo/extract_objects.py:44
- Runner.__init__ (cognitive 16) REDACTED:363
- ChrononRepoValidator._validate_join (cognitive 16) api/py/ai/chronon/repo/validator.py:387
- ChrononRepoValidator._validate_group_by (cognitive 16) api/py/ai/chronon/repo/validator.py:475
- REDACTED
- MethodTooLong: Row.to api/src/main/scala/ai/chronon/api/Row.scala:130
- Duplicated block (21–23 lines × 2) spark/src/main/scala/ai/chronon/spark/streaming/GroupBy.scala:120
- Duplicated block (18 lines × 2) spark/src/main/scala/ai/chronon/spark/streaming/GroupBy.scala:180
- Duplicated block (16 lines × 2) spark/src/main/scala/ai/chronon/spark/streaming/JoinSourceRunner.scala:586
- Duplicated block (11–13 lines × 2) spark/src/main/scala/ai/chronon/spark/Driver.scala:960
- Duplicated block (6 lines × 2) online/src/main/java/ai/chronon/online/TBaseDecoderFactory.java:126
- Duplicated block (17–19 lines × 2) airflow/decorators.py:7
- Duplicated block (16–17 lines × 2) api/py/ai/chronon/pyspark/executables.py:419
- Duplicated block (12–13 lines × 3) api/py/ai/chronon/pyspark/executables.py:359
- Duplicated block (10–11 lines × 2) airflow/helpers.py:272
- Duplicated block (13 lines × 2) api/py/ai/chronon/group_by.py:197
- Off the main sequence: online
- Skeleton type — most members are unfinished aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:118
- No DR/backup evidence
- Length read from the parsed input is spent without ever being bounded spark/src/main/scala/ai/chronon/spark/Analyzer.scala:70
- Recursive walk over a caller-supplied document has no depth cap api/py/ai/chronon/repo/join_backfill.py:110
Minor — 142 finding(s)
- Orphaned file api/py/ai/chronon/pyspark/executables.py:1
- Orphaned file api/py/ai/chronon/utils.py:1
- Orphaned file REDACTED:1
- Orphaned file spark/src/main/scala/ai/chronon/spark/LabelJoin.scala:1
- Orphaned file api/py/ai/chronon/pyspark/jupyter.py:1
- Orphaned file api/src/main/scala/ai/chronon/api/Builders.scala:1
- Orphaned file REDACTED:1
- Orphaned file online/src/main/scala/ai/chronon/online/FetcherModelUtils.scala:1
- Orphaned file flink/src/main/scala/ai/chronon/flink/FlinkJob.scala:1
- Orphaned file REDACTED:1
- Orphaned file online/src/main/scala/ai/chronon/online/FetcherCache.scala:1
- Orphaned file online/src/main/scala/ai/chronon/online/serde/AvroConversions.scala:1
- Orphaned file aggregator/src/main/scala/ai/chronon/aggregator/windowing/SawtoothMutationAggregator.scala:1
- Orphaned file api/py/ai/chronon/lineage/lineage_metadata.py:1
- Orphaned file spark/src/main/scala/ai/chronon/spark/stats/CompareMetrics.scala:1
- Orphaned file online/src/main/scala/ai/chronon/online/DerivationUtils.scala:1
- Orphaned file aggregator/src/main/scala/ai/chronon/aggregator/windowing/TwoStackLiteAggregator.scala:1
- Orphaned file aggregator/src/main/scala/ai/chronon/aggregator/windowing/SawtoothAggregator.scala:1
- Orphaned file flink/src/main/scala/ai/chronon/flink/window/FlinkRowAggregators.scala:1
- Orphaned file aggregator/src/main/scala/ai/chronon/aggregator/row/StatsGenerator.scala:1
- Orphaned file spark/src/main/scala/ai/chronon/spark/SparkSessionBuilder.scala:1
- Orphaned file spark/src/main/scala/ai/chronon/spark/stats/CompareBaseJob.scala:1
- Orphaned file flink/src/main/scala/ai/chronon/flink/AvroCodecFn.scala:1
- Orphaned file spark/src/main/scala/ai/chronon/spark/SemanticHashUtils.scala:1
- Orphaned file aggregator/src/main/scala/ai/chronon/aggregator/windowing/SawtoothOnlineAggregator.scala:1
- Interpolated log message defeats structured logging api/py/ai/chronon/repo/extract_objects.py:39
- Interpolated log message defeats structured logging REDACTED:292
- Interpolated log message defeats structured logging api/py/ai/chronon/lineage/lineage_parser.py:120
- Interpolated log message defeats structured logging api/py/ai/chronon/lineage/lineage_parser.py:124
- Interpolated log message defeats structured logging api/py/ai/chronon/lineage/lineage_parser.py:128
- Interpolated log message defeats structured logging api/py/ai/chronon/lineage/lineage_parser.py:133
- Interpolated log message defeats structured logging airflow/helpers.py:146
- Interpolated log message defeats structured logging airflow/helpers.py:379
- Interpolated log message defeats structured logging airflow/helpers.py:382
- Interpolated log message defeats structured logging REDACTED:71
- Interpolated log message defeats structured logging REDACTED:74
- Interpolated log message defeats structured logging REDACTED:77
- Interpolated log message defeats structured logging REDACTED:114
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:263
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:378
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:396
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:527
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:533
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:541
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:544
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:547
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:549
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:550
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:582
- Interpolated log message defeats structured logging spark/src/main/scala/ai/chronon/spark/Analyzer.scala:628
- Most significant orphaned file aggregator/src/main/scala/ai/chronon/aggregator/base/SimpleAggregators.scala:1
- Most significant orphaned file aggregator/src/main/scala/ai/chronon/aggregator/row/ColumnAggregator.scala:1
- Most significant orphaned file api/py/ai/chronon/join.py:1
- REDACTED
- REDACTED
- Diagnostic log message is built whether or not it is wanted flink/src/main/scala/ai/chronon/flink/window/FlinkRowAggregators.scala:81
- Diagnostic log message is built whether or not it is wanted flink/src/main/scala/ai/chronon/flink/window/FlinkRowAggregators.scala:92
- Silent fallback default in catch spark/src/main/scala/ai/chronon/spark/LogFlattenerJob.scala:207
- Silent fallback default in catch api/py/ai/chronon/pyspark/jupyter.py:240
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Large public API surface
- No SAST
- No rollback/health safety
- No changelog
- Duplicated predicate spark/src/main/scala/ai/chronon/spark/streaming/GroupBy.scala:118
- Scala's null is not held to the type system everywhere
Minor — 17 finding(s)
- Outdated: ch.qos.logback:logback-classic
- Outdated: com.datadoghq:java-dogstatsd-client
- Outdated: com.github.ben-manes.caffeine:caffeine
- Outdated: com.google.code.gson:gson
- Outdated: com.typesafe:config
- Outdated: io.micrometer:micrometer-registry-statsd
- Outdated: io.netty:netty-all
- Outdated: io.vertx:vertx-config
- Outdated: io.vertx:vertx-core
- Outdated: io.vertx:vertx-micrometer-metrics
- Outdated: io.vertx:vertx-web
- Outdated: net.jodah:typetools
- Outdated: org.apache.thrift:libthrift
- Outdated: org.rogach:scallop_2.12
- Outdated: org.scala-lang.modules:scala-collection-compat_2.12
- Outdated: org.scala-lang.modules:scala-java8-compat_2.12
- Outdated: org.slf4j:slf4j-api
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e2d8c871aaff456181c7f81192c1d074/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e2d8c871aaff456181c7f81192c1d074/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 24 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-ef801a0c9fa64de099b4931b438c306b | 14 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 30 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-ef801a0c9fa64de099b4931b438c306b | 0 | artifacts/raw/osv-scanner.json |