Executive summary
apache/livy is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 47 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Accessibility, at 42, is the weakest lens, level with Code Health, and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 4 points. Recording design decisions comes next, worth about 2 points. Raising Accessibility to 65 would lift the score to about 50.
Forty-two known security holes in the packages the code depends on can be used by attackers. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks. The three places where the code runs text as code or as a command need a direct call instead. The three unsafe settings in infrastructure or container files need changing to safe values.
The product code is 25,195 lines, about €35,000 to rebuild.
If Accessibility rose from 42 to 65, the lowest score rated Strong, the score would rise from 47 to about 50.
New since the last survey: 16 findings
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/css/style.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css
Fixed since the last survey: 2 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €35,000 · Estimate
| Cost to rebuild | €12,000 to €59,000, for 196 to 621 hours of work, about 0.2 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 47. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 25,195 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 dev | 2 docs.assets.themes.apache.bootstrap.js | 3 org.apache | 4 org.apache.livy | 5 org.apache.livy.EOLUtils | 6 org.apache.livy.LivyConf | 7 org.apache.livy.server.ui.UIServlet | 8 org.apache.livy.sessions.Session | 9 org.apache.livy.sessions.SessionManager | 10 org.apache.livy.thriftserver.serde | 11 org.apache.livy.thriftserver.types | 12 org.apache.livy.utils.SparkApp | 13 org.apache.livy.ExecutionStatus | 14 org.apache.livy.MsgType | 15 org.apache.livy.client.common | 16 org.apache.livy.repl | 17 org.apache.livy.repl.Interpreter | 18 org.apache.livy.scalaapi | 19 org.apache.livy.server.auth | 20 org.apache.livy.server.recovery | 21 org.apache.livy.server.ui | 22 org.apache.livy.thriftserver.auth.ldap | 23 org.apache.livy.thriftserver.cli | 24 org.apache.livy.thriftserver.operation | 25 org.apache.livy.thriftserver.rpc | 26 org.apache.livy.thriftserver.session | 27 org.apache.livy.utils | 28 org.apache.livy.client.http | 29 org.apache.livy.rsc.rpc | 30 org.apache.livy.server.interactive | 31 org.apache.livy.thriftserver.auth | 32 org.apache.livy.utils.KubernetesExtensions | 33 org.apache.livy.rsc.driver | 34 org.apache.livy.sessions | 35 org.apache.livy.rsc | 36 org.apache.livy.server | 37 org.apache.livy.sessions.SessionState | 38 org.apache.livy.server.batch | 39 org.apache.livy.thriftserver | 40 org.apache.livy.thriftserver.ui |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 dev | ||||||||||||||||||||||||||||||||||||||||
| 2 docs.assets.themes.apache.bootstrap.js | ||||||||||||||||||||||||||||||||||||||||
| 3 org.apache | ||||||||||||||||||||||||||||||||||||||||
| 4 org.apache.livy | ||||||||||||||||||||||||||||||||||||||||
| 5 org.apache.livy.EOLUtils | ||||||||||||||||||||||||||||||||||||||||
| 6 org.apache.livy.LivyConf | ||||||||||||||||||||||||||||||||||||||||
| 7 org.apache.livy.server.ui.UIServlet | ||||||||||||||||||||||||||||||||||||||||
| 8 org.apache.livy.sessions.Session | ||||||||||||||||||||||||||||||||||||||||
| 9 org.apache.livy.sessions.SessionManager | ||||||||||||||||||||||||||||||||||||||||
| 10 org.apache.livy.thriftserver.serde | ||||||||||||||||||||||||||||||||||||||||
| 11 org.apache.livy.thriftserver.types | ||||||||||||||||||||||||||||||||||||||||
| 12 org.apache.livy.utils.SparkApp | ||||||||||||||||||||||||||||||||||||||||
| 13 org.apache.livy.ExecutionStatus | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 org.apache.livy.MsgType | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 org.apache.livy.client.common | 4 | |||||||||||||||||||||||||||||||||||||||
| 16 org.apache.livy.repl | 7 | |||||||||||||||||||||||||||||||||||||||
| 17 org.apache.livy.repl.Interpreter | 4 | |||||||||||||||||||||||||||||||||||||||
| 18 org.apache.livy.scalaapi | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 org.apache.livy.server.auth | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 org.apache.livy.server.recovery | 6 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 org.apache.livy.server.ui | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 org.apache.livy.thriftserver.auth.ldap | 4 | |||||||||||||||||||||||||||||||||||||||
| 23 org.apache.livy.thriftserver.cli | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 24 org.apache.livy.thriftserver.operation | 8 | 3 | 8 | |||||||||||||||||||||||||||||||||||||
| 25 org.apache.livy.thriftserver.rpc | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 org.apache.livy.thriftserver.session | 15 | |||||||||||||||||||||||||||||||||||||||
| 27 org.apache.livy.utils | 15 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 org.apache.livy.client.http | 6 | 7 | ||||||||||||||||||||||||||||||||||||||
| 29 org.apache.livy.rsc.rpc | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 30 org.apache.livy.server.interactive | 3 | 1 | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 31 org.apache.livy.thriftserver.auth | 7 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 org.apache.livy.utils.KubernetesExtensions | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 org.apache.livy.rsc.driver | 10 | 2 | 2 | 11 | ||||||||||||||||||||||||||||||||||||
| 34 org.apache.livy.sessions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 org.apache.livy.rsc | 12 | 5 | 7 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 org.apache.livy.server | 6 | 2 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 37 org.apache.livy.sessions.SessionState | 11 | |||||||||||||||||||||||||||||||||||||||
| 38 org.apache.livy.server.batch | 2 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 39 org.apache.livy.thriftserver | 12 | 3 | 2 | 2 | 3 | 2 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||
| 40 org.apache.livy.thriftserver.ui | 1 |
13→4 org.apache.livy.ExecutionStatus uses org.apache.livy✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.ExecutionStatus uses a type in org.apache.livy.
- The types involved
org.apache.livy.ExecutionStatus.abort→org.apache.livy.ExecutionStatusorg.apache.livy.ExecutionStatus.error→org.apache.livy.ExecutionStatusorg.apache.livy.ExecutionStatus.ok→org.apache.livy.ExecutionStatus
- Direction
- org.apache.livy.ExecutionStatus uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.ExecutionStatus, while a change to org.apache.livy.ExecutionStatus can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.ExecutionStatus uses a module listed above it, which is the healthy direction.
14→4 org.apache.livy.MsgType uses org.apache.livy✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.MsgType uses a type in org.apache.livy.
- The types involved
org.apache.livy.MsgType.execute_reply→org.apache.livy.MsgTypeorg.apache.livy.MsgType.execute_request→org.apache.livy.MsgType
- Direction
- org.apache.livy.MsgType uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.MsgType, while a change to org.apache.livy.MsgType can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.MsgType uses a module listed above it, which is the healthy direction.
15→4 org.apache.livy.client.common uses org.apache.livy✕
- Connections
- 4 pairs of types, where a type in org.apache.livy.client.common uses a type in org.apache.livy.
- The types involved
org.apache.livy.client.common.AbstractJobHandle→org.apache.livy.JobHandleorg.apache.livy.client.common.AbstractJobHandle→org.apache.livy.Listenerorg.apache.livy.client.common.AbstractJobHandle→org.apache.livy.Stateorg.apache.livy.client.common.JobStatus→org.apache.livy.State
- Direction
- org.apache.livy.client.common uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.client.common, while a change to org.apache.livy.client.common can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.client.common uses a module listed above it, which is the healthy direction.
16→4 org.apache.livy.repl uses org.apache.livy✕
- Connections
- 7 pairs of types, where a type in org.apache.livy.repl uses a type in org.apache.livy.
- The types involved
org.apache.livy.repl.ProcessInterpreter→org.apache.livy.ExecuteResponseorg.apache.livy.repl.ProcessInterpreter→org.apache.livy.Loggingorg.apache.livy.repl.PythonInterpreter→org.apache.livy.Loggingorg.apache.livy.repl.ReplDriver→org.apache.livy.Loggingorg.apache.livy.repl.SQLInterpreter→org.apache.livy.ExecuteResponseorg.apache.livy.repl.SQLInterpreter→org.apache.livy.Loggingorg.apache.livy.repl.SparkRInterpreter→org.apache.livy.Logging
- Direction
- org.apache.livy.repl uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.repl, while a change to org.apache.livy.repl can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.repl uses a module listed above it, which is the healthy direction.
17→4 org.apache.livy.repl.Interpreter uses org.apache.livy✕
- Connections
- 4 pairs of types, where a type in org.apache.livy.repl.Interpreter uses a type in org.apache.livy.
- The types involved
org.apache.livy.repl.Interpreter.ExecuteAborted→org.apache.livy.ExecuteResponseorg.apache.livy.repl.Interpreter.ExecuteError→org.apache.livy.ExecuteResponseorg.apache.livy.repl.Interpreter.ExecuteIncomplete→org.apache.livy.ExecuteResponseorg.apache.livy.repl.Interpreter.ExecuteSuccess→org.apache.livy.ExecuteResponse
- Direction
- org.apache.livy.repl.Interpreter uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.repl.Interpreter, while a change to org.apache.livy.repl.Interpreter can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.repl.Interpreter uses a module listed above it, which is the healthy direction.
18→12 org.apache.livy.scalaapi uses org.apache.livy.utils.SparkApp✕
- Connections
- 1 pair of types, where a type in org.apache.livy.scalaapi uses a type in org.apache.livy.utils.SparkApp.
- The types involved
org.apache.livy.scalaapi.ScalaJobHandle→org.apache.livy.utils.SparkApp.State
- Direction
- org.apache.livy.scalaapi uses org.apache.livy.utils.SparkApp, so a change to org.apache.livy.utils.SparkApp can break org.apache.livy.scalaapi, while a change to org.apache.livy.scalaapi can't break org.apache.livy.utils.SparkApp.
- Position
- Below the diagonal: org.apache.livy.scalaapi uses a module listed above it, which is the healthy direction.
19→4 org.apache.livy.server.auth uses org.apache.livy✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.auth uses a type in org.apache.livy.
- The types involved
org.apache.livy.server.auth.LdapUtils→org.apache.livy.LivyConf
- Direction
- org.apache.livy.server.auth uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.server.auth, while a change to org.apache.livy.server.auth can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.server.auth uses a module listed above it, which is the healthy direction.
20→4 org.apache.livy.server.recovery uses org.apache.livy✕
- Connections
- 6 pairs of types, where a type in org.apache.livy.server.recovery uses a type in org.apache.livy.
- The types involved
org.apache.livy.server.recovery.FileSystemStateStore→org.apache.livy.LivyConforg.apache.livy.server.recovery.FileSystemStateStore→org.apache.livy.Loggingorg.apache.livy.server.recovery.RecoveryServlet→org.apache.livy.Loggingorg.apache.livy.server.recovery.SessionStore→org.apache.livy.Loggingorg.apache.livy.server.recovery.ZooKeeperManager→org.apache.livy.LivyConforg.apache.livy.server.recovery.ZooKeeperManager→org.apache.livy.Logging
- Direction
- org.apache.livy.server.recovery uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.server.recovery, while a change to org.apache.livy.server.recovery can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.server.recovery uses a module listed above it, which is the healthy direction.
20→8 org.apache.livy.server.recovery uses org.apache.livy.sessions.Session✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.recovery uses a type in org.apache.livy.sessions.Session.
- The types involved
org.apache.livy.server.recovery.SessionStore→org.apache.livy.sessions.Session.RecoveryMetadata
- Direction
- org.apache.livy.server.recovery uses org.apache.livy.sessions.Session, so a change to org.apache.livy.sessions.Session can break org.apache.livy.server.recovery, while a change to org.apache.livy.server.recovery can't break org.apache.livy.sessions.Session.
- Position
- Below the diagonal: org.apache.livy.server.recovery uses a module listed above it, which is the healthy direction.
20→9 org.apache.livy.server.recovery uses org.apache.livy.sessions.SessionManager✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.recovery uses a type in org.apache.livy.sessions.SessionManager.
- The types involved
org.apache.livy.server.recovery.RecoveryServlet→org.apache.livy.sessions.SessionManager.RefreshResult
- Direction
- org.apache.livy.server.recovery uses org.apache.livy.sessions.SessionManager, so a change to org.apache.livy.sessions.SessionManager can break org.apache.livy.server.recovery, while a change to org.apache.livy.server.recovery can't break org.apache.livy.sessions.SessionManager.
- Position
- Below the diagonal: org.apache.livy.server.recovery uses a module listed above it, which is the healthy direction.
20→36 org.apache.livy.server.recovery uses org.apache.livy.server part of a loop✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.recovery uses a type in org.apache.livy.server.
- The types involved
org.apache.livy.server.recovery.RecoveryServlet→org.apache.livy.server.JsonServlet
- Direction
- org.apache.livy.server.recovery uses org.apache.livy.server, so a change to org.apache.livy.server can break org.apache.livy.server.recovery, while a change to org.apache.livy.server.recovery can't break org.apache.livy.server.
- 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→7 org.apache.livy.server.ui uses org.apache.livy.server.ui.UIServlet✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.server.ui uses a type in org.apache.livy.server.ui.UIServlet.
- The types involved
org.apache.livy.server.ui.UIServlet→org.apache.livy.server.ui.UIServlet.LogPageorg.apache.livy.server.ui.UIServlet→org.apache.livy.server.ui.UIServlet.Page
- Direction
- org.apache.livy.server.ui uses org.apache.livy.server.ui.UIServlet, so a change to org.apache.livy.server.ui.UIServlet can break org.apache.livy.server.ui, while a change to org.apache.livy.server.ui can't break org.apache.livy.server.ui.UIServlet.
- Position
- Below the diagonal: org.apache.livy.server.ui uses a module listed above it, which is the healthy direction.
22→4 org.apache.livy.thriftserver.auth.ldap uses org.apache.livy✕
- Connections
- 4 pairs of types, where a type in org.apache.livy.thriftserver.auth.ldap uses a type in org.apache.livy.
- The types involved
org.apache.livy.thriftserver.auth.ldap.DirSearchFactory→org.apache.livy.LivyConforg.apache.livy.thriftserver.auth.ldap.LdapSearchFactory→org.apache.livy.LivyConforg.apache.livy.thriftserver.auth.ldap.LdapSearchFactory→org.apache.livy.Loggingorg.apache.livy.thriftserver.auth.ldap.UserFilter→org.apache.livy.Logging
- Direction
- org.apache.livy.thriftserver.auth.ldap uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.thriftserver.auth.ldap, while a change to org.apache.livy.thriftserver.auth.ldap can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.thriftserver.auth.ldap uses a module listed above it, which is the healthy direction.
23→4 org.apache.livy.thriftserver.cli uses org.apache.livy✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.thriftserver.cli uses a type in org.apache.livy.
- The types involved
org.apache.livy.thriftserver.cli.ThriftCLIService→org.apache.livy.LivyConforg.apache.livy.thriftserver.cli.ThriftHttpServlet→org.apache.livy.LivyConforg.apache.livy.thriftserver.cli.ThriftHttpServlet→org.apache.livy.Logging
- Direction
- org.apache.livy.thriftserver.cli uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.thriftserver.cli, while a change to org.apache.livy.thriftserver.cli can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.thriftserver.cli uses a module listed above it, which is the healthy direction.
23→31 org.apache.livy.thriftserver.cli uses org.apache.livy.thriftserver.auth part of a loop✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.thriftserver.cli uses a type in org.apache.livy.thriftserver.auth.
- The types involved
org.apache.livy.thriftserver.cli.ThriftCLIService→org.apache.livy.thriftserver.auth.AuthFactoryorg.apache.livy.thriftserver.cli.ThriftHttpServlet→org.apache.livy.thriftserver.auth.AuthFactory
- Direction
- org.apache.livy.thriftserver.cli uses org.apache.livy.thriftserver.auth, so a change to org.apache.livy.thriftserver.auth can break org.apache.livy.thriftserver.cli, while a change to org.apache.livy.thriftserver.cli can't break org.apache.livy.thriftserver.auth.
- 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→39 org.apache.livy.thriftserver.cli uses org.apache.livy.thriftserver part of a loop✕
- Connections
- 4 pairs of types, where a type in org.apache.livy.thriftserver.cli uses a type in org.apache.livy.thriftserver.
- The types involved
org.apache.livy.thriftserver.cli.ThriftBinaryCLIService→org.apache.livy.thriftserver.LivyCLIServiceorg.apache.livy.thriftserver.cli.ThriftCLIService→org.apache.livy.thriftserver.LivyCLIServiceorg.apache.livy.thriftserver.cli.ThriftCLIService→org.apache.livy.thriftserver.ThriftServiceorg.apache.livy.thriftserver.cli.ThriftHttpCLIService→org.apache.livy.thriftserver.LivyCLIService
- Direction
- org.apache.livy.thriftserver.cli uses org.apache.livy.thriftserver, so a change to org.apache.livy.thriftserver can break org.apache.livy.thriftserver.cli, while a change to org.apache.livy.thriftserver.cli can't break org.apache.livy.thriftserver.
- 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→4 org.apache.livy.thriftserver.operation uses org.apache.livy✕
- Connections
- 8 pairs of types, where a type in org.apache.livy.thriftserver.operation uses a type in org.apache.livy.
- The types involved
org.apache.livy.thriftserver.operation.GetCatalogsOperation→org.apache.livy.Loggingorg.apache.livy.thriftserver.operation.GetColumnsOperation→org.apache.livy.Loggingorg.apache.livy.thriftserver.operation.GetFunctionsOperation→org.apache.livy.Loggingorg.apache.livy.thriftserver.operation.GetSchemasOperation→org.apache.livy.Loggingorg.apache.livy.thriftserver.operation.GetTableTypesOperation→org.apache.livy.Loggingorg.apache.livy.thriftserver.operation.GetTablesOperation→org.apache.livy.Loggingorg.apache.livy.thriftserver.operation.GetTypeInfoOperation→org.apache.livy.Loggingorg.apache.livy.thriftserver.operation.Operation→org.apache.livy.Logging
- Direction
- org.apache.livy.thriftserver.operation uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.thriftserver.operation, while a change to org.apache.livy.thriftserver.operation can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.thriftserver.operation uses a module listed above it, which is the healthy direction.
24→10 org.apache.livy.thriftserver.operation uses org.apache.livy.thriftserver.serde✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.thriftserver.operation uses a type in org.apache.livy.thriftserver.serde.
- The types involved
org.apache.livy.thriftserver.operation.MetadataOperation→org.apache.livy.thriftserver.serde.ThriftResultSetorg.apache.livy.thriftserver.operation.Operation→org.apache.livy.thriftserver.serde.ThriftResultSetorg.apache.livy.thriftserver.operation.SparkCatalogOperation→org.apache.livy.thriftserver.serde.ThriftResultSet
- Direction
- org.apache.livy.thriftserver.operation uses org.apache.livy.thriftserver.serde, so a change to org.apache.livy.thriftserver.serde can break org.apache.livy.thriftserver.operation, while a change to org.apache.livy.thriftserver.operation can't break org.apache.livy.thriftserver.serde.
- Position
- Below the diagonal: org.apache.livy.thriftserver.operation uses a module listed above it, which is the healthy direction.
24→11 org.apache.livy.thriftserver.operation uses org.apache.livy.thriftserver.types✕
- Connections
- 8 pairs of types, where a type in org.apache.livy.thriftserver.operation uses a type in org.apache.livy.thriftserver.types.
- The types involved
org.apache.livy.thriftserver.operation.GetCatalogsOperation→org.apache.livy.thriftserver.types.Schemaorg.apache.livy.thriftserver.operation.GetColumnsOperation→org.apache.livy.thriftserver.types.Schemaorg.apache.livy.thriftserver.operation.GetFunctionsOperation→org.apache.livy.thriftserver.types.Schemaorg.apache.livy.thriftserver.operation.GetSchemasOperation→org.apache.livy.thriftserver.types.Schemaorg.apache.livy.thriftserver.operation.GetTableTypesOperation→org.apache.livy.thriftserver.types.Schemaorg.apache.livy.thriftserver.operation.GetTablesOperation→org.apache.livy.thriftserver.types.Schemaorg.apache.livy.thriftserver.operation.GetTypeInfoOperation→org.apache.livy.thriftserver.types.Schemaorg.apache.livy.thriftserver.operation.Operation→org.apache.livy.thriftserver.types.Schema
- Direction
- org.apache.livy.thriftserver.operation uses org.apache.livy.thriftserver.types, so a change to org.apache.livy.thriftserver.types can break org.apache.livy.thriftserver.operation, while a change to org.apache.livy.thriftserver.operation can't break org.apache.livy.thriftserver.types.
- Position
- Below the diagonal: org.apache.livy.thriftserver.operation uses a module listed above it, which is the healthy direction.
25→4 org.apache.livy.thriftserver.rpc uses org.apache.livy✕
- Connections
- 1 pair of types, where a type in org.apache.livy.thriftserver.rpc uses a type in org.apache.livy.
- The types involved
org.apache.livy.thriftserver.rpc.RpcClient→org.apache.livy.Logging
- Direction
- org.apache.livy.thriftserver.rpc uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.thriftserver.rpc, while a change to org.apache.livy.thriftserver.rpc can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.thriftserver.rpc uses a module listed above it, which is the healthy direction.
26→4 org.apache.livy.thriftserver.session uses org.apache.livy✕
- Connections
- 15 pairs of types, where a type in org.apache.livy.thriftserver.session uses a type in org.apache.livy.
- The types involved
org.apache.livy.thriftserver.session.CleanupStatementJob→org.apache.livy.Joborg.apache.livy.thriftserver.session.CleanupStatementJob→org.apache.livy.JobContextorg.apache.livy.thriftserver.session.FetchResultJob→org.apache.livy.Joborg.apache.livy.thriftserver.session.FetchResultJob→org.apache.livy.JobContextorg.apache.livy.thriftserver.session.FetchResultSchemaJob→org.apache.livy.Joborg.apache.livy.thriftserver.session.FetchResultSchemaJob→org.apache.livy.JobContextorg.apache.livy.thriftserver.session.RegisterSessionJob→org.apache.livy.Joborg.apache.livy.thriftserver.session.RegisterSessionJob→org.apache.livy.JobContextorg.apache.livy.thriftserver.session.SparkCatalogJob→org.apache.livy.Joborg.apache.livy.thriftserver.session.SparkCatalogJob→org.apache.livy.JobContextorg.apache.livy.thriftserver.session.SqlJob→org.apache.livy.Joborg.apache.livy.thriftserver.session.SqlJob→org.apache.livy.JobContextorg.apache.livy.thriftserver.session.ThriftSessionState→org.apache.livy.JobContextorg.apache.livy.thriftserver.session.UnregisterSessionJob→org.apache.livy.Joborg.apache.livy.thriftserver.session.UnregisterSessionJob→org.apache.livy.JobContext
- Direction
- org.apache.livy.thriftserver.session uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.thriftserver.session, while a change to org.apache.livy.thriftserver.session can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.thriftserver.session uses a module listed above it, which is the healthy direction.
27→4 org.apache.livy.utils uses org.apache.livy✕
- Connections
- 15 pairs of types, where a type in org.apache.livy.utils uses a type in org.apache.livy.
- The types involved
org.apache.livy.utils.KubernetesAppReport→org.apache.livy.LivyConforg.apache.livy.utils.KubernetesClientFactory→org.apache.livy.LivyConforg.apache.livy.utils.KubernetesExtensions→org.apache.livy.LivyConforg.apache.livy.utils.LineBufferedProcess→org.apache.livy.Loggingorg.apache.livy.utils.LineBufferedStream→org.apache.livy.Loggingorg.apache.livy.utils.LivySparkUtils→org.apache.livy.LivyConforg.apache.livy.utils.LivySparkUtils→org.apache.livy.Loggingorg.apache.livy.utils.SparkApp→org.apache.livy.LivyConforg.apache.livy.utils.SparkApp→org.apache.livy.Loggingorg.apache.livy.utils.SparkKubernetesApp→org.apache.livy.LivyConforg.apache.livy.utils.SparkKubernetesApp→org.apache.livy.Loggingorg.apache.livy.utils.SparkProcApp→org.apache.livy.Loggingorg.apache.livy.utils.SparkProcessBuilder→org.apache.livy.Loggingorg.apache.livy.utils.SparkYarnApp→org.apache.livy.LivyConforg.apache.livy.utils.SparkYarnApp→org.apache.livy.Logging
- Direction
- org.apache.livy.utils uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.utils, while a change to org.apache.livy.utils can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.utils uses a module listed above it, which is the healthy direction.
27→12 org.apache.livy.utils uses org.apache.livy.utils.SparkApp✕
- Connections
- 1 pair of types, where a type in org.apache.livy.utils uses a type in org.apache.livy.utils.SparkApp.
- The types involved
org.apache.livy.utils.SparkAppListener→org.apache.livy.utils.SparkApp.State
- Direction
- org.apache.livy.utils uses org.apache.livy.utils.SparkApp, so a change to org.apache.livy.utils.SparkApp can break org.apache.livy.utils, while a change to org.apache.livy.utils can't break org.apache.livy.utils.SparkApp.
- Position
- Below the diagonal: org.apache.livy.utils uses a module listed above it, which is the healthy direction.
28→4 org.apache.livy.client.http uses org.apache.livy✕
- Connections
- 6 pairs of types, where a type in org.apache.livy.client.http uses a type in org.apache.livy.
- The types involved
org.apache.livy.client.http.HttpClient→org.apache.livy.Joborg.apache.livy.client.http.HttpClient→org.apache.livy.JobHandleorg.apache.livy.client.http.HttpClient→org.apache.livy.LivyClientorg.apache.livy.client.http.HttpClientFactory→org.apache.livy.LivyClientorg.apache.livy.client.http.HttpClientFactory→org.apache.livy.LivyClientFactoryorg.apache.livy.client.http.JobHandleImpl→org.apache.livy.State
- Direction
- org.apache.livy.client.http uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.client.http, while a change to org.apache.livy.client.http can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.client.http uses a module listed above it, which is the healthy direction.
28→15 org.apache.livy.client.http uses org.apache.livy.client.common✕
- Connections
- 7 pairs of types, where a type in org.apache.livy.client.http uses a type in org.apache.livy.client.common.
- The types involved
org.apache.livy.client.http.DepConf→org.apache.livy.client.common.DeprecatedConforg.apache.livy.client.http.Entry→org.apache.livy.client.common.ConfEntryorg.apache.livy.client.http.HttpClient→org.apache.livy.client.common.Serializerorg.apache.livy.client.http.HttpConf→org.apache.livy.client.common.ClientConforg.apache.livy.client.http.HttpConf→org.apache.livy.client.common.DeprecatedConforg.apache.livy.client.http.JobHandleImpl→org.apache.livy.client.common.AbstractJobHandleorg.apache.livy.client.http.JobHandleImpl→org.apache.livy.client.common.Serializer
- Direction
- org.apache.livy.client.http uses org.apache.livy.client.common, so a change to org.apache.livy.client.common can break org.apache.livy.client.http, while a change to org.apache.livy.client.http can't break org.apache.livy.client.common.
- Position
- Below the diagonal: org.apache.livy.client.http uses a module listed above it, which is the healthy direction.
29→15 org.apache.livy.rsc.rpc uses org.apache.livy.client.common✕
- Connections
- 1 pair of types, where a type in org.apache.livy.rsc.rpc uses a type in org.apache.livy.client.common.
- The types involved
org.apache.livy.rsc.rpc.KryoMessageCodec→org.apache.livy.client.common.Serializer
- Direction
- org.apache.livy.rsc.rpc uses org.apache.livy.client.common, so a change to org.apache.livy.client.common can break org.apache.livy.rsc.rpc, while a change to org.apache.livy.rsc.rpc can't break org.apache.livy.client.common.
- Position
- Below the diagonal: org.apache.livy.rsc.rpc uses a module listed above it, which is the healthy direction.
29→35 org.apache.livy.rsc.rpc uses org.apache.livy.rsc part of a loop✕
- Connections
- 5 pairs of types, where a type in org.apache.livy.rsc.rpc uses a type in org.apache.livy.rsc.
- The types involved
org.apache.livy.rsc.rpc.Rpc→org.apache.livy.rsc.RSCConforg.apache.livy.rsc.rpc.RpcServer→org.apache.livy.rsc.RSCConforg.apache.livy.rsc.rpc.SaslClientHandler→org.apache.livy.rsc.RSCConforg.apache.livy.rsc.rpc.SaslHandler→org.apache.livy.rsc.RSCConforg.apache.livy.rsc.rpc.SaslServerHandler→org.apache.livy.rsc.RSCConf
- Direction
- org.apache.livy.rsc.rpc uses org.apache.livy.rsc, so a change to org.apache.livy.rsc can break org.apache.livy.rsc.rpc, while a change to org.apache.livy.rsc.rpc can't break org.apache.livy.rsc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→4 org.apache.livy.server.interactive uses org.apache.livy✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.server.interactive uses a type in org.apache.livy.
- The types involved
org.apache.livy.server.interactive.InteractiveSession→org.apache.livy.LivyConforg.apache.livy.server.interactive.InteractiveSession→org.apache.livy.Loggingorg.apache.livy.server.interactive.InteractiveSessionServlet→org.apache.livy.Logging
- Direction
- org.apache.livy.server.interactive uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.server.interactive, while a change to org.apache.livy.server.interactive can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.server.interactive uses a module listed above it, which is the healthy direction.
30→8 org.apache.livy.server.interactive uses org.apache.livy.sessions.Session✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.interactive uses a type in org.apache.livy.sessions.Session.
- The types involved
org.apache.livy.server.interactive.InteractiveRecoveryMetadata→org.apache.livy.sessions.Session.RecoveryMetadata
- Direction
- org.apache.livy.server.interactive uses org.apache.livy.sessions.Session, so a change to org.apache.livy.sessions.Session can break org.apache.livy.server.interactive, while a change to org.apache.livy.server.interactive can't break org.apache.livy.sessions.Session.
- Position
- Below the diagonal: org.apache.livy.server.interactive uses a module listed above it, which is the healthy direction.
30→20 org.apache.livy.server.interactive uses org.apache.livy.server.recovery✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.interactive uses a type in org.apache.livy.server.recovery.
- The types involved
org.apache.livy.server.interactive.InteractiveSession→org.apache.livy.server.recovery.SessionStore
- Direction
- org.apache.livy.server.interactive uses org.apache.livy.server.recovery, so a change to org.apache.livy.server.recovery can break org.apache.livy.server.interactive, while a change to org.apache.livy.server.interactive can't break org.apache.livy.server.recovery.
- Position
- Below the diagonal: org.apache.livy.server.interactive uses a module listed above it, which is the healthy direction.
30→27 org.apache.livy.server.interactive uses org.apache.livy.utils✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.interactive uses a type in org.apache.livy.utils.
- The types involved
org.apache.livy.server.interactive.InteractiveSession→org.apache.livy.utils.SparkApp
- Direction
- org.apache.livy.server.interactive uses org.apache.livy.utils, so a change to org.apache.livy.utils can break org.apache.livy.server.interactive, while a change to org.apache.livy.server.interactive can't break org.apache.livy.utils.
- Position
- Below the diagonal: org.apache.livy.server.interactive uses a module listed above it, which is the healthy direction.
30→34 org.apache.livy.server.interactive uses org.apache.livy.sessions part of a loop✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.server.interactive uses a type in org.apache.livy.sessions.
- The types involved
org.apache.livy.server.interactive.CreateInteractiveRequest→org.apache.livy.sessions.Kindorg.apache.livy.server.interactive.InteractiveRecoveryMetadata→org.apache.livy.sessions.Kindorg.apache.livy.server.interactive.InteractiveSession→org.apache.livy.sessions.Kind
- Direction
- org.apache.livy.server.interactive uses org.apache.livy.sessions, so a change to org.apache.livy.sessions can break org.apache.livy.server.interactive, while a change to org.apache.livy.server.interactive can't break org.apache.livy.sessions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→36 org.apache.livy.server.interactive uses org.apache.livy.server part of a loop✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.server.interactive uses a type in org.apache.livy.server.
- The types involved
org.apache.livy.server.interactive.InteractiveSession→org.apache.livy.server.AccessManagerorg.apache.livy.server.interactive.SessionHeartbeatNotifier→org.apache.livy.server.SessionServlet
- Direction
- org.apache.livy.server.interactive uses org.apache.livy.server, so a change to org.apache.livy.server can break org.apache.livy.server.interactive, while a change to org.apache.livy.server.interactive can't break org.apache.livy.server.
- 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.
31→4 org.apache.livy.thriftserver.auth uses org.apache.livy✕
- Connections
- 7 pairs of types, where a type in org.apache.livy.thriftserver.auth uses a type in org.apache.livy.
- The types involved
org.apache.livy.thriftserver.auth.AuthFactory→org.apache.livy.LivyConforg.apache.livy.thriftserver.auth.AuthFactory→org.apache.livy.Loggingorg.apache.livy.thriftserver.auth.AuthenticationProvider→org.apache.livy.LivyConforg.apache.livy.thriftserver.auth.LdapAuthenticationProviderImpl→org.apache.livy.LivyConforg.apache.livy.thriftserver.auth.LivyDelegationTokenSecretManager→org.apache.livy.LivyConforg.apache.livy.thriftserver.auth.SaslDigestCallbackHandler→org.apache.livy.Loggingorg.apache.livy.thriftserver.auth.TUGIAssumingProcessor→org.apache.livy.Logging
- Direction
- org.apache.livy.thriftserver.auth uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.thriftserver.auth, while a change to org.apache.livy.thriftserver.auth can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.thriftserver.auth uses a module listed above it, which is the healthy direction.
31→22 org.apache.livy.thriftserver.auth uses org.apache.livy.thriftserver.auth.ldap✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.thriftserver.auth uses a type in org.apache.livy.thriftserver.auth.ldap.
- The types involved
org.apache.livy.thriftserver.auth.LdapAuthenticationProviderImpl→org.apache.livy.thriftserver.auth.ldap.DirSearchFactoryorg.apache.livy.thriftserver.auth.LdapAuthenticationProviderImpl→org.apache.livy.thriftserver.auth.ldap.Filter
- Direction
- org.apache.livy.thriftserver.auth uses org.apache.livy.thriftserver.auth.ldap, so a change to org.apache.livy.thriftserver.auth.ldap can break org.apache.livy.thriftserver.auth, while a change to org.apache.livy.thriftserver.auth can't break org.apache.livy.thriftserver.auth.ldap.
- Position
- Below the diagonal: org.apache.livy.thriftserver.auth uses a module listed above it, which is the healthy direction.
31→23 org.apache.livy.thriftserver.auth uses org.apache.livy.thriftserver.cli✕
- Connections
- 1 pair of types, where a type in org.apache.livy.thriftserver.auth uses a type in org.apache.livy.thriftserver.cli.
- The types involved
org.apache.livy.thriftserver.auth.AuthFactory→org.apache.livy.thriftserver.cli.ThriftCLIService
- Direction
- org.apache.livy.thriftserver.auth uses org.apache.livy.thriftserver.cli, so a change to org.apache.livy.thriftserver.cli can break org.apache.livy.thriftserver.auth, while a change to org.apache.livy.thriftserver.auth can't break org.apache.livy.thriftserver.cli.
- Position
- Below the diagonal: org.apache.livy.thriftserver.auth uses a module listed above it, which is the healthy direction.
32→4 org.apache.livy.utils.KubernetesExtensions uses org.apache.livy✕
- Connections
- 1 pair of types, where a type in org.apache.livy.utils.KubernetesExtensions uses a type in org.apache.livy.
- The types involved
org.apache.livy.utils.KubernetesExtensions.KubernetesClientExtensions→org.apache.livy.LivyConf
- Direction
- org.apache.livy.utils.KubernetesExtensions uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.utils.KubernetesExtensions, while a change to org.apache.livy.utils.KubernetesExtensions can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.utils.KubernetesExtensions uses a module listed above it, which is the healthy direction.
32→27 org.apache.livy.utils.KubernetesExtensions uses org.apache.livy.utils✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.utils.KubernetesExtensions uses a type in org.apache.livy.utils.
- The types involved
org.apache.livy.utils.KubernetesExtensions.KubernetesClientExtensions→org.apache.livy.utils.KubernetesAppReportorg.apache.livy.utils.KubernetesExtensions.KubernetesClientExtensions→org.apache.livy.utils.KubernetesApplication
- Direction
- org.apache.livy.utils.KubernetesExtensions uses org.apache.livy.utils, so a change to org.apache.livy.utils can break org.apache.livy.utils.KubernetesExtensions, while a change to org.apache.livy.utils.KubernetesExtensions can't break org.apache.livy.utils.
- Position
- Below the diagonal: org.apache.livy.utils.KubernetesExtensions uses a module listed above it, which is the healthy direction.
33→4 org.apache.livy.rsc.driver uses org.apache.livy✕
- Connections
- 10 pairs of types, where a type in org.apache.livy.rsc.driver uses a type in org.apache.livy.
- The types involved
org.apache.livy.rsc.driver.AddFileJob→org.apache.livy.Joborg.apache.livy.rsc.driver.AddFileJob→org.apache.livy.JobContextorg.apache.livy.rsc.driver.AddJarJob→org.apache.livy.Joborg.apache.livy.rsc.driver.AddJarJob→org.apache.livy.JobContextorg.apache.livy.rsc.driver.BypassJob→org.apache.livy.Joborg.apache.livy.rsc.driver.BypassJob→org.apache.livy.JobContextorg.apache.livy.rsc.driver.BypassJobWrapper→org.apache.livy.Joborg.apache.livy.rsc.driver.BypassJobWrapper→org.apache.livy.Stateorg.apache.livy.rsc.driver.JobContextImpl→org.apache.livy.JobContextorg.apache.livy.rsc.driver.JobWrapper→org.apache.livy.Job
- Direction
- org.apache.livy.rsc.driver uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.rsc.driver, while a change to org.apache.livy.rsc.driver can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.rsc.driver uses a module listed above it, which is the healthy direction.
33→15 org.apache.livy.rsc.driver uses org.apache.livy.client.common✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.rsc.driver uses a type in org.apache.livy.client.common.
- The types involved
org.apache.livy.rsc.driver.BypassJob→org.apache.livy.client.common.Serializerorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.client.common.Serializer
- Direction
- org.apache.livy.rsc.driver uses org.apache.livy.client.common, so a change to org.apache.livy.client.common can break org.apache.livy.rsc.driver, while a change to org.apache.livy.rsc.driver can't break org.apache.livy.client.common.
- Position
- Below the diagonal: org.apache.livy.rsc.driver uses a module listed above it, which is the healthy direction.
33→29 org.apache.livy.rsc.driver uses org.apache.livy.rsc.rpc✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.rsc.driver uses a type in org.apache.livy.rsc.rpc.
- The types involved
org.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.rpc.Rpcorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.rpc.RpcServer
- Direction
- org.apache.livy.rsc.driver uses org.apache.livy.rsc.rpc, so a change to org.apache.livy.rsc.rpc can break org.apache.livy.rsc.driver, while a change to org.apache.livy.rsc.driver can't break org.apache.livy.rsc.rpc.
- Position
- Below the diagonal: org.apache.livy.rsc.driver uses a module listed above it, which is the healthy direction.
33→35 org.apache.livy.rsc.driver uses org.apache.livy.rsc part of a loop✕
- Connections
- 11 pairs of types, where a type in org.apache.livy.rsc.driver uses a type in org.apache.livy.rsc.
- The types involved
org.apache.livy.rsc.driver.2→org.apache.livy.rsc.FutureListenerorg.apache.livy.rsc.driver.BypassJobWrapper→org.apache.livy.rsc.BypassJobStatusorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.BaseProtocolorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.BypassJobRequestorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.BypassJobStatusorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.CancelJoborg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.EndSessionorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.GetBypassJobStatusorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.JobRequestorg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.RSCConforg.apache.livy.rsc.driver.RSCDriver→org.apache.livy.rsc.SyncJobRequest
- Direction
- org.apache.livy.rsc.driver uses org.apache.livy.rsc, so a change to org.apache.livy.rsc can break org.apache.livy.rsc.driver, while a change to org.apache.livy.rsc.driver can't break org.apache.livy.rsc.
- 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.
34→4 org.apache.livy.sessions uses org.apache.livy✕
- Connections
- 1 pair of types, where a type in org.apache.livy.sessions uses a type in org.apache.livy.
- The types involved
org.apache.livy.sessions.Session→org.apache.livy.LivyConf
- Direction
- org.apache.livy.sessions uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.sessions, while a change to org.apache.livy.sessions can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.sessions uses a module listed above it, which is the healthy direction.
34→30 org.apache.livy.sessions uses org.apache.livy.server.interactive✕
- Connections
- 1 pair of types, where a type in org.apache.livy.sessions uses a type in org.apache.livy.server.interactive.
- The types involved
org.apache.livy.sessions.InteractiveSessionManager→org.apache.livy.server.interactive.SessionHeartbeatWatchdog
- Direction
- org.apache.livy.sessions uses org.apache.livy.server.interactive, so a change to org.apache.livy.server.interactive can break org.apache.livy.sessions, while a change to org.apache.livy.sessions can't break org.apache.livy.server.interactive.
- Position
- Below the diagonal: org.apache.livy.sessions uses a module listed above it, which is the healthy direction.
35→4 org.apache.livy.rsc uses org.apache.livy✕
- Connections
- 12 pairs of types, where a type in org.apache.livy.rsc uses a type in org.apache.livy.
- The types involved
org.apache.livy.rsc.BypassJobStatus→org.apache.livy.Stateorg.apache.livy.rsc.ClientProtocol→org.apache.livy.Joborg.apache.livy.rsc.JobHandleImpl→org.apache.livy.Stateorg.apache.livy.rsc.JobRequest→org.apache.livy.Joborg.apache.livy.rsc.PingJob→org.apache.livy.Joborg.apache.livy.rsc.PingJob→org.apache.livy.JobContextorg.apache.livy.rsc.RSCClient→org.apache.livy.Joborg.apache.livy.rsc.RSCClient→org.apache.livy.JobHandleorg.apache.livy.rsc.RSCClient→org.apache.livy.LivyClientorg.apache.livy.rsc.RSCClientFactory→org.apache.livy.LivyClientorg.apache.livy.rsc.RSCClientFactory→org.apache.livy.LivyClientFactoryorg.apache.livy.rsc.SyncJobRequest→org.apache.livy.Job
- Direction
- org.apache.livy.rsc uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.rsc, while a change to org.apache.livy.rsc can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.rsc uses a module listed above it, which is the healthy direction.
35→15 org.apache.livy.rsc uses org.apache.livy.client.common✕
- Connections
- 5 pairs of types, where a type in org.apache.livy.rsc uses a type in org.apache.livy.client.common.
- The types involved
org.apache.livy.rsc.DepConf→org.apache.livy.client.common.DeprecatedConforg.apache.livy.rsc.Entry→org.apache.livy.client.common.ConfEntryorg.apache.livy.rsc.JobHandleImpl→org.apache.livy.client.common.AbstractJobHandleorg.apache.livy.rsc.RSCConf→org.apache.livy.client.common.ClientConforg.apache.livy.rsc.RSCConf→org.apache.livy.client.common.DeprecatedConf
- Direction
- org.apache.livy.rsc uses org.apache.livy.client.common, so a change to org.apache.livy.client.common can break org.apache.livy.rsc, while a change to org.apache.livy.rsc can't break org.apache.livy.client.common.
- Position
- Below the diagonal: org.apache.livy.rsc uses a module listed above it, which is the healthy direction.
35→29 org.apache.livy.rsc uses org.apache.livy.rsc.rpc✕
- Connections
- 7 pairs of types, where a type in org.apache.livy.rsc uses a type in org.apache.livy.rsc.rpc.
- The types involved
org.apache.livy.rsc.4→org.apache.livy.rsc.rpc.Rpcorg.apache.livy.rsc.BaseProtocol→org.apache.livy.rsc.rpc.RpcDispatcherorg.apache.livy.rsc.RSCClient→org.apache.livy.rsc.rpc.Rpcorg.apache.livy.rsc.RSCClientFactory→org.apache.livy.rsc.rpc.RpcServerorg.apache.livy.rsc.RegistrationHandler→org.apache.livy.rsc.rpc.ClientCallbackorg.apache.livy.rsc.RegistrationHandler→org.apache.livy.rsc.rpc.Rpcorg.apache.livy.rsc.RegistrationHandler→org.apache.livy.rsc.rpc.RpcDispatcher
- Direction
- org.apache.livy.rsc uses org.apache.livy.rsc.rpc, so a change to org.apache.livy.rsc.rpc can break org.apache.livy.rsc, while a change to org.apache.livy.rsc can't break org.apache.livy.rsc.rpc.
- Position
- Below the diagonal: org.apache.livy.rsc uses a module listed above it, which is the healthy direction.
35→33 org.apache.livy.rsc uses org.apache.livy.rsc.driver✕
- Connections
- 1 pair of types, where a type in org.apache.livy.rsc uses a type in org.apache.livy.rsc.driver.
- The types involved
org.apache.livy.rsc.ReplJobResults→org.apache.livy.rsc.driver.Statement
- Direction
- org.apache.livy.rsc uses org.apache.livy.rsc.driver, so a change to org.apache.livy.rsc.driver can break org.apache.livy.rsc, while a change to org.apache.livy.rsc can't break org.apache.livy.rsc.driver.
- Position
- Below the diagonal: org.apache.livy.rsc uses a module listed above it, which is the healthy direction.
36→4 org.apache.livy.server uses org.apache.livy✕
- Connections
- 6 pairs of types, where a type in org.apache.livy.server uses a type in org.apache.livy.
- The types involved
org.apache.livy.server.AccessManager→org.apache.livy.Loggingorg.apache.livy.server.LivyServer→org.apache.livy.LivyConforg.apache.livy.server.LivyServer→org.apache.livy.Loggingorg.apache.livy.server.SessionServlet→org.apache.livy.Loggingorg.apache.livy.server.ThriftServerFactory→org.apache.livy.LivyConforg.apache.livy.server.WebServer→org.apache.livy.Logging
- Direction
- org.apache.livy.server uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.server, while a change to org.apache.livy.server can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.server uses a module listed above it, which is the healthy direction.
36→20 org.apache.livy.server uses org.apache.livy.server.recovery✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.server uses a type in org.apache.livy.server.recovery.
- The types involved
org.apache.livy.server.LivyServer→org.apache.livy.server.recovery.ZooKeeperManagerorg.apache.livy.server.ThriftServerFactory→org.apache.livy.server.recovery.SessionStore
- Direction
- org.apache.livy.server uses org.apache.livy.server.recovery, so a change to org.apache.livy.server.recovery can break org.apache.livy.server, while a change to org.apache.livy.server can't break org.apache.livy.server.recovery.
- Position
- Below the diagonal: org.apache.livy.server uses a module listed above it, which is the healthy direction.
36→22 org.apache.livy.server uses org.apache.livy.thriftserver.auth.ldap✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.server uses a type in org.apache.livy.thriftserver.auth.ldap.
- The types involved
org.apache.livy.server.AccessFilter→org.apache.livy.thriftserver.auth.ldap.Filterorg.apache.livy.server.CsrfFilter→org.apache.livy.thriftserver.auth.ldap.Filterorg.apache.livy.server.SecurityHeadersFilter→org.apache.livy.thriftserver.auth.ldap.Filter
- Direction
- org.apache.livy.server uses org.apache.livy.thriftserver.auth.ldap, so a change to org.apache.livy.thriftserver.auth.ldap can break org.apache.livy.server, while a change to org.apache.livy.server can't break org.apache.livy.thriftserver.auth.ldap.
- Position
- Below the diagonal: org.apache.livy.server uses a module listed above it, which is the healthy direction.
36→34 org.apache.livy.server uses org.apache.livy.sessions✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.server uses a type in org.apache.livy.sessions.
- The types involved
org.apache.livy.server.LivySessionMetrics→org.apache.livy.sessions.BatchSessionManagerorg.apache.livy.server.LivySessionMetrics→org.apache.livy.sessions.InteractiveSessionManagerorg.apache.livy.server.ThriftServerFactory→org.apache.livy.sessions.InteractiveSessionManager
- Direction
- org.apache.livy.server uses org.apache.livy.sessions, so a change to org.apache.livy.sessions can break org.apache.livy.server, while a change to org.apache.livy.server can't break org.apache.livy.sessions.
- Position
- Below the diagonal: org.apache.livy.server uses a module listed above it, which is the healthy direction.
37→34 org.apache.livy.sessions.SessionState uses org.apache.livy.sessions✕
- Connections
- 11 pairs of types, where a type in org.apache.livy.sessions.SessionState uses a type in org.apache.livy.sessions.
- The types involved
org.apache.livy.sessions.SessionState.Busy→org.apache.livy.sessions.SessionStateorg.apache.livy.sessions.SessionState.Dead→org.apache.livy.sessions.FinishedSessionStateorg.apache.livy.sessions.SessionState.Error→org.apache.livy.sessions.FinishedSessionStateorg.apache.livy.sessions.SessionState.Idle→org.apache.livy.sessions.SessionStateorg.apache.livy.sessions.SessionState.Killed→org.apache.livy.sessions.FinishedSessionStateorg.apache.livy.sessions.SessionState.NotStarted→org.apache.livy.sessions.SessionStateorg.apache.livy.sessions.SessionState.Recovering→org.apache.livy.sessions.SessionStateorg.apache.livy.sessions.SessionState.Running→org.apache.livy.sessions.SessionStateorg.apache.livy.sessions.SessionState.ShuttingDown→org.apache.livy.sessions.SessionStateorg.apache.livy.sessions.SessionState.Starting→org.apache.livy.sessions.SessionStateorg.apache.livy.sessions.SessionState.Success→org.apache.livy.sessions.FinishedSessionState
- Direction
- org.apache.livy.sessions.SessionState uses org.apache.livy.sessions, so a change to org.apache.livy.sessions can break org.apache.livy.sessions.SessionState, while a change to org.apache.livy.sessions.SessionState can't break org.apache.livy.sessions.
- Position
- Below the diagonal: org.apache.livy.sessions.SessionState uses a module listed above it, which is the healthy direction.
38→4 org.apache.livy.server.batch uses org.apache.livy✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.server.batch uses a type in org.apache.livy.
- The types involved
org.apache.livy.server.batch.BatchSession→org.apache.livy.LivyConforg.apache.livy.server.batch.BatchSession→org.apache.livy.Logging
- Direction
- org.apache.livy.server.batch uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.server.batch, while a change to org.apache.livy.server.batch can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.server.batch uses a module listed above it, which is the healthy direction.
38→8 org.apache.livy.server.batch uses org.apache.livy.sessions.Session✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.batch uses a type in org.apache.livy.sessions.Session.
- The types involved
org.apache.livy.server.batch.BatchRecoveryMetadata→org.apache.livy.sessions.Session.RecoveryMetadata
- Direction
- org.apache.livy.server.batch uses org.apache.livy.sessions.Session, so a change to org.apache.livy.sessions.Session can break org.apache.livy.server.batch, while a change to org.apache.livy.server.batch can't break org.apache.livy.sessions.Session.
- Position
- Below the diagonal: org.apache.livy.server.batch uses a module listed above it, which is the healthy direction.
38→20 org.apache.livy.server.batch uses org.apache.livy.server.recovery✕
- Connections
- 1 pair of types, where a type in org.apache.livy.server.batch uses a type in org.apache.livy.server.recovery.
- The types involved
org.apache.livy.server.batch.BatchSession→org.apache.livy.server.recovery.SessionStore
- Direction
- org.apache.livy.server.batch uses org.apache.livy.server.recovery, so a change to org.apache.livy.server.recovery can break org.apache.livy.server.batch, while a change to org.apache.livy.server.batch can't break org.apache.livy.server.recovery.
- Position
- Below the diagonal: org.apache.livy.server.batch uses a module listed above it, which is the healthy direction.
38→27 org.apache.livy.server.batch uses org.apache.livy.utils✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.server.batch uses a type in org.apache.livy.utils.
- The types involved
org.apache.livy.server.batch.BatchSession→org.apache.livy.utils.SparkApporg.apache.livy.server.batch.BatchSessionView→org.apache.livy.utils.AppInfo
- Direction
- org.apache.livy.server.batch uses org.apache.livy.utils, so a change to org.apache.livy.utils can break org.apache.livy.server.batch, while a change to org.apache.livy.server.batch can't break org.apache.livy.utils.
- Position
- Below the diagonal: org.apache.livy.server.batch uses a module listed above it, which is the healthy direction.
38→36 org.apache.livy.server.batch uses org.apache.livy.server✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.server.batch uses a type in org.apache.livy.server.
- The types involved
org.apache.livy.server.batch.BatchSession→org.apache.livy.server.AccessManagerorg.apache.livy.server.batch.BatchSessionServlet→org.apache.livy.server.SessionServlet
- Direction
- org.apache.livy.server.batch uses org.apache.livy.server, so a change to org.apache.livy.server can break org.apache.livy.server.batch, while a change to org.apache.livy.server.batch can't break org.apache.livy.server.
- Position
- Below the diagonal: org.apache.livy.server.batch uses a module listed above it, which is the healthy direction.
39→4 org.apache.livy.thriftserver uses org.apache.livy✕
- Connections
- 12 pairs of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.
- The types involved
org.apache.livy.thriftserver.LivyCLIService→org.apache.livy.LivyConforg.apache.livy.thriftserver.LivyCLIService→org.apache.livy.Loggingorg.apache.livy.thriftserver.LivyExecuteStatementOperation→org.apache.livy.Loggingorg.apache.livy.thriftserver.LivyOperationManager→org.apache.livy.Loggingorg.apache.livy.thriftserver.LivyThriftServer→org.apache.livy.LivyConforg.apache.livy.thriftserver.LivyThriftServer→org.apache.livy.Loggingorg.apache.livy.thriftserver.LivyThriftSessionManager→org.apache.livy.LivyConforg.apache.livy.thriftserver.LivyThriftSessionManager→org.apache.livy.Loggingorg.apache.livy.thriftserver.ThriftServerAudit→org.apache.livy.Loggingorg.apache.livy.thriftserver.ThriftServerFactoryImpl→org.apache.livy.LivyConforg.apache.livy.thriftserver.ThriftService→org.apache.livy.LivyConforg.apache.livy.thriftserver.ThriftService→org.apache.livy.Logging
- Direction
- org.apache.livy.thriftserver uses org.apache.livy, so a change to org.apache.livy can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
39→10 org.apache.livy.thriftserver uses org.apache.livy.thriftserver.serde✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.thriftserver.serde.
- The types involved
org.apache.livy.thriftserver.LivyCLIService→org.apache.livy.thriftserver.serde.ThriftResultSetorg.apache.livy.thriftserver.LivyExecuteStatementOperation→org.apache.livy.thriftserver.serde.ThriftResultSetorg.apache.livy.thriftserver.LivyOperationManager→org.apache.livy.thriftserver.serde.ThriftResultSet
- Direction
- org.apache.livy.thriftserver uses org.apache.livy.thriftserver.serde, so a change to org.apache.livy.thriftserver.serde can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.thriftserver.serde.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
39→11 org.apache.livy.thriftserver uses org.apache.livy.thriftserver.types✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.thriftserver.types.
- The types involved
org.apache.livy.thriftserver.LivyCLIService→org.apache.livy.thriftserver.types.Schemaorg.apache.livy.thriftserver.LivyExecuteStatementOperation→org.apache.livy.thriftserver.types.Schema
- Direction
- org.apache.livy.thriftserver uses org.apache.livy.thriftserver.types, so a change to org.apache.livy.thriftserver.types can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.thriftserver.types.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
39→20 org.apache.livy.thriftserver uses org.apache.livy.server.recovery✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.server.recovery.
- The types involved
org.apache.livy.thriftserver.LivyThriftServer→org.apache.livy.server.recovery.SessionStoreorg.apache.livy.thriftserver.ThriftServerFactoryImpl→org.apache.livy.server.recovery.SessionStore
- Direction
- org.apache.livy.thriftserver uses org.apache.livy.server.recovery, so a change to org.apache.livy.server.recovery can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.server.recovery.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
39→24 org.apache.livy.thriftserver uses org.apache.livy.thriftserver.operation✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.thriftserver.operation.
- The types involved
org.apache.livy.thriftserver.LivyCLIService→org.apache.livy.thriftserver.operation.OperationStatusorg.apache.livy.thriftserver.LivyExecuteStatementOperation→org.apache.livy.thriftserver.operation.Operationorg.apache.livy.thriftserver.LivyOperationManager→org.apache.livy.thriftserver.operation.Operation
- Direction
- org.apache.livy.thriftserver uses org.apache.livy.thriftserver.operation, so a change to org.apache.livy.thriftserver.operation can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.thriftserver.operation.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
39→30 org.apache.livy.thriftserver uses org.apache.livy.server.interactive✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.server.interactive.
- The types involved
org.apache.livy.thriftserver.LivyThriftSessionManager→org.apache.livy.server.interactive.InteractiveSessionorg.apache.livy.thriftserver.ThriftSessionCreationException→org.apache.livy.server.interactive.InteractiveSession
- Direction
- org.apache.livy.thriftserver uses org.apache.livy.server.interactive, so a change to org.apache.livy.server.interactive can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.server.interactive.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
39→31 org.apache.livy.thriftserver uses org.apache.livy.thriftserver.auth✕
- Connections
- 1 pair of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.thriftserver.auth.
- The types involved
org.apache.livy.thriftserver.LivyCLIService→org.apache.livy.thriftserver.auth.AuthFactory
- Direction
- org.apache.livy.thriftserver uses org.apache.livy.thriftserver.auth, so a change to org.apache.livy.thriftserver.auth can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.thriftserver.auth.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
39→34 org.apache.livy.thriftserver uses org.apache.livy.sessions✕
- Connections
- 2 pairs of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.sessions.
- The types involved
org.apache.livy.thriftserver.LivyThriftServer→org.apache.livy.sessions.InteractiveSessionManagerorg.apache.livy.thriftserver.ThriftServerFactoryImpl→org.apache.livy.sessions.InteractiveSessionManager
- Direction
- org.apache.livy.thriftserver uses org.apache.livy.sessions, so a change to org.apache.livy.sessions can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.sessions.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
39→36 org.apache.livy.thriftserver uses org.apache.livy.server✕
- Connections
- 3 pairs of types, where a type in org.apache.livy.thriftserver uses a type in org.apache.livy.server.
- The types involved
org.apache.livy.thriftserver.LivyThriftServer→org.apache.livy.server.AccessManagerorg.apache.livy.thriftserver.ThriftServerFactoryImpl→org.apache.livy.server.AccessManagerorg.apache.livy.thriftserver.ThriftServerFactoryImpl→org.apache.livy.server.ThriftServerFactory
- Direction
- org.apache.livy.thriftserver uses org.apache.livy.server, so a change to org.apache.livy.server can break org.apache.livy.thriftserver, while a change to org.apache.livy.thriftserver can't break org.apache.livy.server.
- Position
- Below the diagonal: org.apache.livy.thriftserver uses a module listed above it, which is the healthy direction.
40→36 org.apache.livy.thriftserver.ui uses org.apache.livy.server✕
- Connections
- 1 pair of types, where a type in org.apache.livy.thriftserver.ui uses a type in org.apache.livy.server.
- The types involved
org.apache.livy.thriftserver.ui.ThriftJsonServlet→org.apache.livy.server.JsonServlet
- Direction
- org.apache.livy.thriftserver.ui uses org.apache.livy.server, so a change to org.apache.livy.server can break org.apache.livy.thriftserver.ui, while a change to org.apache.livy.thriftserver.ui can't break org.apache.livy.server.
- Position
- Below the diagonal: org.apache.livy.thriftserver.ui uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 66 | High / Critical |
| A05:2025 — Injection | 17 | High / Critical |
| A02:2025 — Security Misconfiguration | 17 | High / Critical |
Roadmap
First, address visual and motion safety by ensuring visible focus styles, respecting reduced motion preferences, and fixing low-contrast colors. Next, enforce accessibility standards by integrating automated checks into the UI test suite and gating merges on CI. Simultaneously, improve type safety by adopting TypeScript for the frontend and enabling strict null checking in Scala to prevent runtime errors. Finally, resolve the missing architectural decision records to ensure proper documentation of system changes.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +4.1 pts | Medium | Visual & motion safety |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.8 pts | Low | ADR Quality |
| Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge. | +3.5 pts | Medium | A11y enforcement |
| 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. | +3.0 pts | Medium | Type Safety |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +2.5 pts | Medium | Nullable reference types |
| Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off. | +1.4 pts | Medium | Web-Security Posture |
| 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. | +1.4 pts | Medium | Architecture documentation |
| Resolve the 89 Orphaned file finding(s) in Knowledge Freshness — start with JobHandleImpl.java (2), LivyCLIService.scala, REDACTED. | +1.2 pts | Medium | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| server/src/main/scala/org/apache/livy/server/LivyServer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| rsc/src/main/java/org/apache/livy/rsc/RSCClient.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| client-http/src/main/java/org/apache/livy/client/http/JobHandleImpl.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| docs/assets/themes/apache/bootstrap/js/bootstrap.js | 7.0 | Near-clean | Cyclomatic Complexity: bootstrap.Tooltip.show (cyclomatic 22) |
| REDACTED | 7.1 | Near-clean | Cognitive Complexity: merge_livy_pr.resolve_jira_issue (cognitive 21) |
| thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala | 7.1 | Near-clean | Cyclomatic Complexity: LivyThriftSessionManager.processSessionConf (cyclomatic 17) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 79 of 79 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 79 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, 319 of 340 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java, .scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java, .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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a 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.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `server/src/main/scala/org/apache/livy/server/ui/UIServlet.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.
- D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Dev/helmchart/templates/statefulset.yaml:19, REDACTED:118 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — spark-worker-1 Pulling spark-master Pulling livy Pulling livy Error Get "https://registry-1.docker.io/v2/": Forbidden spark-master Error context canceled spark-worker-1 Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: spark-worker-1 Skipped - Image is already being pulled by spark-master livy Pulling spark-master Pulling spark-master Error Get "https://registry-1.docker.io/v2/": Forbidden livy Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned 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.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- 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.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was InteractiveSession.prepareBuilderProp at 27.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with InteractiveSession.prepareBuilderProp (cyclomatic 27), bootstrap.Tooltip.show (cyclomatic 22), LivyServer.start (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
32 method(s) exceeded the cognitive complexity threshold of 15; the worst was InteractiveSession.prepareBuilderProp at 42.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with InteractiveSession.prepareBuilderProp (cognitive 42). — Refactoring it lifts Cognitive Complexity from 6.9 to about 7.3/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with bootstrap.js, SparkKubernetesApp.scala, ThriftCLIService.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with LivyCLIService.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
3 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with LivyThriftSessionManager.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7–8 lines × 2) finding(s) in Code Duplication — start with GetColumnsJob.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SparkEntries.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
15 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 9 of the 15 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
2 of 51 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with PythonInterpreter.scala, SessionServlet.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
493 test methods: 462 unit, 31 integration, 0 BDD, 0 e2e. The Python suite contributes 21 test function(s) across 2 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Scala suite contributes 399 test case(s) across 53 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D12 · Dependency Hygiene
2 outdated direct gem(s), 0 pinning defect(s). 3 declaration(s) graded against rubygems.org, 3 of them against a version resolved in a committed Gemfile.lock. 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 77 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 77 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ 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
Top hotspots: server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala (7×15=105); server/src/main/scala/org/apache/livy/server/LivyServer.scala (4×21=84)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with SparkKubernetesApp.scala, LivyServer.scala. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpServlet.scala. Counted over 53 of the 183 production source files in this repository: 64 are under the ~2,400-byte size floor this dimension measures over, and the remaining 66 have no attributable history left to measure.
D17 · Explicit Debt
18 deducted task-comment markers across 25195 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 17 TodoComment finding(s) in Explicit Debt — start with LivyCLIService.scala (2), Operation.scala, ThriftCLIService.scala. — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with HttpClientSpec.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 8 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 15 build units (Bundler, Maven) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
17 finding(s): 0 critical, 13 high, 3 medium, 1 low. 8 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 15 file(s) — `bin/livy-server` (lines 161–200), `dev/helmchart/templates/certificate-default.yaml`, `dev/helmchart/templates/clusterissuers.yaml`, `dev/helmchart/templates/config.yaml`, `dev/helmchart/templates/ingress.yaml`, … (+10 more) — 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, REDACTED. — 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 issue-level).
- No action in Static Analysis (SAST) — all 8 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
59 finding(s): 8 critical, 34 high, 16 medium, 1 low.
What to do
- Resolve the 34 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (34). — One of this dimension's main actionable groups (34 issue-level).
- Resolve the 16 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (16). — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
D31 · IaC & Container Security
17 finding(s): 0 critical, 3 high, 14 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 14 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (13), REDACTED. — One of this dimension's main actionable groups (14 warning-level).
D34 · Knowledge Freshness
92 of 119 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala. Counted over 119 of the 183 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 89 Orphaned file finding(s) in Knowledge Freshness — start with JobHandleImpl.java (2), LivyCLIService.scala, REDACTED. — One of this dimension's main actionable groups (89 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ThriftCLIService.scala, LivyThriftSessionManager.scala, Rpc.java. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
No workload manifest could be read as a pod spec, so no confinement was judged.
What to do
- Improve Kernel & Syscall Confinement — currently 6.0/10. — No workload manifest could be read as a pod spec, so no confinement was judged.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 40 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
AC3 · Page structure
AC6 · Visual & motion safety
- `.navbar-inverse .navbar-nav > li > a` sets color: #ffffff on background-color: #339999 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/assets/themes/apache/css/style.css:46
- `.dropdown-menu > .active > a, .dropdown-menu > .active > a:hover, .dropdown-menu > .active > a:focus` sets color: #ffffff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:3531
- `.navbar :focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/assets/themes/apache/css/style.css:125
- `.btn.active` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:2275
- `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:3476
- `.dropdown-menu > .active > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:3535
- `.open > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:3558
- `.btn-group > .btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:3654
- `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:3735
- `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:6026
- `.collapsing` moves (`transition: height 0.35s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:2634
- `.progress-bar` moves (`transition: width 0.6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:5450
- `.progress.active .progress-bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:5463
- `.modal.fade .modal-dialog` moves (`transition: transform 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:6002
- `.carousel-inner > .item` moves (`transition: 0.6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/assets/themes/apache/bootstrap/css/bootstrap.css:6389
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
- `getDelegationToken` is a shipped member whose whole body is still a "not implemented" error, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:357
- `setApplicationName` is a shipped member whose whole body is still a "not implemented" error, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:366
- `cancelDelegationToken` is a shipped member whose whole body is still a "not implemented" error, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:370
- `renewDelegationToken` is a shipped member whose whole body is still a "not implemented" error, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:377
- `getQueryId` is a shipped member whose whole body is still a "not implemented" error, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:385
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `getDelegationToken` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:357
- `setApplicationName` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:366
- `cancelDelegationToken` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:370
- `renewDelegationToken` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:377
- `getQueryId` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:385
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — integration-test/src/test/scala/org/apache/livy/test/JobApiIT.scala:138
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 23 of 23 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 5/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `server`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 41 use(s) across 26,538 production line(s) (~1.5/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 5 plain JS — the untyped files are server/src/main/resources/org/apache/livy/server/ui/static/js/all-sessions.js, server/src/main/resources/org/apache/livy/server/ui/static/js/livy-ui.js, server/src/main/resources/org/apache/livy/server/ui/static/js/session-log.js, server/src/main/resources/org/apache/livy/server/ui/static/js/session.js, thriftserver/server/src/main/resources/org/apache/livy/server/ui/static/js/thrift-sessions.js.
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
R2 · Cyclomatic Complexity
R3 · Large Files
R7 · Dead Code
R9 · Circular Imports
S1 · Web-Security Posture
- a `HostnameVerifier` whose `verify` returns `true` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on. — server/src/main/scala/org/apache/livy/server/auth/LdapAuthenticationHandlerImpl.scala:157
- This repository's Scala server sets cookies (thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpServlet.scala:149 — `SET-COOKIE` header) and no `httpOnly`, `secure` or `sameSite` flag is switched on anywhere, nor are its cookies Play's, which are HttpOnly by default. (−1.5 on this card.)
What to do
- Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off.
- Flag the cookies the server sets: `HttpCookie(…, secure = true, httpOnly = true)` with `.withSameSite(…)` in akka/pekko-http, `ResponseCookie(…, secure = true, httpOnly = true, sameSite = Some(SameSite.Lax))` in http4s, or Play's `play.http.session.secure = true` — on every session and auth cookie.
X1 · Async correctness
- The `Future` this starts is not kept anywhere, and `scala.concurrent.Future` never reports a failure on its own: `Future { … }` catches any non-fatal exception its body throws and stores it as the future's `Failure` — not rethrown, not printed, not passed to the `ExecutionContext`'s `reportFailure` — so once nobody holds the future the error is gone, and nothing can wait for the work to finish either. Keep the future and compose it into what the caller returns (`for`/`flatMap`, `Future.sequence`), or, for genuine fire-and-forget, attach a handler that reports the failure — `Future { … }.failed.foreach(error => log.error("…", error))` or `.onComplete { case Failure(e) => report(e); case _ => }` — or catch and report inside the body itself. — repl/src/main/scala/org/apache/livy/repl/Session.scala:163
What to do
- Future started here is not kept
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `LivyServer` declares `stop` — it has told its callers it holds something worth ending — and it creates `executor` itself (line 109, `Executors.newScheduledThreadPool(…)`), which makes that instance its own. Nothing in the file releases it — no `executor.shutdown()`, on any path — and it is private and never handed on as a value (passed, returned, stored, or read through another instance), so no other owner can be releasing it. On what was read, `stop` ends the object and leaves what `Executors.newScheduledThreadPool(…)` holds — a file descriptor, a socket, a pool's live threads — open until the collector happens to reach it, one per instance. Release it in `stop` (`executor.shutdown()`), or, if it truly does not need releasing, drop the `stop` so the claim and the behaviour agree. — server/src/main/scala/org/apache/livy/server/LivyServer.scala:109
- `Files.newDirectoryStream(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.newDirectoryStream(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:89
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThreadPoolExecutorWithOomHook.scala:48, server/src/main/scala/org/apache/livy/server/recovery/FileSystemStateStore.scala:107, REDACTED:170, …
- `case NonFatal(e)` 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. — server/src/main/scala/org/apache/livy/package.scala:54
- `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — server/src/main/scala/org/apache/livy/server/LivySessionMetrics.scala:57, repl/scala-2.13/src/main/scala/org/apache/livy/repl/SparkInterpreter.scala:144
- `except` 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. — REDACTED:154
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 247 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:247
- `warn` at line 301 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:301
- `debug` at line 318 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:318
- `warn` at line 334 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:334
- `debug` at line 380 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:380
- `info` at line 382 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:382
- `debug` at line 97 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:97
- `info` at line 105 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:105
- `error` at line 126 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:126
- `error` at line 129 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:129
- `info` at line 70 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/driver/JobWrapper.java:70
- `warn` at line 283 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:283
- `warn` at line 319 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:319
- `warn` at line 520 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:520
- `warn` at line 225 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — client-common/src/main/java/org/apache/livy/client/common/ClientConf.java:225
- `warn` at line 233 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — client-common/src/main/java/org/apache/livy/client/common/ClientConf.java:233
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 106 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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 42% | Weak — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 54% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 52% | Adequate — gated by D29, D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 42% | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 82% | Strong | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 48 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — spark-worker-1 Pulling spark-master Pulling livy Pulling livy Error Get "https://registry-1.docker.io/v2/": Forbidden spark-master Error context canceled spark-worker-1 Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: spark-worker-1 Skipped - Image is already being pulled by spark-master livy Pulling spark-master Pulling spark-master Error Get "https://registry-1.docker.io/v2/": Forbidden livy Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~14110 lines of test source are present (.java, .scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .scala test runner
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, JavaScript, Python, Scala not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .py, .rb, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- 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): 36 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
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python, Ruby source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (5 production file(s)) has no JavaScript/TypeScript test, but it is 7.23% of this repository's production source and the other 92.77% carries 14,110 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- 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
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby, Scala, Java and Python were read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter; a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 59 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TLS certificate validation disabled server/src/main/scala/org/apache/livy/server/auth/LdapAuthenticationHandlerImpl.scala:157
Serious — 148 finding(s)
- TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:266
- TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:279
- TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/operation/Operation.scala:63
- TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:225
- TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpCLIService.scala:148
- TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthFactory.scala:80
- TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthenticationProvider.scala:28
- TodoComment server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:420
- TodoComment server/src/main/scala/org/apache/livy/utils/SparkYarnApp.scala:276
- TodoComment server/src/main/scala/org/apache/livy/server/LivyServer.scala:96
- TodoComment server/src/main/scala/org/apache/livy/server/recovery/ZooKeeperManager.scala:149
- TodoComment server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala:663
- TodoComment rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:408
- TodoComment rsc/src/main/java/org/apache/livy/rsc/RSCConf.java:116
- TodoComment integration-test/src/test/scala/org/apache/livy/test/InteractiveIT.scala:77
- TodoComment integration-test/src/main/scala/org/apache/livy/test/framework/LivyRestClient.scala:50
- TodoComment client-http/src/main/java/org/apache/livy/client/http/JobHandleImpl.java:244
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/css/style.css:125
- Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:2275
- Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3476
- Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3535
- Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3558
- Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3654
- Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3735
- Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:6026
- Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:2634
- Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:5450
- Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:5463
- Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:6002
- Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:6389
- Unfinished stub — body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:357
- Unfinished stub — body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:366
- Unfinished stub — body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:370
- Unfinished stub — body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:377
- Unfinished stub — body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:385
- Unfinished stub — throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:357
- Unfinished stub — throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:366
- Unfinished stub — throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:370
- Unfinished stub — throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:377
- Unfinished stub — throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:385
- FileTooLong: js/bootstrap.js docs/assets/themes/apache/bootstrap/js/bootstrap.js
- FileTooLong: utils/SparkKubernetesApp.scala server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala
- FileTooLong: cli/ThriftCLIService.scala thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala
- FileTooLong: interactive/InteractiveSession.scala server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala
- Swallowed exception (empty catch) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThreadPoolExecutorWithOomHook.scala:48
- Swallowed exception (empty catch) server/src/main/scala/org/apache/livy/server/recovery/FileSystemStateStore.scala:107
- Swallowed exception (empty catch) REDACTED:170
- Swallowed exception (empty catch) client-http/src/main/java/org/apache/livy/client/http/HttpClient.java:122
- Swallowed exception (caught, then discarded) server/src/main/scala/org/apache/livy/package.scala:54
- Swallowed exception (caught, then discarded) server/src/main/scala/org/apache/livy/server/LivySessionMetrics.scala:57
- Swallowed exception (caught, then discarded) REDACTED:154
- Swallowed exception (caught, then discarded) repl/scala-2.13/src/main/scala/org/apache/livy/repl/SparkInterpreter.scala:144
- Hotspot: server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:350
- Hotspot: server/src/main/scala/org/apache/livy/server/LivyServer.scala server/src/main/scala/org/apache/livy/server/LivyServer.scala:67
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: PythonInterpreter (LCOM4 5) repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:217
- Low cohesion: SessionServlet (LCOM4 4) server/src/main/scala/org/apache/livy/server/SessionServlet.scala:42
- Low contrast colour pair in CSS (3.4:1) docs/assets/themes/apache/css/style.css:46
- Low contrast colour pair in CSS (3.6:1) docs/assets/themes/apache/bootstrap/css/bootstrap.css:3531
- Accessibility enforcement below the top rung
- InteractiveSession.prepareBuilderProp (cyclomatic 27) server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala:211
- bootstrap.Tooltip.show (cyclomatic 22) docs/assets/themes/apache/bootstrap/js/bootstrap.js:1211
- LivyServer.start (cyclomatic 21) server/src/main/scala/org/apache/livy/server/LivyServer.scala:67
- ColumnBuffer.ensureCapacity (cyclomatic 19) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:359
- ColumnBuffer.getValues (cyclomatic 18) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:212
- AbstractSparkInterpreter.executeLines (cyclomatic 17) repl/src/main/scala/org/apache/livy/repl/AbstractSparkInterpreter.scala:255
- LivyThriftSessionManager.processSessionConf (cyclomatic 17) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:594
- SparkUtils.toJavaSQLType (cyclomatic 17) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/SparkUtils.java:113
- ThriftHttpServlet.doPost (cyclomatic 16) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpServlet.scala:76
- bootstrap.Affix.checkPosition (cyclomatic 16) docs/assets/themes/apache/bootstrap/js/bootstrap.js:1925
- HackComment client-http/src/test/scala/org/apache/livy/client/http/HttpClientSpec.scala:256
- InteractiveSession.prepareBuilderProp (cognitive 42) server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala:211
- AbstractSparkInterpreter.executeLines (cognitive 30) repl/src/main/scala/org/apache/livy/repl/AbstractSparkInterpreter.scala:255
- SessionManager.collectGarbage (cognitive 29) server/src/main/scala/org/apache/livy/sessions/SessionManager.scala:171
- bootstrap.Tooltip.show (cognitive 29) docs/assets/themes/apache/bootstrap/js/bootstrap.js:1211
- CreateInteractiveRequest.toString (cognitive 28) server/src/main/scala/org/apache/livy/server/interactive/CreateInteractiveRequest.scala:41
- CreateBatchRequest.toString (cognitive 26) server/src/main/scala/org/apache/livy/server/batch/CreateBatchRequest.scala:39
- ThriftHttpServlet.doPost (cognitive 26) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpServlet.scala:76
- GetColumnsJob.fetchCatalogObjects (cognitive 25) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/GetColumnsJob.java:51
- ContextLauncher.startDriver (cognitive 25) rsc/src/main/java/org/apache/livy/rsc/ContextLauncher.java:155
- LivyThriftSessionManager.startTimeoutChecker (cognitive 24) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:358
- fake_shell.magic_table (cognitive 24) REDACTED:393
- LivyServer.start (cognitive 23) server/src/main/scala/org/apache/livy/server/LivyServer.scala:67
- fake_shell.main (cognitive 22) REDACTED:508
- merge_livy_pr.resolve_jira_issue (cognitive 21) REDACTED:230
- bootstrap.Modal.backdrop (cognitive 20) docs/assets/themes/apache/bootstrap/js/bootstrap.js:980
- ThriftBinaryCLIService.initServer (cognitive 19) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftBinaryCLIService.scala:47
- ColumnBuffer.ensureCapacity (cognitive 19) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:359
- SparkEntries.sparkSession (cognitive 19) rsc/src/main/java/org/apache/livy/rsc/driver/SparkEntries.java:61
- merge_livy_pr.main (cognitive 19) REDACTED:352
- fake_shell.parse_code_into_nodes (cognitive 19) REDACTED:244
- LivyThriftSessionManager.incrementConnections (cognitive 18) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:482
- RSCClient.stop (cognitive 18) rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:213
- LivyClientBuilder.build (cognitive 18) api/src/main/java/org/apache/livy/LivyClientBuilder.java:120
- bootstrap.Carousel.slide (cognitive 18) docs/assets/themes/apache/bootstrap/js/bootstrap.js:377
- SparkKubernetesApp.monitorSparkKubernetesApp (cognitive 17) server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:350
- LivyThriftSessionManager.getOrCreateLivySession (cognitive 17) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:161
- SparkUtils.toJavaSQLType (cognitive 17) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/SparkUtils.java:113
- TUGIAssumingProcessor.process (cognitive 16) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthBridgeServer.scala:217
- PlainSaslServer.evaluateResponse (cognitive 16) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/PlainSaslServer.scala:50
- ColumnBuffer.getValues (cognitive 16) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:212
- JobHandleImpl.get (cognitive 16) client-http/src/main/java/org/apache/livy/client/http/JobHandleImpl.java:173
- bootstrap.Affix.checkPosition (cognitive 16) docs/assets/themes/apache/bootstrap/js/bootstrap.js:1925
- REDACTED
- TooManyMethods: LivyCLIService thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:36
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:173
- Duplicated block (7–8 lines × 2) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/GetColumnsJob.java:53
- Duplicated block (6 lines × 2) rsc/src/main/java/org/apache/livy/rsc/driver/SparkEntries.java:71
- Coverage collected but not gated
- Type Safety
- Future started here is not kept repl/src/main/scala/org/apache/livy/repl/Session.scala:163
- Owned disposable field is never released server/src/main/scala/org/apache/livy/server/LivyServer.scala:109
- Disposable created and abandoned in the function that made it repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:89
Minor — 131 finding(s)
- Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:1
- Orphaned file REDACTED:1
- Orphaned file rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:1
- Orphaned file rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:1
- Orphaned file repl/src/main/scala/org/apache/livy/repl/AbstractSparkInterpreter.scala:1
- Orphaned file repl/src/main/scala/org/apache/livy/repl/SparkRInterpreter.scala:1
- Orphaned file repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:1
- Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthBridgeServer.scala:1
- Orphaned file rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:1
- Orphaned file thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:1
- Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyOperationManager.scala:1
- Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftBinaryCLIService.scala:1
- Orphaned file client-common/src/main/java/org/apache/livy/client/common/ClientConf.java:1
- Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpCLIService.scala:1
- Orphaned file server/src/main/scala/org/apache/livy/server/SessionServlet.scala:1
- Orphaned file client-http/src/main/java/org/apache/livy/client/http/JobHandleImpl.java:1
- Orphaned file scala-api/src/main/scala/org/apache/livy/scalaapi/ScalaJobHandle.scala:1
- Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyExecuteStatementOperation.scala:1
- Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthFactory.scala:1
- Orphaned file server/src/main/scala/org/apache/livy/utils/LivySparkUtils.scala:1
- Orphaned file thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/SparkUtils.java:1
- Orphaned file server/src/main/scala/org/apache/livy/utils/SparkProcessBuilder.scala:1
- Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/PlainSaslServer.scala:1
- Orphaned file server/src/main/scala/org/apache/livy/server/recovery/FileSystemStateStore.scala:1
- Orphaned file rsc/src/main/java/org/apache/livy/rsc/driver/SparkEntries.java:1
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:247
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:301
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:318
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:334
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:380
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:382
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:97
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:105
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:126
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:129
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/driver/JobWrapper.java:70
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:283
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:319
- Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:520
- Interpolated log message defeats structured logging client-common/src/main/java/org/apache/livy/client/common/ClientConf.java:225
- Interpolated log message defeats structured logging client-common/src/main/java/org/apache/livy/client/common/ClientConf.java:233
- Duplicated predicate server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:489
- Duplicated predicate server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:493
- Duplicated predicate repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:104
- Duplicated predicate repl/scala-2.12/src/main/scala/org/apache/livy/repl/SparkInterpreter.scala:69
- Most significant orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:1
- Most significant orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:1
- Most significant orphaned file rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- REDACTED
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- No network policy
- Disabled test integration-test/src/test/scala/org/apache/livy/test/JobApiIT.scala:138
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No rollback/health safety
- No changelog
- Secure cookie flags not detected
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch server/src/main/scala/org/apache/livy/server/LivySessionMetrics.scala:57
Minor — 2 finding(s)
- Outdated: github-pages
- Outdated: rouge
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2629793d33944ebab6fe8803e63fb41e/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2629793d33944ebab6fe8803e63fb41e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude docs/assets/themes/apache/jquery . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 59 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 17 | 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) — `server/src/main/scala/org/apache/livy/server/ui/UIServlet.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 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |