Executive summary
YotpoLtd/metorikku is rated At risk because critical security findings are open, most of them in its servers and containers. Its score is held back in part because we found no recorded design decisions and no architecture document or diagram. It scores 56 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Maturity, at 48, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Fixing the password or key in the code comes next, worth about 6 points. Raising Maturity to 62 would lift the score to about 60.
Fourteen settings leave the servers or containers unsafe. One known security hole in a package the code depends on can be used by attackers, and one password or key in the code and one in the code's history are open to anyone who can read the repository. Replacing each exposed password or key, correcting the unsafe settings and updating the vulnerable packages would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code.
The product code is 3,901 lines, about €6,400 to rebuild.
If Maturity rose from 48 to 62, the lowest score rated Strong, the score would rise from 56 to about 60.
New since the last survey: 1 finding
- REDACTED Scanning · REDACTED
Rebuild cost: about €6,400 · Estimate
| Cost to rebuild | €2,100 to €11,000, for 35 to 112 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. 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 | Small: 3,901 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 code.steps | 2 code.steps.functions | 3 code.steps.obfuscate | 4 configuration.job.ConfigurationParser | 5 configuration.job.instrumentation | 6 configuration.job.output | 7 exceptions | 8 input | 9 metric.stepActions.dataQuality.ValidationRunner | 10 output.Writer | 11 output.catalog | 12 output.writers.cassandra.CassandraOutputWriter | 13 output.writers.elasticsearch.ElasticsearchOutputWriter | 14 configuration.job.input | 15 input.readers.cassandra | 16 input.readers.elasticsearch | 17 input.readers.file | 18 input.readers.jdbc | 19 input.readers.kafka | 20 input.readers.mongodb | 21 metric.stepActions.dataQuality.operators | 22 configuration.job | 23 metric.stepActions.dataQuality | 24 com.yotpo.metorikku | 25 instrumentation | 26 utils | 27 instrumentation.influxdb | 28 output | 29 metric | 30 output.writers.cassandra | 31 output.writers.elasticsearch | 32 output.writers.file | 33 output.writers.instrumentation | 34 output.writers.jdbc | 35 output.writers.kafka | 36 output.writers.redis | 37 output.writers.redshift | 38 output.writers.segment | 39 configuration.metric | 40 metric.stepActions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 code.steps | ||||||||||||||||||||||||||||||||||||||||
| 2 code.steps.functions | ||||||||||||||||||||||||||||||||||||||||
| 3 code.steps.obfuscate | ||||||||||||||||||||||||||||||||||||||||
| 4 configuration.job.ConfigurationParser | ||||||||||||||||||||||||||||||||||||||||
| 5 configuration.job.instrumentation | ||||||||||||||||||||||||||||||||||||||||
| 6 configuration.job.output | ||||||||||||||||||||||||||||||||||||||||
| 7 exceptions | ||||||||||||||||||||||||||||||||||||||||
| 8 input | ||||||||||||||||||||||||||||||||||||||||
| 9 metric.stepActions.dataQuality.ValidationRunner | ||||||||||||||||||||||||||||||||||||||||
| 10 output.Writer | ||||||||||||||||||||||||||||||||||||||||
| 11 output.catalog | ||||||||||||||||||||||||||||||||||||||||
| 12 output.writers.cassandra.CassandraOutputWriter | ||||||||||||||||||||||||||||||||||||||||
| 13 output.writers.elasticsearch.ElasticsearchOutputWriter | ||||||||||||||||||||||||||||||||||||||||
| 14 configuration.job.input | 7 | 7 | ||||||||||||||||||||||||||||||||||||||
| 15 input.readers.cassandra | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 input.readers.elasticsearch | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 input.readers.file | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 input.readers.jdbc | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 input.readers.kafka | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 input.readers.mongodb | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 metric.stepActions.dataQuality.operators | 5 | |||||||||||||||||||||||||||||||||||||||
| 22 configuration.job | 1 | 1 | 4 | 3 | 12 | |||||||||||||||||||||||||||||||||||
| 23 metric.stepActions.dataQuality | 5 | |||||||||||||||||||||||||||||||||||||||
| 24 com.yotpo.metorikku | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 instrumentation | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 utils | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 instrumentation.influxdb | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 28 output | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 metric | 2 | 4 | 1 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 30 output.writers.cassandra | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 output.writers.elasticsearch | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 output.writers.file | 1 | 1 | 2 | 4 | ||||||||||||||||||||||||||||||||||||
| 33 output.writers.instrumentation | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 output.writers.jdbc | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 output.writers.kafka | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 output.writers.redis | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 output.writers.redshift | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 output.writers.segment | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 configuration.metric | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 metric.stepActions | 1 | 2 |
14→8 configuration.job.input uses input✕
- Connections
- 7 pairs of types, where a type in configuration.job.input uses a type in input.
- The types involved
com.yotpo.metorikku.configuration.job.input.Cassandra→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.configuration.job.input.Elasticsearch→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.configuration.job.input.File→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.configuration.job.input.FileDateRange→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.configuration.job.input.JDBC→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.configuration.job.input.Kafka→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.configuration.job.input.MongoDB→com.yotpo.metorikku.input.Reader
- Direction
- configuration.job.input uses input, so a change to input can break configuration.job.input, while a change to configuration.job.input can't break input.
- Position
- Below the diagonal: configuration.job.input uses a module listed above it, which is the healthy direction.
14→22 configuration.job.input uses configuration.job part of a loop✕
- Connections
- 7 pairs of types, where a type in configuration.job.input uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.configuration.job.input.Cassandra→com.yotpo.metorikku.configuration.job.InputConfigcom.yotpo.metorikku.configuration.job.input.Elasticsearch→com.yotpo.metorikku.configuration.job.InputConfigcom.yotpo.metorikku.configuration.job.input.File→com.yotpo.metorikku.configuration.job.InputConfigcom.yotpo.metorikku.configuration.job.input.FileDateRange→com.yotpo.metorikku.configuration.job.InputConfigcom.yotpo.metorikku.configuration.job.input.JDBC→com.yotpo.metorikku.configuration.job.InputConfigcom.yotpo.metorikku.configuration.job.input.Kafka→com.yotpo.metorikku.configuration.job.InputConfigcom.yotpo.metorikku.configuration.job.input.MongoDB→com.yotpo.metorikku.configuration.job.InputConfig
- Direction
- configuration.job.input uses configuration.job, so a change to configuration.job can break configuration.job.input, while a change to configuration.job.input can't break configuration.job.
- 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→8 input.readers.cassandra uses input✕
- Connections
- 1 pair of types, where a type in input.readers.cassandra uses a type in input.
- The types involved
com.yotpo.metorikku.input.readers.cassandra.CassandraInput→com.yotpo.metorikku.input.Reader
- Direction
- input.readers.cassandra uses input, so a change to input can break input.readers.cassandra, while a change to input.readers.cassandra can't break input.
- Position
- Below the diagonal: input.readers.cassandra uses a module listed above it, which is the healthy direction.
16→8 input.readers.elasticsearch uses input✕
- Connections
- 1 pair of types, where a type in input.readers.elasticsearch uses a type in input.
- The types involved
com.yotpo.metorikku.input.readers.elasticsearch.ElasticsearchInput→com.yotpo.metorikku.input.Reader
- Direction
- input.readers.elasticsearch uses input, so a change to input can break input.readers.elasticsearch, while a change to input.readers.elasticsearch can't break input.
- Position
- Below the diagonal: input.readers.elasticsearch uses a module listed above it, which is the healthy direction.
17→8 input.readers.file uses input✕
- Connections
- 3 pairs of types, where a type in input.readers.file uses a type in input.
- The types involved
com.yotpo.metorikku.input.readers.file.FileInput→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.input.readers.file.FileStreamInput→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.input.readers.file.FilesInput→com.yotpo.metorikku.input.Reader
- Direction
- input.readers.file uses input, so a change to input can break input.readers.file, while a change to input.readers.file can't break input.
- Position
- Below the diagonal: input.readers.file uses a module listed above it, which is the healthy direction.
18→8 input.readers.jdbc uses input✕
- Connections
- 1 pair of types, where a type in input.readers.jdbc uses a type in input.
- The types involved
com.yotpo.metorikku.input.readers.jdbc.JDBCInput→com.yotpo.metorikku.input.Reader
- Direction
- input.readers.jdbc uses input, so a change to input can break input.readers.jdbc, while a change to input.readers.jdbc can't break input.
- Position
- Below the diagonal: input.readers.jdbc uses a module listed above it, which is the healthy direction.
19→8 input.readers.kafka uses input✕
- Connections
- 1 pair of types, where a type in input.readers.kafka uses a type in input.
- The types involved
com.yotpo.metorikku.input.readers.kafka.KafkaInput→com.yotpo.metorikku.input.Reader
- Direction
- input.readers.kafka uses input, so a change to input can break input.readers.kafka, while a change to input.readers.kafka can't break input.
- Position
- Below the diagonal: input.readers.kafka uses a module listed above it, which is the healthy direction.
20→8 input.readers.mongodb uses input✕
- Connections
- 1 pair of types, where a type in input.readers.mongodb uses a type in input.
- The types involved
com.yotpo.metorikku.input.readers.mongodb.MongoDBInput→com.yotpo.metorikku.input.Reader
- Direction
- input.readers.mongodb uses input, so a change to input can break input.readers.mongodb, while a change to input.readers.mongodb can't break input.
- Position
- Below the diagonal: input.readers.mongodb uses a module listed above it, which is the healthy direction.
21→23 metric.stepActions.dataQuality.operators uses metric.stepActions.dataQuality part of a loop✕
- Connections
- 5 pairs of types, where a type in metric.stepActions.dataQuality.operators uses a type in metric.stepActions.dataQuality.
- The types involved
com.yotpo.metorikku.metric.stepActions.dataQuality.operators.HasSize→com.yotpo.metorikku.metric.stepActions.dataQuality.Operatorcom.yotpo.metorikku.metric.stepActions.dataQuality.operators.HasUniqueness→com.yotpo.metorikku.metric.stepActions.dataQuality.Operatorcom.yotpo.metorikku.metric.stepActions.dataQuality.operators.IsComplete→com.yotpo.metorikku.metric.stepActions.dataQuality.Operatorcom.yotpo.metorikku.metric.stepActions.dataQuality.operators.IsContainedIn→com.yotpo.metorikku.metric.stepActions.dataQuality.Operatorcom.yotpo.metorikku.metric.stepActions.dataQuality.operators.IsUnique→com.yotpo.metorikku.metric.stepActions.dataQuality.Operator
- Direction
- metric.stepActions.dataQuality.operators uses metric.stepActions.dataQuality, so a change to metric.stepActions.dataQuality can break metric.stepActions.dataQuality.operators, while a change to metric.stepActions.dataQuality.operators can't break metric.stepActions.dataQuality.
- 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→4 configuration.job uses configuration.job.ConfigurationParser✕
- Connections
- 1 pair of types, where a type in configuration.job uses a type in configuration.job.ConfigurationParser.
- The types involved
com.yotpo.metorikku.configuration.job.ConfigurationParser→com.yotpo.metorikku.configuration.job.ConfigurationParser.ConfigFileName
- Direction
- configuration.job uses configuration.job.ConfigurationParser, so a change to configuration.job.ConfigurationParser can break configuration.job, while a change to configuration.job can't break configuration.job.ConfigurationParser.
- Position
- Below the diagonal: configuration.job uses a module listed above it, which is the healthy direction.
22→5 configuration.job uses configuration.job.instrumentation✕
- Connections
- 1 pair of types, where a type in configuration.job uses a type in configuration.job.instrumentation.
- The types involved
com.yotpo.metorikku.configuration.job.Instrumentation→com.yotpo.metorikku.configuration.job.instrumentation.InfluxDBConfig
- Direction
- configuration.job uses configuration.job.instrumentation, so a change to configuration.job.instrumentation can break configuration.job, while a change to configuration.job can't break configuration.job.instrumentation.
- Position
- Below the diagonal: configuration.job uses a module listed above it, which is the healthy direction.
22→6 configuration.job uses configuration.job.output✕
- Connections
- 4 pairs of types, where a type in configuration.job uses a type in configuration.job.output.
- The types involved
com.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.output.Hudicom.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.output.Rediscom.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.output.Redshiftcom.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.output.Segment
- Direction
- configuration.job uses configuration.job.output, so a change to configuration.job.output can break configuration.job, while a change to configuration.job can't break configuration.job.output.
- Position
- Below the diagonal: configuration.job uses a module listed above it, which is the healthy direction.
22→8 configuration.job uses input✕
- Connections
- 3 pairs of types, where a type in configuration.job uses a type in input.
- The types involved
com.yotpo.metorikku.configuration.job.Configuration→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.configuration.job.Input→com.yotpo.metorikku.input.Readercom.yotpo.metorikku.configuration.job.InputConfig→com.yotpo.metorikku.input.Reader
- Direction
- configuration.job uses input, so a change to input can break configuration.job, while a change to configuration.job can't break input.
- Position
- Below the diagonal: configuration.job uses a module listed above it, which is the healthy direction.
22→14 configuration.job uses configuration.job.input✕
- Connections
- 12 pairs of types, where a type in configuration.job uses a type in configuration.job.input.
- The types involved
com.yotpo.metorikku.configuration.job.Input→com.yotpo.metorikku.configuration.job.input.Cassandracom.yotpo.metorikku.configuration.job.Input→com.yotpo.metorikku.configuration.job.input.Elasticsearchcom.yotpo.metorikku.configuration.job.Input→com.yotpo.metorikku.configuration.job.input.Filecom.yotpo.metorikku.configuration.job.Input→com.yotpo.metorikku.configuration.job.input.FileDateRangecom.yotpo.metorikku.configuration.job.Input→com.yotpo.metorikku.configuration.job.input.JDBCcom.yotpo.metorikku.configuration.job.Input→com.yotpo.metorikku.configuration.job.input.Kafkacom.yotpo.metorikku.configuration.job.Input→com.yotpo.metorikku.configuration.job.input.MongoDBcom.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.input.Cassandracom.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.input.Elasticsearchcom.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.input.Filecom.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.input.JDBCcom.yotpo.metorikku.configuration.job.Output→com.yotpo.metorikku.configuration.job.input.Kafka
- Direction
- configuration.job uses configuration.job.input, so a change to configuration.job.input can break configuration.job, while a change to configuration.job can't break configuration.job.input.
- Position
- Below the diagonal: configuration.job uses a module listed above it, which is the healthy direction.
23→21 metric.stepActions.dataQuality uses metric.stepActions.dataQuality.operators✕
- Connections
- 5 pairs of types, where a type in metric.stepActions.dataQuality uses a type in metric.stepActions.dataQuality.operators.
- The types involved
com.yotpo.metorikku.metric.stepActions.dataQuality.DataQualityCheck→com.yotpo.metorikku.metric.stepActions.dataQuality.operators.HasSizecom.yotpo.metorikku.metric.stepActions.dataQuality.DataQualityCheck→com.yotpo.metorikku.metric.stepActions.dataQuality.operators.HasUniquenesscom.yotpo.metorikku.metric.stepActions.dataQuality.DataQualityCheck→com.yotpo.metorikku.metric.stepActions.dataQuality.operators.IsCompletecom.yotpo.metorikku.metric.stepActions.dataQuality.DataQualityCheck→com.yotpo.metorikku.metric.stepActions.dataQuality.operators.IsContainedIncom.yotpo.metorikku.metric.stepActions.dataQuality.DataQualityCheck→com.yotpo.metorikku.metric.stepActions.dataQuality.operators.IsUnique
- Direction
- metric.stepActions.dataQuality uses metric.stepActions.dataQuality.operators, so a change to metric.stepActions.dataQuality.operators can break metric.stepActions.dataQuality, while a change to metric.stepActions.dataQuality can't break metric.stepActions.dataQuality.operators.
- Position
- Below the diagonal: metric.stepActions.dataQuality uses a module listed above it, which is the healthy direction.
24→8 com.yotpo.metorikku uses input✕
- Connections
- 1 pair of types, where a type in com.yotpo.metorikku uses a type in input.
- The types involved
com.yotpo.metorikku.Job→com.yotpo.metorikku.input.Reader
- Direction
- com.yotpo.metorikku uses input, so a change to input can break com.yotpo.metorikku, while a change to com.yotpo.metorikku can't break input.
- Position
- Below the diagonal: com.yotpo.metorikku uses a module listed above it, which is the healthy direction.
24→22 com.yotpo.metorikku uses configuration.job✕
- Connections
- 2 pairs of types, where a type in com.yotpo.metorikku uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.Job→com.yotpo.metorikku.configuration.job.Configurationcom.yotpo.metorikku.Metorikku→com.yotpo.metorikku.configuration.job.Periodic
- Direction
- com.yotpo.metorikku uses configuration.job, so a change to configuration.job can break com.yotpo.metorikku, while a change to com.yotpo.metorikku can't break configuration.job.
- Position
- Below the diagonal: com.yotpo.metorikku uses a module listed above it, which is the healthy direction.
25→22 instrumentation uses configuration.job✕
- Connections
- 1 pair of types, where a type in instrumentation uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.instrumentation.InstrumentationProvider→com.yotpo.metorikku.configuration.job.Instrumentation
- Direction
- instrumentation uses configuration.job, so a change to configuration.job can break instrumentation, while a change to instrumentation can't break configuration.job.
- Position
- Below the diagonal: instrumentation uses a module listed above it, which is the healthy direction.
26→14 utils uses configuration.job.input✕
- Connections
- 1 pair of types, where a type in utils uses a type in configuration.job.input.
- The types involved
com.yotpo.metorikku.utils.FileUtils→com.yotpo.metorikku.configuration.job.input.File
- Direction
- utils uses configuration.job.input, so a change to configuration.job.input can break utils, while a change to utils can't break configuration.job.input.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
26→22 utils uses configuration.job✕
- Connections
- 1 pair of types, where a type in utils uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.utils.TableUtils→com.yotpo.metorikku.configuration.job.Catalog
- Direction
- utils uses configuration.job, so a change to configuration.job can break utils, while a change to utils can't break configuration.job.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
27→5 instrumentation.influxdb uses configuration.job.instrumentation✕
- Connections
- 1 pair of types, where a type in instrumentation.influxdb uses a type in configuration.job.instrumentation.
- The types involved
com.yotpo.metorikku.instrumentation.influxdb.InfluxDBInstrumentationFactory→com.yotpo.metorikku.configuration.job.instrumentation.InfluxDBConfig
- Direction
- instrumentation.influxdb uses configuration.job.instrumentation, so a change to configuration.job.instrumentation can break instrumentation.influxdb, while a change to instrumentation.influxdb can't break configuration.job.instrumentation.
- Position
- Below the diagonal: instrumentation.influxdb uses a module listed above it, which is the healthy direction.
27→25 instrumentation.influxdb uses instrumentation✕
- Connections
- 3 pairs of types, where a type in instrumentation.influxdb uses a type in instrumentation.
- The types involved
com.yotpo.metorikku.instrumentation.influxdb.InfluxDBInstrumentation→com.yotpo.metorikku.instrumentation.InstrumentationProvidercom.yotpo.metorikku.instrumentation.influxdb.InfluxDBInstrumentationFactory→com.yotpo.metorikku.instrumentation.InstrumentationFactorycom.yotpo.metorikku.instrumentation.influxdb.InfluxDBInstrumentationFactory→com.yotpo.metorikku.instrumentation.InstrumentationProvider
- Direction
- instrumentation.influxdb uses instrumentation, so a change to instrumentation can break instrumentation.influxdb, while a change to instrumentation.influxdb can't break instrumentation.
- Position
- Below the diagonal: instrumentation.influxdb uses a module listed above it, which is the healthy direction.
28→22 output uses configuration.job✕
- Connections
- 3 pairs of types, where a type in output uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.output.Writer→com.yotpo.metorikku.configuration.job.Streamingcom.yotpo.metorikku.output.WriterFactory→com.yotpo.metorikku.configuration.job.Configurationcom.yotpo.metorikku.output.WriterFactory→com.yotpo.metorikku.configuration.job.Output
- Direction
- output uses configuration.job, so a change to configuration.job can break output, while a change to output can't break configuration.job.
- Position
- Below the diagonal: output uses a module listed above it, which is the healthy direction.
28→24 output uses com.yotpo.metorikku✕
- Connections
- 1 pair of types, where a type in output uses a type in com.yotpo.metorikku.
- The types involved
com.yotpo.metorikku.output.WriterFactory→com.yotpo.metorikku.Job
- Direction
- output uses com.yotpo.metorikku, so a change to com.yotpo.metorikku can break output, while a change to output can't break com.yotpo.metorikku.
- Position
- Below the diagonal: output uses a module listed above it, which is the healthy direction.
29→14 metric uses configuration.job.input✕
- Connections
- 2 pairs of types, where a type in metric uses a type in configuration.job.input.
- The types involved
com.yotpo.metorikku.metric.Metric→com.yotpo.metorikku.configuration.job.input.Filecom.yotpo.metorikku.metric.StepFactory→com.yotpo.metorikku.configuration.job.input.File
- Direction
- metric uses configuration.job.input, so a change to configuration.job.input can break metric, while a change to metric can't break configuration.job.input.
- Position
- Below the diagonal: metric uses a module listed above it, which is the healthy direction.
29→22 metric uses configuration.job✕
- Connections
- 4 pairs of types, where a type in metric uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.metric.Metric→com.yotpo.metorikku.configuration.job.Configurationcom.yotpo.metorikku.metric.Metric→com.yotpo.metorikku.configuration.job.Outputcom.yotpo.metorikku.metric.Metric→com.yotpo.metorikku.configuration.job.Streamingcom.yotpo.metorikku.metric.StreamingWritingConfiguration→com.yotpo.metorikku.configuration.job.Output
- Direction
- metric uses configuration.job, so a change to configuration.job can break metric, while a change to metric can't break configuration.job.
- Position
- Below the diagonal: metric uses a module listed above it, which is the healthy direction.
29→23 metric uses metric.stepActions.dataQuality✕
- Connections
- 1 pair of types, where a type in metric uses a type in metric.stepActions.dataQuality.
- The types involved
com.yotpo.metorikku.metric.DeequFactory→com.yotpo.metorikku.metric.stepActions.dataQuality.DataQualityCheckList
- Direction
- metric uses metric.stepActions.dataQuality, so a change to metric.stepActions.dataQuality can break metric, while a change to metric can't break metric.stepActions.dataQuality.
- Position
- Below the diagonal: metric uses a module listed above it, which is the healthy direction.
29→24 metric uses com.yotpo.metorikku✕
- Connections
- 1 pair of types, where a type in metric uses a type in com.yotpo.metorikku.
- The types involved
com.yotpo.metorikku.metric.Metric→com.yotpo.metorikku.Job
- Direction
- metric uses com.yotpo.metorikku, so a change to com.yotpo.metorikku can break metric, while a change to metric can't break com.yotpo.metorikku.
- Position
- Below the diagonal: metric uses a module listed above it, which is the healthy direction.
29→25 metric uses instrumentation✕
- Connections
- 2 pairs of types, where a type in metric uses a type in instrumentation.
- The types involved
com.yotpo.metorikku.metric.Metric→com.yotpo.metorikku.instrumentation.InstrumentationProvidercom.yotpo.metorikku.metric.MetricReporting→com.yotpo.metorikku.instrumentation.InstrumentationProvider
- Direction
- metric uses instrumentation, so a change to instrumentation can break metric, while a change to metric can't break instrumentation.
- Position
- Below the diagonal: metric uses a module listed above it, which is the healthy direction.
29→28 metric uses output✕
- Connections
- 2 pairs of types, where a type in metric uses a type in output.
- The types involved
com.yotpo.metorikku.metric.Metric→com.yotpo.metorikku.output.Writercom.yotpo.metorikku.metric.StreamingWritingConfiguration→com.yotpo.metorikku.output.Writer
- Direction
- metric uses output, so a change to output can break metric, while a change to metric can't break output.
- Position
- Below the diagonal: metric uses a module listed above it, which is the healthy direction.
29→39 metric uses configuration.metric part of a loop✕
- Connections
- 1 pair of types, where a type in metric uses a type in configuration.metric.
- The types involved
com.yotpo.metorikku.metric.StepFactory→com.yotpo.metorikku.configuration.metric.Step
- Direction
- metric uses configuration.metric, so a change to configuration.metric can break metric, while a change to metric can't break configuration.metric.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→14 output.writers.cassandra uses configuration.job.input✕
- Connections
- 1 pair of types, where a type in output.writers.cassandra uses a type in configuration.job.input.
- The types involved
com.yotpo.metorikku.output.writers.cassandra.CassandraOutputWriter→com.yotpo.metorikku.configuration.job.input.Cassandra
- Direction
- output.writers.cassandra uses configuration.job.input, so a change to configuration.job.input can break output.writers.cassandra, while a change to output.writers.cassandra can't break configuration.job.input.
- Position
- Below the diagonal: output.writers.cassandra uses a module listed above it, which is the healthy direction.
30→28 output.writers.cassandra uses output✕
- Connections
- 1 pair of types, where a type in output.writers.cassandra uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.cassandra.CassandraOutputWriter→com.yotpo.metorikku.output.WriterSessionRegistration
- Direction
- output.writers.cassandra uses output, so a change to output can break output.writers.cassandra, while a change to output.writers.cassandra can't break output.
- Position
- Below the diagonal: output.writers.cassandra uses a module listed above it, which is the healthy direction.
31→28 output.writers.elasticsearch uses output✕
- Connections
- 1 pair of types, where a type in output.writers.elasticsearch uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.elasticsearch.ElasticsearchOutputWriter→com.yotpo.metorikku.output.Writer
- Direction
- output.writers.elasticsearch uses output, so a change to output can break output.writers.elasticsearch, while a change to output.writers.elasticsearch can't break output.
- Position
- Below the diagonal: output.writers.elasticsearch uses a module listed above it, which is the healthy direction.
32→6 output.writers.file uses configuration.job.output✕
- Connections
- 1 pair of types, where a type in output.writers.file uses a type in configuration.job.output.
- The types involved
com.yotpo.metorikku.output.writers.file.HudiOutputWriter→com.yotpo.metorikku.configuration.job.output.Hudi
- Direction
- output.writers.file uses configuration.job.output, so a change to configuration.job.output can break output.writers.file, while a change to output.writers.file can't break configuration.job.output.
- Position
- Below the diagonal: output.writers.file uses a module listed above it, which is the healthy direction.
32→14 output.writers.file uses configuration.job.input✕
- Connections
- 1 pair of types, where a type in output.writers.file uses a type in configuration.job.input.
- The types involved
com.yotpo.metorikku.output.writers.file.FileOutputWriter→com.yotpo.metorikku.configuration.job.input.File
- Direction
- output.writers.file uses configuration.job.input, so a change to configuration.job.input can break output.writers.file, while a change to output.writers.file can't break configuration.job.input.
- Position
- Below the diagonal: output.writers.file uses a module listed above it, which is the healthy direction.
32→22 output.writers.file uses configuration.job✕
- Connections
- 2 pairs of types, where a type in output.writers.file uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.output.writers.file.CSVOutputWriter→com.yotpo.metorikku.configuration.job.Streamingcom.yotpo.metorikku.output.writers.file.FileOutputWriter→com.yotpo.metorikku.configuration.job.Streaming
- Direction
- output.writers.file uses configuration.job, so a change to configuration.job can break output.writers.file, while a change to output.writers.file can't break configuration.job.
- Position
- Below the diagonal: output.writers.file uses a module listed above it, which is the healthy direction.
32→28 output.writers.file uses output✕
- Connections
- 4 pairs of types, where a type in output.writers.file uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.file.CSVOutputWriter→com.yotpo.metorikku.output.Writercom.yotpo.metorikku.output.writers.file.CatalogWriter→com.yotpo.metorikku.output.Writercom.yotpo.metorikku.output.writers.file.FileOutputWriter→com.yotpo.metorikku.output.Writercom.yotpo.metorikku.output.writers.file.HudiOutputWriter→com.yotpo.metorikku.output.Writer
- Direction
- output.writers.file uses output, so a change to output can break output.writers.file, while a change to output.writers.file can't break output.
- Position
- Below the diagonal: output.writers.file uses a module listed above it, which is the healthy direction.
33→28 output.writers.instrumentation uses output✕
- Connections
- 1 pair of types, where a type in output.writers.instrumentation uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.instrumentation.InstrumentationOutputWriter→com.yotpo.metorikku.output.Writer
- Direction
- output.writers.instrumentation uses output, so a change to output can break output.writers.instrumentation, while a change to output.writers.instrumentation can't break output.
- Position
- Below the diagonal: output.writers.instrumentation uses a module listed above it, which is the healthy direction.
34→28 output.writers.jdbc uses output✕
- Connections
- 2 pairs of types, where a type in output.writers.jdbc uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.jdbc.JDBCOutputWriter→com.yotpo.metorikku.output.Writercom.yotpo.metorikku.output.writers.jdbc.JDBCQueryWriter→com.yotpo.metorikku.output.Writer
- Direction
- output.writers.jdbc uses output, so a change to output can break output.writers.jdbc, while a change to output.writers.jdbc can't break output.
- Position
- Below the diagonal: output.writers.jdbc uses a module listed above it, which is the healthy direction.
35→14 output.writers.kafka uses configuration.job.input✕
- Connections
- 1 pair of types, where a type in output.writers.kafka uses a type in configuration.job.input.
- The types involved
com.yotpo.metorikku.output.writers.kafka.KafkaOutputWriter→com.yotpo.metorikku.configuration.job.input.Kafka
- Direction
- output.writers.kafka uses configuration.job.input, so a change to configuration.job.input can break output.writers.kafka, while a change to output.writers.kafka can't break configuration.job.input.
- Position
- Below the diagonal: output.writers.kafka uses a module listed above it, which is the healthy direction.
35→22 output.writers.kafka uses configuration.job✕
- Connections
- 1 pair of types, where a type in output.writers.kafka uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.output.writers.kafka.KafkaOutputWriter→com.yotpo.metorikku.configuration.job.Streaming
- Direction
- output.writers.kafka uses configuration.job, so a change to configuration.job can break output.writers.kafka, while a change to output.writers.kafka can't break configuration.job.
- Position
- Below the diagonal: output.writers.kafka uses a module listed above it, which is the healthy direction.
35→28 output.writers.kafka uses output✕
- Connections
- 1 pair of types, where a type in output.writers.kafka uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.kafka.KafkaOutputWriter→com.yotpo.metorikku.output.Writer
- Direction
- output.writers.kafka uses output, so a change to output can break output.writers.kafka, while a change to output.writers.kafka can't break output.
- Position
- Below the diagonal: output.writers.kafka uses a module listed above it, which is the healthy direction.
36→6 output.writers.redis uses configuration.job.output✕
- Connections
- 1 pair of types, where a type in output.writers.redis uses a type in configuration.job.output.
- The types involved
com.yotpo.metorikku.output.writers.redis.RedisOutputWriter→com.yotpo.metorikku.configuration.job.output.Redis
- Direction
- output.writers.redis uses configuration.job.output, so a change to configuration.job.output can break output.writers.redis, while a change to output.writers.redis can't break configuration.job.output.
- Position
- Below the diagonal: output.writers.redis uses a module listed above it, which is the healthy direction.
36→28 output.writers.redis uses output✕
- Connections
- 1 pair of types, where a type in output.writers.redis uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.redis.RedisOutputWriter→com.yotpo.metorikku.output.WriterSessionRegistration
- Direction
- output.writers.redis uses output, so a change to output can break output.writers.redis, while a change to output.writers.redis can't break output.
- Position
- Below the diagonal: output.writers.redis uses a module listed above it, which is the healthy direction.
37→28 output.writers.redshift uses output✕
- Connections
- 1 pair of types, where a type in output.writers.redshift uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.redshift.RedshiftOutputWriter→com.yotpo.metorikku.output.Writer
- Direction
- output.writers.redshift uses output, so a change to output can break output.writers.redshift, while a change to output.writers.redshift can't break output.
- Position
- Below the diagonal: output.writers.redshift uses a module listed above it, which is the healthy direction.
38→28 output.writers.segment uses output✕
- Connections
- 1 pair of types, where a type in output.writers.segment uses a type in output.
- The types involved
com.yotpo.metorikku.output.writers.segment.SegmentOutputWriter→com.yotpo.metorikku.output.Writer
- Direction
- output.writers.segment uses output, so a change to output can break output.writers.segment, while a change to output.writers.segment can't break output.
- Position
- Below the diagonal: output.writers.segment uses a module listed above it, which is the healthy direction.
39→14 configuration.metric uses configuration.job.input✕
- Connections
- 1 pair of types, where a type in configuration.metric uses a type in configuration.job.input.
- The types involved
com.yotpo.metorikku.configuration.metric.ConfigurationParser→com.yotpo.metorikku.configuration.job.input.File
- Direction
- configuration.metric uses configuration.job.input, so a change to configuration.job.input can break configuration.metric, while a change to configuration.metric can't break configuration.job.input.
- Position
- Below the diagonal: configuration.metric uses a module listed above it, which is the healthy direction.
39→22 configuration.metric uses configuration.job✕
- Connections
- 2 pairs of types, where a type in configuration.metric uses a type in configuration.job.
- The types involved
com.yotpo.metorikku.configuration.metric.Configuration→com.yotpo.metorikku.configuration.job.Outputcom.yotpo.metorikku.configuration.metric.ConfigurationParser→com.yotpo.metorikku.configuration.job.Configuration
- Direction
- configuration.metric uses configuration.job, so a change to configuration.job can break configuration.metric, while a change to configuration.metric can't break configuration.job.
- Position
- Below the diagonal: configuration.metric uses a module listed above it, which is the healthy direction.
39→23 configuration.metric uses metric.stepActions.dataQuality✕
- Connections
- 1 pair of types, where a type in configuration.metric uses a type in metric.stepActions.dataQuality.
- The types involved
com.yotpo.metorikku.configuration.metric.Step→com.yotpo.metorikku.metric.stepActions.dataQuality.DataQualityCheckList
- Direction
- configuration.metric uses metric.stepActions.dataQuality, so a change to metric.stepActions.dataQuality can break configuration.metric, while a change to configuration.metric can't break metric.stepActions.dataQuality.
- Position
- Below the diagonal: configuration.metric uses a module listed above it, which is the healthy direction.
39→29 configuration.metric uses metric✕
- Connections
- 1 pair of types, where a type in configuration.metric uses a type in metric.
- The types involved
com.yotpo.metorikku.configuration.metric.ConfigurationParser→com.yotpo.metorikku.metric.Metric
- Direction
- configuration.metric uses metric, so a change to metric can break configuration.metric, while a change to configuration.metric can't break metric.
- Position
- Below the diagonal: configuration.metric uses a module listed above it, which is the healthy direction.
40→23 metric.stepActions uses metric.stepActions.dataQuality✕
- Connections
- 1 pair of types, where a type in metric.stepActions uses a type in metric.stepActions.dataQuality.
- The types involved
com.yotpo.metorikku.metric.stepActions.Sql→com.yotpo.metorikku.metric.stepActions.dataQuality.DataQualityCheckList
- Direction
- metric.stepActions uses metric.stepActions.dataQuality, so a change to metric.stepActions.dataQuality can break metric.stepActions, while a change to metric.stepActions can't break metric.stepActions.dataQuality.
- Position
- Below the diagonal: metric.stepActions uses a module listed above it, which is the healthy direction.
40→29 metric.stepActions uses metric✕
- Connections
- 2 pairs of types, where a type in metric.stepActions uses a type in metric.
- The types involved
com.yotpo.metorikku.metric.stepActions.Code→com.yotpo.metorikku.metric.StepActioncom.yotpo.metorikku.metric.stepActions.Sql→com.yotpo.metorikku.metric.StepAction
- Direction
- metric.stepActions uses metric, so a change to metric can break metric.stepActions, while a change to metric.stepActions can't break metric.
- Position
- Below the diagonal: metric.stepActions uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 99 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
First, address the missing architectural decision records by documenting key design choices in the docs/adr folder to ensure traceability. Next, resolve the 21 orphaned files, prioritizing REDACTED and key source modules, and immediately remediate the leaked secret in REDACTED. Finally, integrate static analysis tools into the CI pipeline as a required gate to prevent regressions from reaching production.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +8.4 pts | Low | ADR Quality |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +6.2 pts | Low | REDACTED Scanning |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.0 pts | Medium | Architecture documentation |
| Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, Metric.scala, FileOutputWriter.scala. | +6.7 pts | Medium | Knowledge Freshness |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +2.0 pts | Medium | Security & performance tooling |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.8 pts | Medium | Nullable reference types |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +1.6 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.7 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Near-clean | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/main/scala/com/yotpo/metorikku/output/WriterFactory.scala | 7.3 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/com/yotpo/metorikku/output/writers/file/HudiOutputWriter.scala | 7.4 | Near-clean | Cyclomatic Complexity: HudiOutputWriter.write (cyclomatic 30) |
| docker/metorikku-spark35/spark35-overlay/src/main/scala/com/yotpo/metorikku/output/writers/redis/RedisOutputWriter.scala | 7.8 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| src/main/scala/com/yotpo/metorikku/test/TestUtil.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/com/yotpo/metorikku/input/readers/mongodb/MongoDBInput.scala | 8.5 | Near-clean | Cognitive Complexity: MongoDBInput.sanitizeRow (cognitive 22) |
| src/main/scala/com/yotpo/metorikku/input/readers/file/FileStreamInput.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (10–13 lines × 2) |
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. 62 of 62 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 — 62 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, 138 of 156 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) 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`) 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`) 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) and this repository declares an sbt build (repository root, 17 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.
- 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.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/main/scala/com/yotpo/metorikku/utils/FileUtils.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a REDACTED scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- 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 DockerCompose (examples/atlas/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — atlas-server Error context canceled atlas-tester Error context canceled hive Error context canceled spark-master Error context canceled hive-db Error context canceled zookeeper Error context canceled kafka Error context canceled spark-worker Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: hive-db Pulling hive Pulling atlas-server Pulling zookeeper Error Get "https://registry-1.docker.io/v2/": Forbidden hive Error Get "https://registry-1.docker.io/v2/": Forbidden kafka Error context canceled atlas-server Error context canceled hive-db Error context canceled spark-submit Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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. 'java.sql.DriverManager' is imported (src/main/scala/com/yotpo/metorikku/output/writers/jdbc/JDBCOutputWriter.scala:9), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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. 'java.sql.DriverManager' is imported (src/main/scala/com/yotpo/metorikku/output/writers/jdbc/JDBCOutputWriter.scala:9), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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. 'java.sql.DriverManager' is imported (src/main/scala/com/yotpo/metorikku/output/writers/jdbc/JDBCOutputWriter.scala:9), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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 requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HudiOutputWriter.write at 30. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being WriterFactory.get at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/main/scala/com/yotpo/metorikku/output/WriterFactory.scala (WriterFactory.get at 18). 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 15 down to 15 or less in Cyclomatic Complexity — start with HudiOutputWriter.write (cyclomatic 30), HudiOutputWriter.updateJobConfig (cyclomatic 23). — 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 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was HudiOutputWriter.write at 25.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with HudiOutputWriter.write (cognitive 25), MongoDBInput.sanitizeRow (cognitive 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.3 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
0 god class(es) detected.
D4 · Code Duplication
3 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (10–13 lines × 2) finding(s) in Code Duplication — start with FileStreamInput.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with RedisOutputWriter.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with RedisOutputWriter.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 production modules (sbt), 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; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 16 classes have LCOM4 above 3.
D9 · Test Distribution
80 test methods: 80 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 80 test case(s) across 16 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
5 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 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 5 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 1 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. 13 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is docker/metorikku-spark35/spark35-overlay/REDACTED. Counted over 18 of the 116 production source files in this repository: 92 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
3 deducted task-comment markers across 3901 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with WriterFactory.scala (2), TestUtil.scala. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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
0 of 2 build units (sbt) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. semgrep hit a parse error in 2 file(s) — `e2e/elasticsearch/mocks/movies.json`, `src/main/scala/com/yotpo/metorikku/utils/FileUtils.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
3 finding(s): 1 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
99 finding(s): 0 critical, 14 high, 76 medium, 9 low.
What to do
- Resolve the 76 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (66), REDACTED (9), REDACTED. — One of this dimension's main actionable groups (76 warning-level).
- Resolve the 14 High IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 9 Low IaC finding(s) in IaC & Container Security — start with REDACTED (9). — One of this dimension's main actionable groups (9 recommendation-level).
D34 · Knowledge Freshness
22 of 24 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/scala/com/yotpo/metorikku/output/writers/file/HudiOutputWriter.scala. Counted over 24 of the 116 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 21 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, Metric.scala, FileOutputWriter.scala. — One of this dimension's main actionable groups (21 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with HudiOutputWriter.scala. — 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).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 2 of 2 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
What to do
- Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
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.
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` builds the web-server image that serves this application, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:58
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 121 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 | 74% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 48% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 49% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72% | Adequate — gated by D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'java.sql.DriverManager' (src/main/scala/com/yotpo/metorikku/output/writers/jdbc/JDBCOutputWriter.scala:9) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'java.sql.DriverManager' (src/main/scala/com/yotpo/metorikku/output/writers/jdbc/JDBCOutputWriter.scala:9) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'java.sql.DriverManager' (src/main/scala/com/yotpo/metorikku/output/writers/jdbc/JDBCOutputWriter.scala:9) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 55 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — atlas-server Error context canceled atlas-tester Error context canceled hive Error context canceled spark-master Error context canceled hive-db Error context canceled zookeeper Error context canceled kafka Error context canceled spark-worker Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: hive-db Pulling hive Pulling atlas-server Pulling zookeeper Error Get "https://registry-1.docker.io/v2/": Forbidden hive Error Get "https://registry-1.docker.io/v2/": Forbidden kafka Error context canceled atlas-server Error context canceled hive-db Error context canceled spark-submit Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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 — ~2403 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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): 38 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`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.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Java and Scala code has 4,624 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 89 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
- TodoComment src/main/scala/com/yotpo/metorikku/test/TestUtil.scala:57
- TodoComment src/main/scala/com/yotpo/metorikku/output/WriterFactory.scala:27
- TodoComment src/main/scala/com/yotpo/metorikku/output/WriterFactory.scala:29
- REDACTED
- REDACTED
- HudiOutputWriter.write (cyclomatic 30) src/main/scala/com/yotpo/metorikku/output/writers/file/HudiOutputWriter.scala:60
- HudiOutputWriter.updateJobConfig (cyclomatic 23) src/main/scala/com/yotpo/metorikku/output/writers/file/HudiOutputWriter.scala:210
- HudiOutputWriter.write (cognitive 25) src/main/scala/com/yotpo/metorikku/output/writers/file/HudiOutputWriter.scala:60
- MongoDBInput.sanitizeRow (cognitive 22) src/main/scala/com/yotpo/metorikku/input/readers/mongodb/MongoDBInput.scala:91
- Duplicated block (10–13 lines × 2) src/main/scala/com/yotpo/metorikku/input/readers/file/FileStreamInput.scala:15
- Duplicated block (6 lines × 2) docker/metorikku-spark35/spark35-overlay/src/main/scala/com/yotpo/metorikku/output/writers/redis/RedisOutputWriter.scala:51
- Duplicated block (5 lines × 2) docker/metorikku-spark35/spark35-overlay/src/main/scala/com/yotpo/metorikku/output/writers/redis/RedisOutputWriter.scala:23
- CI pipeline targets a decommissioned service
Minor — 44 finding(s)
- Orphaned file REDACTED:1
- Orphaned file src/main/scala/com/yotpo/metorikku/metric/Metric.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/output/writers/file/FileOutputWriter.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/metric/stepActions/dataQuality/ValidationRunner.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/input/readers/mongodb/MongoDBInput.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/code/steps/SelectiveMerge.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/input/readers/file/SchemaConverter.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/output/writers/kafka/KafkaOutputWriter.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/Job.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/output/writers/segment/SegmentOutputWriter.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/output/writers/jdbc/JDBCQueryWriter.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/output/writers/elasticsearch/ElasticsearchOutputWriter.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/output/writers/instrumentation/InstrumentationOutputWriter.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/output/WriterFactory.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/output/writers/redshift/RedshiftOutputWriter.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/input/readers/kafka/KafkaInput.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/utils/FileUtils.scala:1
- Orphaned file REDACTED:1
- Orphaned file src/main/scala/com/yotpo/metorikku/configuration/job/ConfigurationParser.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/code/steps/ToAvro.scala:1
- Orphaned file src/main/scala/com/yotpo/metorikku/metric/MetricReporting.scala:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- No ADRs found
- REDACTED
- Concentrated knowledge decay
- Most significant orphaned file src/main/scala/com/yotpo/metorikku/output/writers/file/HudiOutputWriter.scala:1
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No rollback/health safety
- No release approval gate
- No changelog
- No security response headers detected REDACTED:58
- Scala's null is not held to the type system everywhere
Minor — 5 finding(s)
- Outdated: org.apache.commons:commons-text
- Outdated: org.apache.logging.log4j:log4j-api
- Outdated: org.apache.logging.log4j:log4j-core
- Outdated: org.apache.logging.log4j:log4j-slf4j-impl
- Outdated: org.influxdb:influxdb-java
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-8652b630be1043d180fa488fff91a922/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8652b630be1043d180fa488fff91a922/tree.json --exit-code 0 --source . | 1 | 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 . | 1 | 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-e4d84769aa5145228c6f3a3e30818e5f | 3 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 99 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/main/scala/com/yotpo/metorikku/utils/FileUtils.scala` — so the PII/GDPR sweep did not cover them at all. | 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-e4d84769aa5145228c6f3a3e30818e5f | 0 | artifacts/raw/osv-scanner.json |