Executive summary
mesos/chronos falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 37 out of 100 and is rated Weak, and all six of its critical findings are security problems.
Production Readiness, at 23, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Adding automated security scanning would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 50.
Three known security holes in the packages the code depends on can be used by attackers. Two weaknesses in the code could be used by an attacker, and one setting leaves the servers or containers unsafe. Updating the vulnerable packages, fixing the weaknesses the scanner points to and correcting the unsafe settings would close these risks.
The product code is 6,450 lines, about €7,100 to rebuild.
If Production Readiness rose from 23 to 70, the lowest score rated Strong, the score would rise from 37 to about 50.
New since the last survey: 4 findings
- Code Duplication · Edited copy of a member (46 corresponding lines) src/main/scala/org/apache/mesos/chronos/notification/MattermostClient.scala
- Code Duplication · Edited copy of a member (24 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (19 corresponding lines) src/main/scala/org/apache/mesos/chronos/scheduler/jobs/constraints/LikeConstraint.scala
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (10–11 lines × 2) REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €7,100 · Estimate
| Cost to rebuild | €2,300 to €12,000, for 39 to 124 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.7 at a score of 37. 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: 6,450 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 org.apache.mesos.chronos.scheduler | 2 org.apache.mesos.chronos.scheduler.jobs.MetricReporterService | 3 org.apache.mesos.chronos.scheduler.jobs.TaskManager | 4 org.apache.mesos.chronos.scheduler.jobs.constraints | 5 org.apache.mesos.chronos.scheduler.jobs.graph.Exporter | 6 org.apache.mesos.chronos.scheduler.mesos.MesosOfferReviverDelegate | 7 src.main.resources.ui | 8 src.main.resources.ui.components | 9 src.main.resources.ui.components.JobEditor | 10 src.main.resources.ui.components.JobSummaryView | 11 src.main.resources.ui.components.JsonEditor | 12 src.main.resources.ui.components.Main | 13 src.main.resources.ui.components.Root | 14 src.main.resources.ui.models | 15 src.main.resources.ui.models.JobForm | 16 src.main.resources.ui.models.JobSummaryModel | 17 src.main.resources.ui.models.JsonModel | 18 src.main.resources.ui.stores.JobSummaryStore | 19 src.main.resources.ui.stores.JsonStore | 20 org.apache.mesos.chronos.scheduler.graph | 21 org.apache.mesos.chronos.scheduler.jobs.stats | 22 org.apache.mesos.chronos.scheduler.mesos | 23 org.apache.mesos.chronos.scheduler.state | 24 org.apache.mesos.chronos.scheduler.config | 25 org.apache.mesos.chronos.scheduler.jobs | 26 org.apache.mesos.chronos.notification | 27 org.apache.mesos.chronos.scheduler.api | 28 org.apache.mesos.chronos.scheduler.jobs.graph | 29 org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework | 30 org.apache.mesos.chronos.utils |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 org.apache.mesos.chronos.scheduler | ||||||||||||||||||||||||||||||
| 2 org.apache.mesos.chronos.scheduler.jobs.MetricReporterService | ||||||||||||||||||||||||||||||
| 3 org.apache.mesos.chronos.scheduler.jobs.TaskManager | ||||||||||||||||||||||||||||||
| 4 org.apache.mesos.chronos.scheduler.jobs.constraints | ||||||||||||||||||||||||||||||
| 5 org.apache.mesos.chronos.scheduler.jobs.graph.Exporter | ||||||||||||||||||||||||||||||
| 6 org.apache.mesos.chronos.scheduler.mesos.MesosOfferReviverDelegate | ||||||||||||||||||||||||||||||
| 7 src.main.resources.ui | ||||||||||||||||||||||||||||||
| 8 src.main.resources.ui.components | ||||||||||||||||||||||||||||||
| 9 src.main.resources.ui.components.JobEditor | ||||||||||||||||||||||||||||||
| 10 src.main.resources.ui.components.JobSummaryView | ||||||||||||||||||||||||||||||
| 11 src.main.resources.ui.components.JsonEditor | ||||||||||||||||||||||||||||||
| 12 src.main.resources.ui.components.Main | ||||||||||||||||||||||||||||||
| 13 src.main.resources.ui.components.Root | ||||||||||||||||||||||||||||||
| 14 src.main.resources.ui.models | ||||||||||||||||||||||||||||||
| 15 src.main.resources.ui.models.JobForm | ||||||||||||||||||||||||||||||
| 16 src.main.resources.ui.models.JobSummaryModel | ||||||||||||||||||||||||||||||
| 17 src.main.resources.ui.models.JsonModel | ||||||||||||||||||||||||||||||
| 18 src.main.resources.ui.stores.JobSummaryStore | ||||||||||||||||||||||||||||||
| 19 src.main.resources.ui.stores.JsonStore | ||||||||||||||||||||||||||||||
| 20 org.apache.mesos.chronos.scheduler.graph | 2 | |||||||||||||||||||||||||||||
| 21 org.apache.mesos.chronos.scheduler.jobs.stats | 2 | |||||||||||||||||||||||||||||
| 22 org.apache.mesos.chronos.scheduler.mesos | 1 | 4 | 3 | |||||||||||||||||||||||||||
| 23 org.apache.mesos.chronos.scheduler.state | 1 | 2 | ||||||||||||||||||||||||||||
| 24 org.apache.mesos.chronos.scheduler.config | 1 | 1 | 2 | 2 | 4 | |||||||||||||||||||||||||
| 25 org.apache.mesos.chronos.scheduler.jobs | 3 | 2 | 3 | 3 | 1 | |||||||||||||||||||||||||
| 26 org.apache.mesos.chronos.notification | 7 | |||||||||||||||||||||||||||||
| 27 org.apache.mesos.chronos.scheduler.api | 6 | 2 | 1 | 6 | 15 | |||||||||||||||||||||||||
| 28 org.apache.mesos.chronos.scheduler.jobs.graph | 1 | 1 | 1 | |||||||||||||||||||||||||||
| 29 org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework | 1 | |||||||||||||||||||||||||||||
| 30 org.apache.mesos.chronos.utils | 1 | 1 |
20→25 org.apache.mesos.chronos.scheduler.graph uses org.apache.mesos.chronos.scheduler.jobs part of a loop✕
- Connections
- 2 pairs of types, where a type in org.apache.mesos.chronos.scheduler.graph uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.scheduler.graph.JobGraph→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.scheduler.graph.JobGraph→org.apache.mesos.chronos.scheduler.jobs.DependencyBasedJob
- Direction
- org.apache.mesos.chronos.scheduler.graph uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.scheduler.graph, while a change to org.apache.mesos.chronos.scheduler.graph can't break org.apache.mesos.chronos.scheduler.jobs.
- 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.
21→25 org.apache.mesos.chronos.scheduler.jobs.stats uses org.apache.mesos.chronos.scheduler.jobs part of a loop✕
- Connections
- 2 pairs of types, where a type in org.apache.mesos.chronos.scheduler.jobs.stats uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.stats.JobStats→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.scheduler.jobs.stats.JobStats→org.apache.mesos.chronos.scheduler.jobs.TaskStat
- Direction
- org.apache.mesos.chronos.scheduler.jobs.stats uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.scheduler.jobs.stats, while a change to org.apache.mesos.chronos.scheduler.jobs.stats can't break org.apache.mesos.chronos.scheduler.jobs.
- 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 org.apache.mesos.chronos.scheduler.mesos uses org.apache.mesos.chronos.scheduler.jobs.constraints✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.mesos uses a type in org.apache.mesos.chronos.scheduler.jobs.constraints.
- The types involved
org.apache.mesos.chronos.scheduler.mesos.ConstraintChecker→org.apache.mesos.chronos.scheduler.jobs.constraints.Constraint
- Direction
- org.apache.mesos.chronos.scheduler.mesos uses org.apache.mesos.chronos.scheduler.jobs.constraints, so a change to org.apache.mesos.chronos.scheduler.jobs.constraints can break org.apache.mesos.chronos.scheduler.mesos, while a change to org.apache.mesos.chronos.scheduler.mesos can't break org.apache.mesos.chronos.scheduler.jobs.constraints.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.mesos uses a module listed above it, which is the healthy direction.
22→24 org.apache.mesos.chronos.scheduler.mesos uses org.apache.mesos.chronos.scheduler.config part of a loop✕
- Connections
- 4 pairs of types, where a type in org.apache.mesos.chronos.scheduler.mesos uses a type in org.apache.mesos.chronos.scheduler.config.
- The types involved
org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework→org.apache.mesos.chronos.scheduler.config.SchedulerConfigurationorg.apache.mesos.chronos.scheduler.mesos.MesosOfferReviverActor→org.apache.mesos.chronos.scheduler.config.SchedulerConfigurationorg.apache.mesos.chronos.scheduler.mesos.MesosTaskBuilder→org.apache.mesos.chronos.scheduler.config.SchedulerConfigurationorg.apache.mesos.chronos.scheduler.mesos.SchedulerDriverBuilder→org.apache.mesos.chronos.scheduler.config.SchedulerConfiguration
- Direction
- org.apache.mesos.chronos.scheduler.mesos uses org.apache.mesos.chronos.scheduler.config, so a change to org.apache.mesos.chronos.scheduler.config can break org.apache.mesos.chronos.scheduler.mesos, while a change to org.apache.mesos.chronos.scheduler.mesos can't break org.apache.mesos.chronos.scheduler.config.
- 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→25 org.apache.mesos.chronos.scheduler.mesos uses org.apache.mesos.chronos.scheduler.jobs part of a loop✕
- Connections
- 3 pairs of types, where a type in org.apache.mesos.chronos.scheduler.mesos uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.mesos.MesosJobFramework→org.apache.mesos.chronos.scheduler.jobs.TaskManagerorg.apache.mesos.chronos.scheduler.mesos.MesosTaskBuilder→org.apache.mesos.chronos.scheduler.jobs.BaseJob
- Direction
- org.apache.mesos.chronos.scheduler.mesos uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.scheduler.mesos, while a change to org.apache.mesos.chronos.scheduler.mesos can't break org.apache.mesos.chronos.scheduler.jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→24 org.apache.mesos.chronos.scheduler.state uses org.apache.mesos.chronos.scheduler.config part of a loop✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.state uses a type in org.apache.mesos.chronos.scheduler.config.
- The types involved
org.apache.mesos.chronos.scheduler.state.MesosStatePersistenceStore→org.apache.mesos.chronos.scheduler.config.SchedulerConfiguration
- Direction
- org.apache.mesos.chronos.scheduler.state uses org.apache.mesos.chronos.scheduler.config, so a change to org.apache.mesos.chronos.scheduler.config can break org.apache.mesos.chronos.scheduler.state, while a change to org.apache.mesos.chronos.scheduler.state can't break org.apache.mesos.chronos.scheduler.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→25 org.apache.mesos.chronos.scheduler.state uses org.apache.mesos.chronos.scheduler.jobs part of a loop✕
- Connections
- 2 pairs of types, where a type in org.apache.mesos.chronos.scheduler.state uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.scheduler.state.MesosStatePersistenceStore→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.scheduler.state.PersistenceStore→org.apache.mesos.chronos.scheduler.jobs.BaseJob
- Direction
- org.apache.mesos.chronos.scheduler.state uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.scheduler.state, while a change to org.apache.mesos.chronos.scheduler.state can't break org.apache.mesos.chronos.scheduler.jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→20 org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.graph✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.config uses a type in org.apache.mesos.chronos.scheduler.graph.
- The types involved
org.apache.mesos.chronos.scheduler.config.MainModule→org.apache.mesos.chronos.scheduler.graph.JobGraph
- Direction
- org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.graph, so a change to org.apache.mesos.chronos.scheduler.graph can break org.apache.mesos.chronos.scheduler.config, while a change to org.apache.mesos.chronos.scheduler.config can't break org.apache.mesos.chronos.scheduler.graph.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.config uses a module listed above it, which is the healthy direction.
24→21 org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.jobs.stats✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.config uses a type in org.apache.mesos.chronos.scheduler.jobs.stats.
- The types involved
org.apache.mesos.chronos.scheduler.config.MainModule→org.apache.mesos.chronos.scheduler.jobs.stats.JobStats
- Direction
- org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.jobs.stats, so a change to org.apache.mesos.chronos.scheduler.jobs.stats can break org.apache.mesos.chronos.scheduler.config, while a change to org.apache.mesos.chronos.scheduler.config can't break org.apache.mesos.chronos.scheduler.jobs.stats.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.config uses a module listed above it, which is the healthy direction.
24→22 org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.mesos✕
- Connections
- 2 pairs of types, where a type in org.apache.mesos.chronos.scheduler.config uses a type in org.apache.mesos.chronos.scheduler.mesos.
- The types involved
org.apache.mesos.chronos.scheduler.config.MainModule→org.apache.mesos.chronos.scheduler.mesos.MesosDriverFactoryorg.apache.mesos.chronos.scheduler.config.MainModule→org.apache.mesos.chronos.scheduler.mesos.MesosOfferReviver
- Direction
- org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.mesos, so a change to org.apache.mesos.chronos.scheduler.mesos can break org.apache.mesos.chronos.scheduler.config, while a change to org.apache.mesos.chronos.scheduler.config can't break org.apache.mesos.chronos.scheduler.mesos.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.config uses a module listed above it, which is the healthy direction.
24→23 org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.state✕
- Connections
- 2 pairs of types, where a type in org.apache.mesos.chronos.scheduler.config uses a type in org.apache.mesos.chronos.scheduler.state.
- The types involved
org.apache.mesos.chronos.scheduler.config.MainModule→org.apache.mesos.chronos.scheduler.state.PersistenceStoreorg.apache.mesos.chronos.scheduler.config.ZookeeperModule→org.apache.mesos.chronos.scheduler.state.PersistenceStore
- Direction
- org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.state, so a change to org.apache.mesos.chronos.scheduler.state can break org.apache.mesos.chronos.scheduler.config, while a change to org.apache.mesos.chronos.scheduler.config can't break org.apache.mesos.chronos.scheduler.state.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.config uses a module listed above it, which is the healthy direction.
24→25 org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.jobs part of a loop✕
- Connections
- 4 pairs of types, where a type in org.apache.mesos.chronos.scheduler.config uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.scheduler.config.MainModule→org.apache.mesos.chronos.scheduler.jobs.JobMetricsorg.apache.mesos.chronos.scheduler.config.MainModule→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.config.MainModule→org.apache.mesos.chronos.scheduler.jobs.TaskManagerorg.apache.mesos.chronos.scheduler.config.ZookeeperModule→org.apache.mesos.chronos.scheduler.jobs.ZookeeperService
- Direction
- org.apache.mesos.chronos.scheduler.config uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.scheduler.config, while a change to org.apache.mesos.chronos.scheduler.config can't break org.apache.mesos.chronos.scheduler.jobs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→4 org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.jobs.constraints✕
- Connections
- 3 pairs of types, where a type in org.apache.mesos.chronos.scheduler.jobs uses a type in org.apache.mesos.chronos.scheduler.jobs.constraints.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.BaseJob→org.apache.mesos.chronos.scheduler.jobs.constraints.Constraintorg.apache.mesos.chronos.scheduler.jobs.DependencyBasedJob→org.apache.mesos.chronos.scheduler.jobs.constraints.Constraintorg.apache.mesos.chronos.scheduler.jobs.ScheduleBasedJob→org.apache.mesos.chronos.scheduler.jobs.constraints.Constraint
- Direction
- org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.jobs.constraints, so a change to org.apache.mesos.chronos.scheduler.jobs.constraints can break org.apache.mesos.chronos.scheduler.jobs, while a change to org.apache.mesos.chronos.scheduler.jobs can't break org.apache.mesos.chronos.scheduler.jobs.constraints.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.jobs uses a module listed above it, which is the healthy direction.
25→20 org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.graph✕
- Connections
- 2 pairs of types, where a type in org.apache.mesos.chronos.scheduler.jobs uses a type in org.apache.mesos.chronos.scheduler.graph.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.JobScheduler→org.apache.mesos.chronos.scheduler.graph.JobGraphorg.apache.mesos.chronos.scheduler.jobs.TaskManager→org.apache.mesos.chronos.scheduler.graph.JobGraph
- Direction
- org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.graph, so a change to org.apache.mesos.chronos.scheduler.graph can break org.apache.mesos.chronos.scheduler.jobs, while a change to org.apache.mesos.chronos.scheduler.jobs can't break org.apache.mesos.chronos.scheduler.graph.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.jobs uses a module listed above it, which is the healthy direction.
25→22 org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.mesos✕
- Connections
- 3 pairs of types, where a type in org.apache.mesos.chronos.scheduler.jobs uses a type in org.apache.mesos.chronos.scheduler.mesos.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.JobScheduler→org.apache.mesos.chronos.scheduler.mesos.MesosDriverFactoryorg.apache.mesos.chronos.scheduler.jobs.TaskManager→org.apache.mesos.chronos.scheduler.mesos.MesosDriverFactoryorg.apache.mesos.chronos.scheduler.jobs.TaskManager→org.apache.mesos.chronos.scheduler.mesos.MesosOfferReviver
- Direction
- org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.mesos, so a change to org.apache.mesos.chronos.scheduler.mesos can break org.apache.mesos.chronos.scheduler.jobs, while a change to org.apache.mesos.chronos.scheduler.jobs can't break org.apache.mesos.chronos.scheduler.mesos.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.jobs uses a module listed above it, which is the healthy direction.
25→23 org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.state✕
- Connections
- 3 pairs of types, where a type in org.apache.mesos.chronos.scheduler.jobs uses a type in org.apache.mesos.chronos.scheduler.state.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.JobScheduler→org.apache.mesos.chronos.scheduler.state.PersistenceStoreorg.apache.mesos.chronos.scheduler.jobs.JobUtils→org.apache.mesos.chronos.scheduler.state.PersistenceStoreorg.apache.mesos.chronos.scheduler.jobs.TaskManager→org.apache.mesos.chronos.scheduler.state.PersistenceStore
- Direction
- org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.state, so a change to org.apache.mesos.chronos.scheduler.state can break org.apache.mesos.chronos.scheduler.jobs, while a change to org.apache.mesos.chronos.scheduler.jobs can't break org.apache.mesos.chronos.scheduler.state.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.jobs uses a module listed above it, which is the healthy direction.
25→24 org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.config✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.jobs uses a type in org.apache.mesos.chronos.scheduler.config.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.TaskManager→org.apache.mesos.chronos.scheduler.config.SchedulerConfiguration
- Direction
- org.apache.mesos.chronos.scheduler.jobs uses org.apache.mesos.chronos.scheduler.config, so a change to org.apache.mesos.chronos.scheduler.config can break org.apache.mesos.chronos.scheduler.jobs, while a change to org.apache.mesos.chronos.scheduler.jobs can't break org.apache.mesos.chronos.scheduler.config.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.jobs uses a module listed above it, which is the healthy direction.
26→25 org.apache.mesos.chronos.notification uses org.apache.mesos.chronos.scheduler.jobs✕
- Connections
- 7 pairs of types, where a type in org.apache.mesos.chronos.notification uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.notification.HttpClient→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.notification.JobNotificationObserver→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.notification.MailClient→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.notification.MattermostClient→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.notification.NotificationClient→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.notification.RavenClient→org.apache.mesos.chronos.scheduler.jobs.BaseJoborg.apache.mesos.chronos.notification.SlackClient→org.apache.mesos.chronos.scheduler.jobs.BaseJob
- Direction
- org.apache.mesos.chronos.notification uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.notification, while a change to org.apache.mesos.chronos.notification can't break org.apache.mesos.chronos.scheduler.jobs.
- Position
- Below the diagonal: org.apache.mesos.chronos.notification uses a module listed above it, which is the healthy direction.
27→20 org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.graph✕
- Connections
- 6 pairs of types, where a type in org.apache.mesos.chronos.scheduler.api uses a type in org.apache.mesos.chronos.scheduler.graph.
- The types involved
org.apache.mesos.chronos.scheduler.api.DependentJobResource→org.apache.mesos.chronos.scheduler.graph.JobGraphorg.apache.mesos.chronos.scheduler.api.GraphManagementResource→org.apache.mesos.chronos.scheduler.graph.JobGraphorg.apache.mesos.chronos.scheduler.api.Iso8601JobResource→org.apache.mesos.chronos.scheduler.graph.JobGraphorg.apache.mesos.chronos.scheduler.api.JobManagementResource→org.apache.mesos.chronos.scheduler.graph.JobGraphorg.apache.mesos.chronos.scheduler.api.StatsResource→org.apache.mesos.chronos.scheduler.graph.JobGraphorg.apache.mesos.chronos.scheduler.api.TaskManagementResource→org.apache.mesos.chronos.scheduler.graph.JobGraph
- Direction
- org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.graph, so a change to org.apache.mesos.chronos.scheduler.graph can break org.apache.mesos.chronos.scheduler.api, while a change to org.apache.mesos.chronos.scheduler.api can't break org.apache.mesos.chronos.scheduler.graph.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.api uses a module listed above it, which is the healthy direction.
27→21 org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.jobs.stats✕
- Connections
- 2 pairs of types, where a type in org.apache.mesos.chronos.scheduler.api uses a type in org.apache.mesos.chronos.scheduler.jobs.stats.
- The types involved
org.apache.mesos.chronos.scheduler.api.GraphManagementResource→org.apache.mesos.chronos.scheduler.jobs.stats.JobStatsorg.apache.mesos.chronos.scheduler.api.JobManagementResource→org.apache.mesos.chronos.scheduler.jobs.stats.JobStats
- Direction
- org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.jobs.stats, so a change to org.apache.mesos.chronos.scheduler.jobs.stats can break org.apache.mesos.chronos.scheduler.api, while a change to org.apache.mesos.chronos.scheduler.api can't break org.apache.mesos.chronos.scheduler.jobs.stats.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.api uses a module listed above it, which is the healthy direction.
27→23 org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.state✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.api uses a type in org.apache.mesos.chronos.scheduler.state.
- The types involved
org.apache.mesos.chronos.scheduler.api.TaskManagementResource→org.apache.mesos.chronos.scheduler.state.PersistenceStore
- Direction
- org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.state, so a change to org.apache.mesos.chronos.scheduler.state can break org.apache.mesos.chronos.scheduler.api, while a change to org.apache.mesos.chronos.scheduler.api can't break org.apache.mesos.chronos.scheduler.state.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.api uses a module listed above it, which is the healthy direction.
27→24 org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.config✕
- Connections
- 6 pairs of types, where a type in org.apache.mesos.chronos.scheduler.api uses a type in org.apache.mesos.chronos.scheduler.config.
- The types involved
org.apache.mesos.chronos.scheduler.api.GraphManagementResource→org.apache.mesos.chronos.scheduler.config.SchedulerConfigurationorg.apache.mesos.chronos.scheduler.api.JobManagementResource→org.apache.mesos.chronos.scheduler.config.CassandraConfigurationorg.apache.mesos.chronos.scheduler.api.JobManagementResource→org.apache.mesos.chronos.scheduler.config.SchedulerConfigurationorg.apache.mesos.chronos.scheduler.api.RedirectFilter→org.apache.mesos.chronos.scheduler.config.SchedulerConfigurationorg.apache.mesos.chronos.scheduler.api.StatsResource→org.apache.mesos.chronos.scheduler.config.SchedulerConfigurationorg.apache.mesos.chronos.scheduler.api.TaskManagementResource→org.apache.mesos.chronos.scheduler.config.SchedulerConfiguration
- Direction
- org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.config, so a change to org.apache.mesos.chronos.scheduler.config can break org.apache.mesos.chronos.scheduler.api, while a change to org.apache.mesos.chronos.scheduler.api can't break org.apache.mesos.chronos.scheduler.config.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.api uses a module listed above it, which is the healthy direction.
27→25 org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.jobs✕
- Connections
- 15 pairs of types, where a type in org.apache.mesos.chronos.scheduler.api uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.scheduler.api.DependentJobResource→org.apache.mesos.chronos.scheduler.jobs.DependencyBasedJoborg.apache.mesos.chronos.scheduler.api.DependentJobResource→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.api.Iso8601JobResource→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.api.Iso8601JobResource→org.apache.mesos.chronos.scheduler.jobs.ScheduleBasedJoborg.apache.mesos.chronos.scheduler.api.JobManagementResource→org.apache.mesos.chronos.scheduler.jobs.JobMetricsorg.apache.mesos.chronos.scheduler.api.JobManagementResource→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.api.JobManagementResource→org.apache.mesos.chronos.scheduler.jobs.TaskStatorg.apache.mesos.chronos.scheduler.api.JobStatWrapperSerializer→org.apache.mesos.chronos.scheduler.jobs.JobStatWrapperorg.apache.mesos.chronos.scheduler.api.JobSummaryWrapperSerializer→org.apache.mesos.chronos.scheduler.jobs.JobSummaryWrapperorg.apache.mesos.chronos.scheduler.api.LeaderResource→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.api.RedirectFilter→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.api.StatsResource→org.apache.mesos.chronos.scheduler.jobs.JobMetricsorg.apache.mesos.chronos.scheduler.api.StatsResource→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.api.TaskManagementResource→org.apache.mesos.chronos.scheduler.jobs.JobSchedulerorg.apache.mesos.chronos.scheduler.api.TaskManagementResource→org.apache.mesos.chronos.scheduler.jobs.TaskManager
- Direction
- org.apache.mesos.chronos.scheduler.api uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.scheduler.api, while a change to org.apache.mesos.chronos.scheduler.api can't break org.apache.mesos.chronos.scheduler.jobs.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.api uses a module listed above it, which is the healthy direction.
28→20 org.apache.mesos.chronos.scheduler.jobs.graph uses org.apache.mesos.chronos.scheduler.graph✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.jobs.graph uses a type in org.apache.mesos.chronos.scheduler.graph.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.graph.Exporter→org.apache.mesos.chronos.scheduler.graph.JobGraph
- Direction
- org.apache.mesos.chronos.scheduler.jobs.graph uses org.apache.mesos.chronos.scheduler.graph, so a change to org.apache.mesos.chronos.scheduler.graph can break org.apache.mesos.chronos.scheduler.jobs.graph, while a change to org.apache.mesos.chronos.scheduler.jobs.graph can't break org.apache.mesos.chronos.scheduler.graph.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.jobs.graph uses a module listed above it, which is the healthy direction.
28→21 org.apache.mesos.chronos.scheduler.jobs.graph uses org.apache.mesos.chronos.scheduler.jobs.stats✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.jobs.graph uses a type in org.apache.mesos.chronos.scheduler.jobs.stats.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.graph.Exporter→org.apache.mesos.chronos.scheduler.jobs.stats.JobStats
- Direction
- org.apache.mesos.chronos.scheduler.jobs.graph uses org.apache.mesos.chronos.scheduler.jobs.stats, so a change to org.apache.mesos.chronos.scheduler.jobs.stats can break org.apache.mesos.chronos.scheduler.jobs.graph, while a change to org.apache.mesos.chronos.scheduler.jobs.graph can't break org.apache.mesos.chronos.scheduler.jobs.stats.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.jobs.graph uses a module listed above it, which is the healthy direction.
28→25 org.apache.mesos.chronos.scheduler.jobs.graph uses org.apache.mesos.chronos.scheduler.jobs✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.jobs.graph uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.scheduler.jobs.graph.Exporter→org.apache.mesos.chronos.scheduler.jobs.BaseJob
- Direction
- org.apache.mesos.chronos.scheduler.jobs.graph uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.scheduler.jobs.graph, while a change to org.apache.mesos.chronos.scheduler.jobs.graph can't break org.apache.mesos.chronos.scheduler.jobs.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.jobs.graph uses a module listed above it, which is the healthy direction.
29→25 org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework uses org.apache.mesos.chronos.scheduler.jobs✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework.Resources→org.apache.mesos.chronos.scheduler.jobs.BaseJob
- Direction
- org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework, while a change to org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework can't break org.apache.mesos.chronos.scheduler.jobs.
- Position
- Below the diagonal: org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework uses a module listed above it, which is the healthy direction.
30→24 org.apache.mesos.chronos.utils uses org.apache.mesos.chronos.scheduler.config✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.utils uses a type in org.apache.mesos.chronos.scheduler.config.
- The types involved
org.apache.mesos.chronos.utils.JobDeserializer→org.apache.mesos.chronos.scheduler.config.SchedulerConfiguration
- Direction
- org.apache.mesos.chronos.utils uses org.apache.mesos.chronos.scheduler.config, so a change to org.apache.mesos.chronos.scheduler.config can break org.apache.mesos.chronos.utils, while a change to org.apache.mesos.chronos.utils can't break org.apache.mesos.chronos.scheduler.config.
- Position
- Below the diagonal: org.apache.mesos.chronos.utils uses a module listed above it, which is the healthy direction.
30→25 org.apache.mesos.chronos.utils uses org.apache.mesos.chronos.scheduler.jobs✕
- Connections
- 1 pair of types, where a type in org.apache.mesos.chronos.utils uses a type in org.apache.mesos.chronos.scheduler.jobs.
- The types involved
org.apache.mesos.chronos.utils.JobSerializer→org.apache.mesos.chronos.scheduler.jobs.BaseJob
- Direction
- org.apache.mesos.chronos.utils uses org.apache.mesos.chronos.scheduler.jobs, so a change to org.apache.mesos.chronos.scheduler.jobs can break org.apache.mesos.chronos.utils, while a change to org.apache.mesos.chronos.utils can't break org.apache.mesos.chronos.scheduler.jobs.
- Position
- Below the diagonal: org.apache.mesos.chronos.utils uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 5 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED; Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with JobDeserializer.scala, JobManagementResource.scala, MesosJobFramework.scala; Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +5.7 pts | Low | ADR Quality |
| Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with JobDeserializer.scala, JobManagementResource.scala, MesosJobFramework.scala. | +5.4 pts | Medium | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.4 pts | Medium | Security & performance tooling |
| Add tests that import the unreached modules (directly or through their public entry). | +4.4 pts | Medium | Test Coverage |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.3 pts | Medium | Architecture documentation |
| 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. | +3.0 pts | Medium | CI/CD gates |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +2.5 pts | Medium | Type Safety |
| Resolve the 1 No Gemfile.lock committed by an application finding(s) in Dependency Hygiene. | +1.2 pts | Low | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.9 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| src/main/scala/org/apache/mesos/chronos/utils/JobDeserializer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/api/DependentJobResource.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/api/Iso8601JobResource.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/state/MesosStatePersistenceStore.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/graph/JobGraph.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosJobFramework.scala | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/notification/MattermostClient.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (46 corresponding lines) |
| src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobSchedule.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobUtils.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/jobs/ScheduledTask.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/config/MainModule.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/config/SchedulerConfiguration.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/config/ZookeeperModule.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/org/apache/mesos/chronos/scheduler/api/GraphManagementResource.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 53 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 53 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, 118 of 135 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Maven POM, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Maven dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Every one of the 29 significant source file(s) was last meaningfully changed so long ago that no living knowledge remains, so there is no concentration to measure — the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/main/scala/org/apache/mesos/chronos/scheduler/jobs/Jobs.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.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Guice, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.datastax' is imported (REDACTED:7), 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.datastax' is imported (REDACTED:7), 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.datastax' is imported (REDACTED:7), 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.
- X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was JobDeserializer.deserialize at 99.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with JobDeserializer.deserialize (cyclomatic 99). — Refactoring it lifts Cyclomatic Complexity from 7.9 to about 10.0/10.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was JobDeserializer.deserialize at 192.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with JobDeserializer.deserialize (cognitive 192). — Refactoring it lifts Cognitive Complexity from 6.7 to about 7.9/10.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with JobSerializer.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with JobScheduler.scala. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
8 duplicated block group(s) detected. 8.3 % of the production lines (535 of 6,450) are in a reported copy. A further 5 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (21 lines × 2) finding(s) in Code Duplication — start with REDACTED, JobDeserializer.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (15 members, 50+ identical tokens) finding(s) in Code Duplication — start with DependentJobResource.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 23 classes have LCOM4 above 3.
D12 · Dependency Hygiene
0 outdated direct gem(s), 1 pinning defect(s). 12 declaration(s) graded against rubygems.org, none of them against a committed Gemfile.lock — this repository commits none, which a published gem correctly does not, so currency is read off the declared requirements: a declaration that does not cap below the current release resolves to it on `bundle install`. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 1 No Gemfile.lock committed by an application finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 12 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 12 runtime gem(s) this repository declares. It commits no Gemfile.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Maven POM, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
28 deducted task-comment markers across 6450 LoC (0.3/KLoC) → score 9.3. 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 28 TodoComment finding(s) in Explicit Debt — start with MesosTaskBuilder.scala (4), MesosStatePersistenceStore.scala (3), JobScheduler.scala (3). — One of this dimension's main actionable groups (28 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 14 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Maven, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 2 high, 2 medium, 0 low. semgrep hit a parse error in 3 file(s) — `docs/_layouts/default.html` (line 37, line 40, line 43), `docs/_layouts/docs.html` (lines 1–3), `src/main/scala/org/apache/mesos/chronos/scheduler/jobs/Jobs.scala` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 3 high, 2 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 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
5 finding(s): 0 critical, 1 high, 2 medium, 2 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
29 of 29 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/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala. Counted over 29 of the 75 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 27 Orphaned file finding(s) in Knowledge Freshness — start with JobDeserializer.scala, JobManagementResource.scala, MesosJobFramework.scala. — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with JobScheduler.scala, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: JobDeserializer.scala↔JobSerializer.scala 91%; MesosTaskBuilder.scala↔JobSerializer.scala 55%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with JobDeserializer.scala, MesosTaskBuilder.scala. — One of this dimension's main actionable groups (2 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 39 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- 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.
P2 · Observability
- Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `src/main/resources/ui`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `src/main/resources/ui/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/main/resources/ui/package.json:21
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `HttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/main/scala/org/apache/mesos/chronos/notification/HttpClient.scala:11
- `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/main/scala/org/apache/mesos/chronos/scheduler/api/RedirectFilter.scala:51
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
R1 · Type Safety
- 0 typed · 13 plain JS — the untyped files are src/main/resources/ui/components/Footer.js, src/main/resources/ui/components/Header.js, src/main/resources/ui/components/JobEditor.js, src/main/resources/ui/components/JobSummaryView.js, REDACTED, src/main/resources/ui/components/Main.js (+7 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- src/main/resources/ui/components/JobEditor.js:33 · src/main/resources/ui/components/JobEditor.js:79 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/main/resources/ui/components/JobEditor.js:33
- src/main/resources/ui/components/JobEditor.js:142 · src/main/resources/ui/components/JobEditor.js:175 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/main/resources/ui/components/JobEditor.js:142
- src/main/resources/ui/webpack-release.config.js:15 · src/main/resources/ui/webpack.config.js:17 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/main/resources/ui/webpack-release.config.js:15
- src/main/resources/ui/models/JobForm.js:248 · src/main/resources/ui/models/JobForm.js:263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/main/resources/ui/models/JobForm.js:248
- src/main/resources/ui/components/JobEditor.js:248 · REDACTED:118 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/main/resources/ui/components/JobEditor.js:248
- src/main/resources/ui/server.js:122 · src/main/resources/ui/server.js:136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/main/resources/ui/server.js:122
- REDACTED:73 · src/main/resources/ui/models/JobForm.js:395 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — REDACTED:73
- src/main/resources/ui/models/JobForm.js:280 · src/main/resources/ui/models/JobForm.js:298 · src/main/resources/ui/models/JobForm.js:313 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/main/resources/ui/models/JobForm.js:280
- src/main/resources/ui/components/JobSummaryView.js:62 · src/main/resources/ui/components/JobSummaryView.js:71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/main/resources/ui/components/JobSummaryView.js:62
- src/main/resources/ui/server.js:92 · src/main/resources/ui/server.js:100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/main/resources/ui/server.js:92
- src/main/resources/ui/components/JobEditor.js:279 · src/main/resources/ui/components/JobEditor.js:286 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/main/resources/ui/components/JobEditor.js:279
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/main/resources/ui/models/JobForm.js:409
R3 · Large Files
- src/main/resources/ui/models/JobForm.js has 432 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/main/resources/ui/models/JobForm.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 0% of 13 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✗ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
- Declared in src/main/resources/ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: src/main/scala/org/apache/mesos/chronos/scheduler/api/WebJarServlet.scala:12 — `HttpServlet`.
- 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 set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: src/main/scala/org/apache/mesos/chronos/scheduler/api/WebJarServlet.scala:12 — `HttpServlet`.
What to do
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X23 · Unguarded diagnostic materialisation
- `fine` at line 299 is called with an argument built by `dependents.mkString("…")` (line 300), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because fine is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:299
- `fine` at line 172 is called with an argument built by `results.mkString("…")` (line 172), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because fine is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — src/main/scala/org/apache/mesos/chronos/scheduler/graph/JobGraph.scala:172
What to do
- In Scala, put the construction behind the logger's own check (`if (log.isDebugEnabled)`), or log through a logger that takes the message by name or by macro and so builds it only when the level is on — scala-logging's `LazyLogging`/`StrictLogging` (`logger.debug(s"rows: ${rows.mkString(", ")}")` expands to that check), log4s or log4cats. Interpolating into an `s"…"` is not the fix on SLF4J or Akka's `LoggingAdapter`: their `debug` takes a `String`, so the interpolation and every `mkString` inside it run before the call is entered.
X27 · Collection changed while being enumerated
X3 · Exception handling
- `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:369
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
X5 · Nullable reference types
- No build over this repository's 74 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 | 40% | Weak — gated by R1, R10, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 43% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 23% | Critical — gated by R4, R6, P1, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Strong | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'com.datastax' (REDACTED:7) 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 'com.datastax' (REDACTED:7) 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 'com.datastax' (REDACTED:7) 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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 — ~1830 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .scala test runner
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (948 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rb, .scala source were not judged.
- 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
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Maven build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 14 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 14 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); M4 checks only links and versions and artefact counts.
- 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'.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was 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
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 83 finding(s)
- TodoComment src/main/scala/org/apache/mesos/chronos/utils/JobDeserializer.scala:230
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/state/MesosStatePersistenceStore.scala:25
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/state/MesosStatePersistenceStore.scala:26
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/state/MesosStatePersistenceStore.scala:27
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosJobFramework.scala:87
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosJobFramework.scala:192
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala:58
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala:263
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala:269
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala:293
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobSchedule.scala:5
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:58
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:144
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/api/DependentJobResource.scala:51
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:302
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobUtils.scala:38
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/jobs/ScheduledTask.scala:20
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/graph/JobGraph.scala:132
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/graph/JobGraph.scala:133
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/graph/JobGraph.scala:136
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/config/MainModule.scala:46
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/config/SchedulerConfiguration.scala:25
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/config/ZookeeperModule.scala:22
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/api/DependentJobResource.scala:58
- TodoComment src/main/scala/org/apache/mesos/chronos/scheduler/api/GraphManagementResource.scala:22
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: JobDeserializer.scala ↔ JobSerializer.scala src/main/scala/org/apache/mesos/chronos/utils/JobDeserializer.scala:1
- Change coupling: MesosTaskBuilder.scala ↔ JobSerializer.scala src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala:1
- Duplicated block (21 lines × 2) REDACTED:432
- Duplicated block (21 lines × 2) src/main/scala/org/apache/mesos/chronos/utils/JobDeserializer.scala:393
- Outbound HTTP without resilience src/main/scala/org/apache/mesos/chronos/notification/HttpClient.scala:11
- Outbound HTTP without resilience src/main/scala/org/apache/mesos/chronos/scheduler/api/RedirectFilter.scala:51
- Duplicated block (23 lines × 2 locations) src/main/resources/ui/components/JobEditor.js:33
- Duplicated block (23 lines × 2 locations) src/main/resources/ui/components/JobEditor.js:142
- Duplicated block (13 lines × 2 locations) src/main/resources/ui/components/JobEditor.js:248
- Duplicated block (13 lines × 2 locations) src/main/resources/ui/server.js:122
- JobDeserializer.deserialize (cyclomatic 99) src/main/scala/org/apache/mesos/chronos/utils/JobDeserializer.scala:29
- No Gemfile.lock committed by an application
- JobDeserializer.deserialize (cognitive 192) src/main/scala/org/apache/mesos/chronos/utils/JobDeserializer.scala:29
- RedirectFilter.doFilter (cognitive 48) src/main/scala/org/apache/mesos/chronos/scheduler/api/RedirectFilter.scala:31
- JobForm.toJS (cognitive 34) src/main/resources/ui/models/JobForm.js:407
- JobScheduler.handleFailedTask (cognitive 32) src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:343
- MesosTaskBuilder.getMesosTaskInfoBuilder (cognitive 25) src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala:55
- JobStats.insertToStatTable (cognitive 19) REDACTED:510
- Iso8601JobResource.post (cognitive 18) src/main/scala/org/apache/mesos/chronos/scheduler/api/Iso8601JobResource.scala:31
- MethodTooLong: JobSerializer.serialize src/main/scala/org/apache/mesos/chronos/utils/JobSerializer.scala:23
- ClassTooLong: JobScheduler src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:34
- Members sharing a duplicated core (15 members, 50+ identical tokens) src/main/scala/org/apache/mesos/chronos/scheduler/api/DependentJobResource.scala:34
- Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:121
- Edited copy of a member (46 corresponding lines) src/main/scala/org/apache/mesos/chronos/notification/MattermostClient.scala:14
- Edited copy of a member (24 corresponding lines) REDACTED:429
- Edited copy of a member (19 corresponding lines) src/main/scala/org/apache/mesos/chronos/scheduler/jobs/constraints/LikeConstraint.scala:15
- Duplicated block (28 lines × 2) src/main/scala/org/apache/mesos/chronos/notification/MattermostClient.scala:16
- Duplicated block (16–17 lines × 15) src/main/scala/org/apache/mesos/chronos/scheduler/api/DependentJobResource.scala:84
- Duplicated block (17 lines × 3) src/main/scala/org/apache/mesos/chronos/utils/JobDeserializer.scala:390
- Duplicated block (15 lines × 3) src/main/scala/org/apache/mesos/chronos/notification/HttpClient.scala:78
- Duplicated block (11–12 lines × 2) src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:164
- Duplicated block (9 lines × 4) REDACTED:147
- CI pipeline targets a decommissioned service
- Type Safety
- Duplicated block (22 lines × 2 locations) src/main/resources/ui/webpack-release.config.js:15
- Duplicated block (14 lines × 2 locations) src/main/resources/ui/models/JobForm.js:248
- Duplicated block (11 lines × 2 locations) REDACTED:73
- Duplicated block (11 lines × 3 locations) src/main/resources/ui/models/JobForm.js:280
- Duplicated block (9 lines × 2 locations) src/main/resources/ui/components/JobSummaryView.js:62
- Duplicated block (8 lines × 2 locations) src/main/resources/ui/server.js:92
- Duplicated block (7 lines × 2 locations) src/main/resources/ui/components/JobEditor.js:279
- Complex function (anonymous) (cyclomatic 12, cognitive 24) src/main/resources/ui/models/JobForm.js:409
- src/main/resources/ui/models/JobForm.js: 432 lines of code src/main/resources/ui/models/JobForm.js:1
- Test Coverage
- No test or typecheck script
- Unused dependency 'mobx-react-form'
- Unused dependency 'validatorjs'
- JavaScript dependencies are not locked src/main/resources/ui/package.json:21
- Swallowed exception (caught, then discarded) src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:369
Minor — 46 finding(s)
- Orphaned file src/main/scala/org/apache/mesos/chronos/utils/JobDeserializer.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/api/JobManagementResource.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosJobFramework.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/jobs/TaskManager.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/utils/JobSerializer.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/jobs/Jobs.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/graph/JobGraph.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/config/SchedulerConfiguration.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/config/MainModule.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobUtils.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/api/Iso8601JobResource.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/api/RedirectFilter.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/state/MesosStatePersistenceStore.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/api/DependentJobResource.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/mesos/SchedulerDriverBuilder.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/config/ZookeeperModule.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/api/WebJarServlet.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/notification/HttpClient.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/jobs/TaskUtils.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/api/ChronosRestModule.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/jobs/Iso8601Expressions.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/api/StatsResource.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosOfferReviverActor.scala:1
- Orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/jobs/TaskStat.scala:1
- REDACTED
- REDACTED
- Most significant orphaned file src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:1
- Most significant orphaned file REDACTED:1
- Diagnostic log message is built whether or not it is wanted src/main/scala/org/apache/mesos/chronos/scheduler/jobs/JobScheduler.scala:299
- Diagnostic log message is built whether or not it is wanted src/main/scala/org/apache/mesos/chronos/scheduler/graph/JobGraph.scala:172
- No ADRs found REDACTED:372
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST
- No dependency-update automation src/main/resources/ui/package.json:21
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Duplicated predicate src/main/scala/org/apache/mesos/chronos/notification/HttpClient.scala:28
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5bf84d724b574cb183ca2c970fe5d70f/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5bf84d724b574cb183ca2c970fe5d70f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 5 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | 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/org/apache/mesos/chronos/scheduler/jobs/Jobs.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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |