Public report of apache/livy, published 14 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey β†’ Signed and filed in the standard's public register, 14 November 2026, 14:33 UTC Β· Survey ID cd_d6d0596cca284803aeca70cc437f0b58

apache/livy

Measured 14 November 2026, 14:33 UTC, at code version bc23445

CAI score 49out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 2 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 25,195 lines of product code in 15 projects, tests not counted Β· Estimated rebuild effort: about 0.2 person-years Β· Weakest lens: Code Health, 42

Findings by how serious they are

34 critical 145 serious 132 minor

9 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 14:33 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology β–Έ

69of 69 dimensions measured by tools.
292of 311 findings point to an exact file and line, so you can open each one in the code. The other 19 concern the repository as a whole, such as missing documentation.
69dimensions across 7 lenses, read from 25,195 lines of product code in 15 projects.
Chapters

Executive summary

apache/livy falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 49 out of 100 and is rated Adequate, and all 34 of its critical findings are security problems.

Code Health, at 42, is the weakest lens and counts most in the score. The best first steps are adding type checking and declaring which values may be missing, each worth about 4 points. Raising Code Health to 67 would lift the score to about 54.

Seventeen 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 €36,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Code Health 42 Β· counts for 46%Accessibility 49 Β· counts for 25%Security and Compliance 54 Β· counts for 14%Maturity 54 Β· counts for 8%Production Readiness 58 Β· counts for 4%Architecture 98 Β· counts for 2%Performance 100 Β· counts for 1%

If Code Health rose from 42 to 67, the lowest score rated Strong, the score would rise from 49 to about 54.

Code composition: what the lines of code are
Product code 64%Tests 36%
New since the last survey: 41 findings

These 41 critical or serious findings weren't in the previous survey, on 26 October 2026.

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 69 findings

These 69 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.

  • Cyclomatic Complexity Β· bootstrap.Tooltip.show (cyclomatic 22) docs/assets/themes/apache/bootstrap/js/bootstrap.js
  • Cyclomatic Complexity Β· bootstrap.Affix.checkPosition (cyclomatic 16) docs/assets/themes/apache/bootstrap/js/bootstrap.js
  • Cognitive Complexity Β· bootstrap.Tooltip.show (cognitive 29) docs/assets/themes/apache/bootstrap/js/bootstrap.js
  • Cognitive Complexity Β· bootstrap.Modal.backdrop (cognitive 20) docs/assets/themes/apache/bootstrap/js/bootstrap.js
  • Cognitive Complexity Β· bootstrap.Carousel.slide (cognitive 18) docs/assets/themes/apache/bootstrap/js/bootstrap.js
  • Cognitive Complexity Β· bootstrap.Affix.checkPosition (cognitive 16) docs/assets/themes/apache/bootstrap/js/bootstrap.js
  • God Classes Β· FileTooLong: js/bootstrap.js docs/assets/themes/apache/bootstrap/js/bootstrap.js
  • Code Duplication Β· Duplicated block (14 lines × 2) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala
  • Churn × Complexity Hotspots Β· Hotspot: server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala
  • Dependency Vulnerabilities Β· Critical CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· Critical CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· Critical CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Critical CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Critical CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Critical CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Critical CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Critical CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: REDACTED api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: REDACTED api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· High CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: REDACTED api/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: REDACTED api/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: REDACTED api/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: REDACTED api/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] api/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Dependency Vulnerabilities Β· Medium CVE: [GHSA redacted] thriftserver/client/pom.xml
  • Visual & motion safety Β· Low contrast colour pair in CSS (3.6:1) docs/assets/themes/apache/bootstrap/css/bootstrap.css
  • A11y enforcement Β· Accessibility enforcement below the top rung
Rebuild cost: about €36,000 Β· Estimate
Cost to rebuild€12,000 to €61,000, for 201 to 638 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 25,195 lines of product code
What it is notNot 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.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
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.
Raises the score by about 4 points Β· Medium effort Β· Type Safety
2
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.
Raises the score by about 4 points Β· Medium effort Β· Nullable reference types
3
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.
Raises the score by about 3 points Β· Medium effort Β· Visual & motion safety

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed Β· Value at risk
This code would cost about €36,000 to build again, about 0.2 person-years of work. Its weakest lens is Code Health, at 42 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first Β· First action
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. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture β€” module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch livy-api livy-api livy-client-common livy-client-common livy-client-common->livy-api livy-client-http livy-client-http livy-client-http->livy-api livy-client-http->livy-client-common livy-core_2.12 12 livy-core_2.13 13 livy-integration-test livy-integration-test livy-server livy-server livy-integration-test->livy-server livy-repl_2.12 12 livy-repl_2.13 13 livy-rsc livy-rsc livy-rsc->livy-api livy-rsc->livy-client-common livy-scala-api_2.12 12 livy-scala-api_2.13 13 livy-server->livy-rsc livy-test-lib livy-test-lib livy-test-lib->livy-api livy-thriftserver livy-thriftserver livy-thriftserver->livy-api livy-thriftserver->livy-rsc livy-thriftserver->livy-server livy-thriftserver-session livy-thriftserver-session livy-thriftserver->livy-thriftserver-session livy-thriftserver-session->livy-api

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

56 modules, with 63 dependencies between them. 3 loops run through 10 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 16 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses β†’1 dev2 org.apache3 org.apache.livy4 org.apache.livy.EOLUtils5 org.apache.livy.LivyConf6 org.apache.livy.annotations7 org.apache.livy.repl.AbstractSparkInterpreter8 org.apache.livy.repl.Interpreter9 org.apache.livy.repl.SQLInterpreter10 org.apache.livy.repl.SparkRInterpreter11 org.apache.livy.scalaapi12 org.apache.livy.sessions.Session13 org.apache.livy.sessions.SessionManager14 org.apache.livy.thriftserver.serde15 org.apache.livy.thriftserver.types16 org.apache.livy.ExecutionStatus17 org.apache.livy.MsgType18 org.apache.livy.client.common19 org.apache.livy.repl20 org.apache.livy.server.auth21 org.apache.livy.server.recovery22 org.apache.livy.thriftserver.auth.ldap23 org.apache.livy.thriftserver.cli24 org.apache.livy.thriftserver.operation25 org.apache.livy.thriftserver.rpc26 org.apache.livy.thriftserver.session27 org.apache.livy.utils28 org.apache.livy.client.http29 org.apache.livy.rsc.rpc30 org.apache.livy.server.interactive31 org.apache.livy.thriftserver.auth32 org.apache.livy.utils.KubernetesExtensions33 org.apache.livy.rsc.driver34 org.apache.livy.sessions35 org.apache.livy.rsc36 org.apache.livy.server37 org.apache.livy.sessions.SessionState38 org.apache.livy.server.batch39 org.apache.livy.thriftserver40 org.apache.livy.thriftserver.ui
1 dev
2 org.apache
3 org.apache.livy
4 org.apache.livy.EOLUtils
5 org.apache.livy.LivyConf
6 org.apache.livy.annotations
7 org.apache.livy.repl.AbstractSparkInterpreter
8 org.apache.livy.repl.Interpreter
9 org.apache.livy.repl.SQLInterpreter
10 org.apache.livy.repl.SparkRInterpreter
11 org.apache.livy.scalaapi
12 org.apache.livy.sessions.Session
13 org.apache.livy.sessions.SessionManager
14 org.apache.livy.thriftserver.serde
15 org.apache.livy.thriftserver.types
16 org.apache.livy.ExecutionStatus3
17 org.apache.livy.MsgType2
18 org.apache.livy.client.common4
19 org.apache.livy.repl7
20 org.apache.livy.server.auth1
21 org.apache.livy.server.recovery6111
22 org.apache.livy.thriftserver.auth.ldap4
23 org.apache.livy.thriftserver.cli324
24 org.apache.livy.thriftserver.operation838
25 org.apache.livy.thriftserver.rpc1
26 org.apache.livy.thriftserver.session15
27 org.apache.livy.utils15
28 org.apache.livy.client.http67
29 org.apache.livy.rsc.rpc15
30 org.apache.livy.server.interactive311132
31 org.apache.livy.thriftserver.auth721
32 org.apache.livy.utils.KubernetesExtensions12
33 org.apache.livy.rsc.driver102211
34 org.apache.livy.sessions11
35 org.apache.livy.rsc12571
36 org.apache.livy.server623
37 org.apache.livy.sessions.SessionState11
38 org.apache.livy.server.batch21122
39 org.apache.livy.thriftserver1232232123
40 org.apache.livy.thriftserver.ui1
Uses a module listed above itPart of a loopThe module itself
1 dev2 org.apache3 org.apache.livy4 org.apache.livy.EOLUtils5 org.apache.livy.LivyConf6 org.apache.livy.annotations7 org.apache.livy.repl.AbstractSparkInterpreter8 org.apache.livy.repl.Interpreter9 org.apache.livy.repl.SQLInterpreter10 org.apache.livy.repl.SparkRInterpreter11 org.apache.livy.scalaapi12 org.apache.livy.sessions.Session13 org.apache.livy.sessions.SessionManager14 org.apache.livy.thriftserver.serde15 org.apache.livy.thriftserver.types16 org.apache.livy.ExecutionStatus17 org.apache.livy.MsgType18 org.apache.livy.client.common19 org.apache.livy.repl20 org.apache.livy.server.auth21 org.apache.livy.server.recovery22 org.apache.livy.thriftserver.auth.ldap23 org.apache.livy.thriftserver.cli24 org.apache.livy.thriftserver.operation25 org.apache.livy.thriftserver.rpc26 org.apache.livy.thriftserver.session27 org.apache.livy.utils28 org.apache.livy.client.http29 org.apache.livy.rsc.rpc30 org.apache.livy.server.interactive31 org.apache.livy.thriftserver.auth32 org.apache.livy.utils.KubernetesExtensions33 org.apache.livy.rsc.driver34 org.apache.livy.sessions35 org.apache.livy.rsc36 org.apache.livy.server37 org.apache.livy.sessions.SessionState38 org.apache.livy.server.batch39 org.apache.livy.thriftserver40 org.apache.livy.thriftserver.uidev1org.apache2org.apache.livy3org.apache.livy.EOLUtils4org.apache.livy.LivyConf5org.apache.livy.annotations6org.apache.livy.repl.AbstractSparkInterpreter7org.apache.livy.repl.Interpreter8org.apache.livy.repl.SQLInterpreter9org.apache.livy.repl.SparkRInterpreter10org.apache.livy.scalaapi11org.apache.livy.sessions.Session12org.apache.livy.sessions.SessionManager13org.apache.livy.thriftserver.serde14org.apache.livy.thriftserver.types15org.apache.livy.ExecutionStatus16org.apache.livy.MsgType17org.apache.livy.client.common18org.apache.livy.repl19org.apache.livy.server.auth20org.apache.livy.server.recovery21org.apache.livy.thriftserver.auth.ldap22org.apache.livy.thriftserver.cli23org.apache.livy.thriftserver.operation24org.apache.livy.thriftserver.rpc25org.apache.livy.thriftserver.session26org.apache.livy.utils27org.apache.livy.client.http28org.apache.livy.rsc.rpc29org.apache.livy.server.interactive30org.apache.livy.thriftserver.auth31org.apache.livy.utils.KubernetesExtensions32org.apache.livy.rsc.driver33org.apache.livy.sessions34org.apache.livy.rsc35org.apache.livy.server36org.apache.livy.sessions.SessionState37org.apache.livy.server.batch38org.apache.livy.thriftserver39org.apache.livy.thriftserver.ui403247161114324838115156715311132721121022111112571623112112212322321231+16 more modules (most-connected shown)

At a glance β€” Code Health Β· 42% Β· Weak Β· gated by R1, X5 Β·

At a glance β€” Architecture Β· 98% Β· Exemplary Β·

At a glance β€” Maturity Β· 54% Β· Adequate Β· gated by D34, M2 Β·

At a glance β€” Readiness Β· 58% Β· Adequate Β· gated by P3 Β·

At a glance β€” Security Β· 54% Β· Adequate Β· gated by D29, D36 Β·

At a glance β€” Accessibility Β· 49% Β· Adequate Β· gated by AC6 Β·

At a glance β€” Performance Β· 100% Β· Exemplary Β·

Security & Compliance β€” OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 β€” Software Supply Chain Failures34High / Critical
A05:2025 β€” Injection17High / Critical
A02:2025 β€” Security Misconfiguration17High / Critical

Roadmap

Top priorities: 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; 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; 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.

Ranked by impact Γ· effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
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.+4.4 ptsMediumType 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.+3.8 ptsMediumNullable reference types
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.+3.3 ptsMediumVisual & motion safety
Resolve the 1 No ADRs found finding(s) in ADR Quality β€” start with REDACTED.+1.5 ptsLowADR Quality
Interpolated log message defeats structured logging+1.7 ptsMediumStructured logging
Future started here is not kept+1.6 ptsMediumAsync correctness
Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity β€” start with InteractiveSession.prepareBuilderProp (cyclomatic 27), LivyServer.start (cyclomatic 21), ColumnBuffer.ensureCapacity (cyclomatic 19).+1.4 ptsHighCyclomatic Complexity
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.3 ptsMediumArchitecture documentation

File quality

Per-file score 0–10 β€” a quality signature. Of 60 files carrying findings, judged against the Preview bar: 7% slop Β· 31% mixed Β· 62% near-clean.

FileScoreBandWorst signal
REDACTED1.1SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.6SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.2SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.7MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED5.8MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.8MixedIaC & Container Security: Medium IaC: REDACTED
server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala6.0MixedExplicit Debt: TodoComment
server/src/main/scala/org/apache/livy/server/LivyServer.scala6.0MixedExplicit Debt: TodoComment
server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala6.0MixedExplicit Debt: TodoComment
thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala6.0MixedExplicit Debt: TodoComment
thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala6.0MixedExplicit Debt: TodoComment
REDACTED6.3MixedIaC & Container Security: Medium IaC: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it β€” and it is a grade, not a gap.

Critical β€” 34

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.

Serious β€” 145

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.

Minor β€” 132

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved β€” 9

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository β€” a backup job that nothing shows was ever restored from proves nothing about restores β€” or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment β€” run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 69 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: βœ“ Measured β€” a deterministic fact (LoC, complexity, coverage); ~ Modeled β€” an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): βœ“ Tool-verified means the property itself was measured across the surface; β—‹ Nothing flagged means the probes came back clean β€” a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence β€” absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked β€” 69 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D16D17D19D20D21D26D28D29D30D31D34D35D36D40D41D43D44AC3AC6AX10AX2AX3AX4AX6GD1IC1M1M2M3M4P1P10P2P3P4P6PF3R1R10R2R3R7R9S1X1X12X13X16X18X19X20X21X23X24X26X27X3X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality β€” in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report β€” three questions
  1. 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, 292 of 311 do; the remainder are repo-wide signals β€” a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) β€” re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0βœ“ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0βœ“ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0βœ“ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400βœ“ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400βœ“ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 Β· 0.31.0βœ“ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 Β· 0.69.3 Β· 3.2.533βœ“ deterministic

Every finding is locatable in findings.md. Run 01a1da79-e6cc-7b72-aa04-1676c5e1626a.

The exact command behind every deep-scan dimension β€” tool, version, invocation and retained raw output β€” is in Appendix B β€” Reproduction & audit trail.

Run transparency β€” what happened this run

What ran differently this time β€” a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage β€” not measured this run β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT 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.
  • D11 Test Reliability β€” not measured this run β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.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 β€” We measured this, but not all of it. What we did not reach is a gap on our side β€” a collector, parser or image we have not built yet β€” so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Maven POM, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Maven dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality β€” measured, with a gap in what it reached β€” We measured this, but not all of it. What we did not reach is a gap on our side β€” a collector, parser or image we have not built yet β€” so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency β€” measured, with a gap in what it reached β€” We measured this, but not all of it. What we did not reach is a gap on our side β€” a collector, parser or image we have not built yet β€” so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency β€” not measured this run β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability β€” not measured this run β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) β€” not measured this run β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. `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 β€” We measured this, but not all of it. What we did not reach is a gap on our side β€” a collector, parser or image we have not built yet β€” so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 β€” an image could not be pulled) β€” spark-master Error context canceled livy Error context canceled Error response from daemon: pull access denied for livy-dev-spark, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: spark-master Pulling spark-master Error pull access denied for livy-dev-spark, repository does not exist or may require 'docker login': denied: requested access to the resource is denied livy Error context canceled Error response from daemon: pull access denied for livy-dev-spark, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; 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 β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β€” not a finding that the repository lacks personal data controls.
  • C2 Access Controls β€” not measured this run β€” We could not measure this here. That is a gap on our side β€” a collector, parser or image we have not built yet β€” and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β€” not a finding that the repository lacks authorization controls.
  • M4 Documentation accuracy β€” measured, with a gap in what it reached β€” We measured this, but not all of it. What we did not reach is a gap on our side β€” a collector, parser or image we have not built yet β€” so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. 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.
  • X1 Async correctness β€” measured, with a gap in what it reached β€” We measured this, but not all of it. What we did not reach is a gap on our side β€” a collector, parser or image we have not built yet β€” so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X12 Unreachable branch β€” measured, with a gap in what it reached β€” We measured this, but not all of it. What we did not reach is a gap on our side β€” a collector, parser or image we have not built yet β€” so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X13 Undrained process stream β€” measured, with a gap in what it reached β€” We measured this, but not all of it. What we did not reach is a gap on our side β€” a collector, parser or image we have not built yet β€” so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared β€” every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap β€” a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see β€” the honest edge of the measurement, not a failure of it.

  • 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.
  • 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • 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.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics β€” a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see β€” only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) β€” controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 Β· Cyclomatic Complexity8.7 / 10Strongβœ“ Tool-verified

What it measures: How tangled the control flow is β€” methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 8.7 / 10 Β· rule-coverage 100% Β· ceiling Prevented

8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was InteractiveSession.prepareBuilderProp at 27.

InteractiveSession.prepareBuilderProp (cyclomatic 27)server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala:211
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

+ 3 more group(s) β€” more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity β€” start with InteractiveSession.prepareBuilderProp (cyclomatic 27), LivyServer.start (cyclomatic 21), ColumnBuffer.ensureCapacity (cyclomatic 19). β€” 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 8 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d1_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D2 Β· Cognitive Complexity6.9 / 10Adequateβœ“ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 6.9 / 10 Β· rule-coverage 100% Β· ceiling Prevented

28 method(s) exceeded the cognitive complexity threshold of 15; the worst was InteractiveSession.prepareBuilderProp at 42.

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
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

+ 23 more group(s) β€” more in Appendix A; the complete list is findings.md.

What to do

  1. 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.

Detailed fixes: d2_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D3 Β· God Classes9.3 / 10Stronggated by 4 serious findingsβœ“ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 9.3 / 10 Β· rule-coverage 100% Β· ceiling Prevented

4 god class(es) detected.

FileTooLong: utils/SparkKubernetesApp.scala Β· Γ—3server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala
TooManyMethods: LivyCLIServicethriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:36

What to do

  1. Resolve the 3 FileTooLong finding(s) in God Classes β€” start with SparkKubernetesApp.scala, ThriftCLIService.scala, InteractiveSession.scala. β€” One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 TooManyMethods finding(s) in God Classes β€” start with LivyCLIService.scala. β€” One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d3_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D4 Β· Code Duplication9.4 / 10Stronggated by 10 serious findingsβœ“ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 9.4 / 10 Β· rule-coverage 100% Β· ceiling Verified

2 duplicated block group(s) detected. 1.4 % of the production lines (348 of 25,195) are in a reported copy. A further 8 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Edited copy of a member (12 corresponding lines) Β· Γ—2rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:615
Edited copy of a member (17 corresponding lines)server/src/main/scala/org/apache/livy/server/batch/CreateBatchRequest.scala:39
Edited copies of one member (3 members, 17+ corresponding lines)thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:132
Edited copies of one member (4 members, 16+ corresponding lines)thriftserver/server/src/main/scala/org/apache/livy/thriftserver/operation/GetColumnsOperation.scala:37
Edited copy of a member (15 corresponding lines)repl/src/main/scala/org/apache/livy/repl/ReplDriver.scala:106

+ 4 more group(s) β€” more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 2 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication β€” start with Rpc.java, ThriftBinaryCLIService.scala. β€” One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication β€” start with CreateBatchRequest.scala. β€” One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Edited copies of one member (3 members, 17+ corresponding lines) finding(s) in Code Duplication β€” start with ThriftCLIService.scala. β€” One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d4_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D5 Β· Coupling10.0 / 10Exemplaryβœ“ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type β€” the population is all types, not a name convention.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Prevented

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).

βœ“ On the Gold path β€” maintain.

Detailed fixes: d5_recommendation.md.

D6 Β· Cohesion (LCOM4)9.5 / 10Stronggated by 2 serious findingsβœ“ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class β€” the population is all types, not a name convention.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 9.5 / 10 Β· rule-coverage 100% Β· ceiling Verified

2 of 51 classes have LCOM4 above 3.

Low cohesion: PythonInterpreter (LCOM4 5) Β· Γ—2repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:217

What to do

  1. 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).

Detailed fixes: d6_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D12 Β· Dependency Hygiene9.9 / 10Exemplaryβœ“ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 9.9 / 10 Β· rule-coverage 100% Β· ceiling Verified

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.

Outdated: github-pages Β· Γ—2

βœ“ On the Gold path β€” maintain.

Detailed fixes: d12_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D13 Β· Secret Scanning10.0 / 10Exemplaryβ—‹ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Prevented

Secret scan ran and found no leaked secrets.

βœ“ On the Gold path β€” maintain.

Detailed fixes: d13_recommendation.md.

D14 Β· License Compliance10.0 / 10Exemplaryβ—‹ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Verified

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.

βœ“ On the Gold path β€” maintain.

Detailed fixes: d14_recommendation.md.

D15 Β· Churn × Complexity Hotspots9.9 / 10Stronggated by 1 serious findingβœ“ Tool-verified

What it measures: Files that change often and are also complex β€” the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 9.9 / 10 Β· rule-coverage 100% Β· ceiling Documented

Top hotspots: server/src/main/scala/org/apache/livy/server/LivyServer.scala (4×21=84)

Hotspot: server/src/main/scala/org/apache/livy/server/LivyServer.scalaserver/src/main/scala/org/apache/livy/server/LivyServer.scala:67

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots β€” start with LivyServer.scala. β€” One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d15_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D16 Β· Bus Factor9.1 / 10Exemplaryβœ“ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 9.1 / 10 Β· rule-coverage 100% Β· ceiling Documented

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.

Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)

βœ“ On the Gold path β€” maintain.

Detailed fixes: d16_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D17 Β· Explicit Debt9.9 / 10Stronggated by 18 serious findingsβœ“ Tool-verified

What it measures: Acknowledged debt left in the code β€” TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 9.9 / 10 Β· rule-coverage 100% Β· ceiling Prevented

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.

TodoComment Β· Γ—17thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:266
HackCommentclient-http/src/test/scala/org/apache/livy/client/http/HttpClientSpec.scala:256

What to do

  1. 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).
  2. Resolve the 1 HackComment finding(s) in Explicit Debt β€” start with HttpClientSpec.scala. β€” One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D19 Β· Documentation Quality10.0 / 10Exemplaryβ—‹ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

1 of 1 documentation facets pass in full. 8 document(s) read across 1 unit(s).

βœ“ On the Gold path β€” maintain.

Detailed fixes: d19_recommendation.md.

D20 Β· ADR Quality0.0 / 10Criticalβœ“ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 0.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

No architecture decision records were found.

No ADRs foundREDACTED:370

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality β€” start with REDACTED. β€” One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D21 Β· Naming Consistency10.0 / 10Exemplaryβ—‹ Nothing flagged

What it measures: Whether names β€” types, methods, variables β€” are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Verified

0 naming inconsistencies among 32 declarations measured against a convention their peers follow.

βœ“ On the Gold path β€” maintain.

Detailed fixes: d21_recommendation.md.

D26 Β· Project Cohesion10.0 / 10Exemplaryβœ“ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

0 of 15 build units (Bundler, Maven) flagged as possibly oversized/incoherent.

βœ“ On the Gold path β€” maintain.

Detailed fixes: d26_recommendation.md.

D28 Β· Secrets (history)10.0 / 10Exemplaryβ—‹ Nothing flagged

What it measures: Whether any secrets were ever committed β€” scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout β€” the full git history, then a second --no-git pass over the working tree as it stands β€” merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side β€” unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

βœ“ On the Gold path β€” maintain.

Detailed fixes: d28_recommendation.md.

D29 Β· Static Analysis (SAST)3.5 / 10Weakβœ“ Tool-verified

What it measures: Real static-analysis (SAST) findings β€” likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files β€” exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 3.5 / 10 Β· rule-coverage 100% Β· ceiling Documented

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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 2 more group(s) β€” more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. 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).
  3. 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).

Detailed fixes: d29_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D30 Β· Dependency Vulnerabilities8.2 / 10Adequategated by 17 critical findingsβœ“ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares β€” Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 8.2 / 10 Β· rule-coverage 100% Β· ceiling Documented

27 finding(s): 0 critical, 17 high, 10 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 17 High CVE finding(s) in Dependency Vulnerabilities β€” start with REDACTED (17). β€” One of this dimension's main actionable groups (17 issue-level).
  2. Resolve the 10 Medium CVE finding(s) in Dependency Vulnerabilities β€” start with REDACTED (10). β€” One of this dimension's main actionable groups (10 warning-level).

Detailed fixes: d30_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D31 Β· IaC & Container Security7.6 / 10Adequategated by 3 critical findingsβœ“ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 7.6 / 10 Β· rule-coverage 100% Β· ceiling Documented

17 finding(s): 0 critical, 3 high, 14 medium, 0 low.

REDACTED
REDACTED

What to do

  1. 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).
  2. 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).

Detailed fixes: d31_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D34 Β· Knowledge Freshness2.3 / 10Criticalβœ“ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned β€” last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 2.3 / 10 Β· rule-coverage 100% Β· ceiling Documented

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.

Orphaned file Β· Γ—89thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:1
Most significant orphaned file Β· Γ—3thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:1
Concentrated knowledge decay

What to do

  1. 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).
  2. 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).
  3. Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. β€” One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D35 Β· Change Coupling10.0 / 10Exemplaryβœ“ Tool-verified

What it measures: Whether files that change together actually belong together β€” pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only β€” tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file β‰₯10 revisions, β‰₯5 shared commits, β‰₯50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only β€” test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair β€” a command and the reference page that restates it β€” is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

No strong hidden change-coupling between production files.

βœ“ On the Gold path β€” maintain.

Detailed fixes: d35_recommendation.md.

D36 Β· Supply-chain Provenance & Signing2.5 / 10Weakβœ“ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity β€” generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals β€” generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions β€” scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 2.5 / 10 Β· rule-coverage 100% Β· ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 1 more group(s) β€” more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β€” One of this dimension's main actionable groups (1 warning-level).
  3. 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).

Detailed fixes: d36_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D40 Β· Network Egress Confinement6.0 / 10Adequateβœ“ Tool-verified

What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn β€” language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction β€” baseline misconfigs stay with D31). Deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 6.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

0/2 network-egress controls present (network policy, egress restriction).

No network policy

What to do

  1. Resolve the 1 No network policy finding(s) in Network Egress Confinement. β€” One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d40_recommendation.md Β· top locations in Appendix A, every location in findings.md.

D41 Β· Kernel & Syscall Confinement6.0 / 10Adequateβœ“ Tool-verified

What it measures: Whether Kubernetes workloads confine the kernel boundary β€” a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer β€” shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 6.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

No workload manifest could be read as a pod spec, so no confinement was judged.

Detailed fixes: d41_recommendation.md.

D43 Β· Malicious Dependencies10.0 / 10Exemplaryβœ“ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable β€” a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it β€” a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

βœ“ On the Gold path β€” maintain.

Detailed fixes: d43_recommendation.md.

D44 Β· Platform End-of-Life10.0 / 10Exemplaryβœ“ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON β€” the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates β€” no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged β€” `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on β€” and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads β€” never scores it clean.

Maturity: Documented β†’ Verified β†’ Prevented Β· effective 10.0 / 10 Β· rule-coverage 100% Β· ceiling Documented

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.

βœ“ On the Gold path β€” maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS Β· M = Maturity Β· P = Readiness.

AC3 Β· Page structure10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Accessibility β€” Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks β€” lang, title, single main landmark β€” fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script β€” tagged-template (html`…`) UIs and hyperscript DOM factories β€” is not read at all.

AC6 Β· Visual & motion safety1.0 / 10Criticalβœ“ Tool-verified

Other Β· Accessibility β€” Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast β€” PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL β€” only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) β€” computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script β€” tagged-template (html`…`) UIs and hyperscript DOM factories β€” is not read at all.

  • `.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
  • `.tag_box a.active` sets color: #FFF on background-color: #57A957 β€” 2.9: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:326
  • `.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
  • `.nav-pills > li.active > a, .nav-pills > li.active > a:hover, .nav-pills > li.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:4221
  • `.pagination > .active > a, .pagination > .active > span, .pagination > .active > a:hover, .pagination > .active > span:hover, .pagination > .active > a:focus, .pagination > .active > span: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:4989
  • `a.list-group-item.active > .badge, .nav-pills > .active > a > .badge` sets color: #428bca on background-color: #ffffff β€” 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:5220
  • `a.list-group-item.active, a.list-group-item.active:hover, a.list-group-item.active: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:5595
  • `.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.
AX10 Β· Code composition9.5 / 10Exemplaryβœ“ Tool-verified

Other Β· Architecture β€” How the codebase splits by code ROLE β€” domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER β€” domain, then infrastructure, then application β€” so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone β€” no declared namespace was available to add to the evidence β€” and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention β€” a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX2 Β· Stateful singletons10.0 / 10Exemplaryβœ“ Tool-verified

Other Β· Architecture β€” Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

AX3 Β· Project dependency cycles10.0 / 10Exemplaryβœ“ Tool-verified

Other Β· Architecture β€” Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 Β· Dependency direction10.0 / 10Exemplaryβœ“ Tool-verified

Other Β· Architecture β€” Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) β€” the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX6 Β· Interface segregation10.0 / 10Exemplaryβœ“ Tool-verified

Other Β· Architecture β€” Whether interfaces stay focused rather than fat β€” the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count β€” members counted by name, so an overload group counts once β€” which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) β€” data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

GD1 Β· Unfinished & placeholder code9.9 / 10Exemplaryβœ“ Tool-verified

Other Β· Code Health β€” Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • `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 & stubs7.6 / 10Strongβœ“ Tool-verified

Other Β· Code Health β€” Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `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)6.7 / 10Strongβœ“ Tool-verified

Maturity Β· Maturity β€” Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 Β· Architecture documentation0.0 / 10Criticalβœ“ Tool-verified

Maturity Β· Maturity β€” Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • 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 structure10.0 / 10Exemplaryβœ“ Tool-verified

Maturity Β· Maturity β€” Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 Β· Documentation accuracy10.0 / 10Exemplaryβ—‹ Nothing flagged

Maturity Β· Maturity β€” Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 Β· CI/CD gates10.0 / 10Exemplaryβ—‹ Nothing flagged

Readiness Β· Readiness β€” Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 Β· Library API & versioning10.0 / 10Exemplaryβ—‹ Nothing flagged

Readiness Β· Readiness β€” For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 Β· Observability6.5 / 10Strongβœ“ Tool-verified

Readiness Β· Readiness β€” Whether the code is diagnosable in production β€” structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • 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.
  • Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 Β· Security & performance tooling3.0 / 10Weakβœ“ Tool-verified

Readiness Β· Readiness β€” Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step β€” in this repository's own ecosystem. Exhaustive, deterministic.

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 & Rollback5.0 / 10Adequateβœ“ Tool-verified

Readiness Β· Readiness β€” Whether releases are automated and safely reversible (probes, rolling updates, approval gates) β€” from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

  • 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 Hygiene5.0 / 10Adequateβœ“ Tool-verified

Readiness Β· Readiness β€” Whether releases are traceable β€” a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • 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.
PF3 Β· Async & latency hygiene10.0 / 10Exemplaryβœ“ Tool-verified

Readiness Β· Performance β€” Whether asynchronous code stays responsive β€” it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere β€” .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect β€” and, for a .NET library with β‰₯5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

R1 Β· Type Safety0.0 / 10Criticalβœ“ Tool-verified

React / JS Β· Code Health β€” How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 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 Duplication10.0 / 10Exemplaryβœ“ Tool-verified

React / JS Β· Code Health β€” The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines β€” so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own β€” or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

R2 Β· Cyclomatic Complexity10.0 / 10Exemplaryβœ“ Tool-verified

React / JS Β· Code Health β€” Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) β€” real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

R3 Β· Large Files10.0 / 10Exemplaryβœ“ Tool-verified

React / JS Β· Code Health β€” How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

R7 Β· Dead Code10.0 / 10Exemplaryβœ“ Tool-verified

React / JS Β· Code Health β€” Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

R9 Β· Circular Imports10.0 / 10Exemplaryβœ“ Tool-verified

React / JS Β· Architecture β€” Import cycles in the module graph (D-386) β€” files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 Β· Web-Security Posture4.5 / 10Weakβœ“ Tool-verified

Other Β· Security β€” Read from this repository's Scala source and the Java beside it: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) β€” facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (server/src/main/scala/org/apache/livy/server/JsonServlet.scala:39 β€” `ScalatraServlet`), so its Scala source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation β€” each credited where its Scala spelling appears in production source, not proven on every route. A Play application is credited the security headers Play's default `SecurityHeadersFilter` sends unless its build or configuration switches that filter off, and its cookies the HttpOnly flag Play sets by default.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • 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 correctness5.4 / 10Adequateβœ“ Tool-verified

Other Β· Code Health β€” Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • 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 branch10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether any branch is dead by construction β€” a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 Β· Undrained process stream10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether a child process that has BOTH standard streams redirected drains both β€” reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X16 Β· Unfloored truncation loop10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether a loop that shortens a string until it fits a length budget has a floor β€” one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything β€” a direct comparison on the length, a body guard, a break β€” bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression β€” never compared directly, never tested for truthiness, and with no other read of `x` β€” and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 Β· Disposal-pattern correctness5.0 / 10Adequateβœ“ Tool-verified

Other Β· Code Health β€” Whether a type's disposal matches what it OWNS β€” releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer β€” an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) β€” a class whose superclass or mixin lies outside the repository is not judged β€” and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `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 state10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether a method that temporarily changes state belonging to the whole process β€” the working directory, an environment variable β€” puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X20 Β· Mistyped argument guard10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether an argument guard throws the exception its own condition describes β€” a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` β€” directly or through the `using`, `lock` or `try` that wraps the throw β€” whose condition is read for a test that is true of a NON-null `p` β€” an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

X21 Β· Side-effecting pattern guard10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether a `when` guard is free of side effects β€” a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X23 Β· Unguarded diagnostic materialisation10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether the work a diagnostic log line costs is paid only when that line is wanted β€” C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence β€” a LINQ operator, a materialisation, `string.Join`, a serializer β€” with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` β€” outside any arrow or function passed as an argument, which the logger calls only when the level is on β€” with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 Β· Document value interpolated into markup unescaped10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Security β€” Whether text read out of the document being converted is escaped before it is written into generated markup β€” a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF β€” the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

X26 Β· Unsynchronised callback handoff10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed β€” a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it β€” and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 Β· Collection changed while being enumerated10.0 / 10Exemplaryβ—‹ Nothing flagged

Other Β· Code Health β€” Whether an enhanced `for` leaves the collection it is walking alone β€” a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone β€” CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone β€” Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone β€” an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A β€” the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B β€” the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X3 Β· Exception handling7.2 / 10Strongβœ“ Tool-verified

Other Β· Code Health β€” Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • 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)
X4 Β· Structured logging5.3 / 10Adequateβœ“ Tool-verified

Other Β· Code Health β€” Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `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 types2.0 / 10Criticalβœ“ Tool-verified

Other Β· Code Health β€” Whether Scala's null is held to the type system and not undermined by assertions β€” a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 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

Statically assessed 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; β‰ˆ16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim β€” a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC3 Β· Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC6 Β· Visual & motion safety1.4.3, 2.4.7Partial β€” literal CSS only

Not statically assessed β€” these 47 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference β€” by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health42%Weak β€” gated by R1, X5Capped at Fair by a Critical contributor β€” resolve it before relying on this lens.
Architecture98%ExemplarySolid.
Maturity54%Adequate β€” gated by D34, M2Capped at Fair by a Critical contributor β€” resolve it before relying on this lens.
Readiness58%Adequate β€” gated by P3Capped at Fair by a Critical contributor β€” resolve it before relying on this lens.
Security54%Adequate β€” gated by D29, D36Capped at Fair by a Critical contributor β€” resolve it before relying on this lens.
Accessibility49%Adequate β€” gated by AC6Capped at Fair by a Critical contributor β€” resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored β€” 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score β€” either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • 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

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase β€” the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P5 DR & Backup β€” not evidenced β€” repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included β€” 55 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • 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-master Error context canceled livy Error context canceled Error response from daemon: pull access denied for livy-dev-spark, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: spark-master Pulling spark-master Error pull access denied for livy-dev-spark, repository does not exist or may require 'docker login': denied: requested access to the resource is denied livy Error context canceled Error response from daemon: pull access denied for livy-dev-spark, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; 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.
  • 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (β‰₯2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it β€” e.g. `architecture:` β†’ `contexts:` β†’ `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value β€” D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .py, .rb, .scala source were not judged.
  • D25 ADR Conformance β€” no ADRs to check
  • D27 Navigability β€” D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) β€” 1 file(s) were not parsed by semgrep β€” the PII/GDPR ruleset never ran over them
  • 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.
  • 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 β€” coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here β€” Test coverage (D8) says why
  • PF1 Benchmark discipline β€” Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene β€” Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • 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).
  • X14 Bypassable address classification β€” not applicable β€” the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader β€” not applicable β€” the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document β€” not applicable β€” the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X22 Contradicted release guard β€” not applicable β€” the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob β€” not applicable β€” the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard β€” not applicable β€” the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element β€” not applicable β€” the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects β€” not applicable β€” the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly β€” This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing β€” Advisory β€” this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand β€” Advisory β€” this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A β€” Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical β€” 34 finding(s)
D30 Β· Dependency Vulnerabilities Β· High CVE Β· Γ—17
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 Β· Static Analysis (SAST) Β· REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 Β· IaC & Container Security Β· High IaC Β· Γ—3
  • REDACTED
  • REDACTED
  • REDACTED
D29 Β· Static Analysis (SAST) Β· REDACTED
  • REDACTED
  • REDACTED
D29 Β· Static Analysis (SAST) Β· REDACTED
  • REDACTED
  • REDACTED
D29 Β· Static Analysis (SAST) Β· REDACTED Β· Γ—1
  • REDACTED
S1 Β· Web-Security Posture Β· TLS certificate validation disabled Β· Γ—1
  • TLS certificate validation disabled server/src/main/scala/org/apache/livy/server/auth/LdapAuthenticationHandlerImpl.scala:157 β€” 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.
Serious β€” 145 finding(s)
D17 Β· Explicit Debt Β· TodoComment Β· Γ—17
  • TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:266 β€” // TODO β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:279 β€” // TODO β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/operation/Operation.scala:63 β€” // TODO: get and return also the task status β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:225 β€” // TODO: We don't do anything for now, just log this for debugging. β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpCLIService.scala:148 β€” // TODO: check defaults: maxTimeout, keepalive, maxBodySize, β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthFactory.scala:80 β€” // TODO: add PAM when supported β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthenticationProvider.scala:28 β€” // TODO: support PAM β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:420 β€” // TODO analyse available exceptions β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment server/src/main/scala/org/apache/livy/utils/SparkYarnApp.scala:276 β€” // TODO Instead of spawning a thread for every session, create a centralized thread and β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment server/src/main/scala/org/apache/livy/server/LivyServer.scala:96 β€” // TODO Create a new class to pass variables from LivyServer to sessions and remove these β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment server/src/main/scala/org/apache/livy/server/recovery/ZooKeeperManager.scala:149 β€” // TODO Make sure ZK path has proper secure permissions so that other users cannot read its β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala:663 β€” // TODO: don't block indefinitely? β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:408 β€” // TODO: need a better exception for this. β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment rsc/src/main/java/org/apache/livy/rsc/RSCConf.java:116 β€” // TODO: add more options? β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment integration-test/src/test/scala/org/apache/livy/test/InteractiveIT.scala:77 β€” // TODO separate all these checks to different sub tests after merging new IT code. β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment integration-test/src/main/scala/org/apache/livy/test/framework/LivyRestClient.scala:50 β€” // TODO Define these in production code and share them with test code. β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment client-http/src/main/java/org/apache/livy/client/http/JobHandleImpl.java:244 β€” // TODO: better exception. β€” source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D31 Β· IaC & Container Security Β· Medium IaC Β· Γ—14
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 Β· Dependency Vulnerabilities Β· Medium CVE Β· Γ—10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC6 Β· Visual & motion safety Β· Focus outline removed in CSS without a Β· Γ—8
  • Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/css/style.css:125 β€” `.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.
  • Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:2275 β€” `.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.
  • Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3476 β€” `.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.
  • Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3535 β€” `.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.
  • Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3558 β€” `.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.
  • Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3654 β€” `.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.
  • Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:3735 β€” `.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.
  • Focus outline removed in CSS without a :focus replacement docs/assets/themes/apache/bootstrap/css/bootstrap.css:6026 β€” `.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.
AC6 Β· Visual & motion safety Β· Low contrast colour pair in CSS (3.6 Β· Γ—5
  • Low contrast colour pair in CSS (3.6:1) docs/assets/themes/apache/bootstrap/css/bootstrap.css:3531 β€” `.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.
  • Low contrast colour pair in CSS (3.6:1) docs/assets/themes/apache/bootstrap/css/bootstrap.css:4221 β€” `.nav-pills > li.active > a, .nav-pills > li.active > a:hover, .nav-pills > li.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.
  • Low contrast colour pair in CSS (3.6:1) docs/assets/themes/apache/bootstrap/css/bootstrap.css:4989 β€” `.pagination > .active > a, .pagination > .active > span, .pagination > .active > a:hover, .pagination > .active > span:hover, .pagination > .active > a:focus, .pagination > .active > span: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.
  • Low contrast colour pair in CSS (3.6:1) docs/assets/themes/apache/bootstrap/css/bootstrap.css:5220 β€” `a.list-group-item.active > .badge, .nav-pills > .active > a > .badge` sets color: #428bca on background-color: #ffffff β€” 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.6:1) docs/assets/themes/apache/bootstrap/css/bootstrap.css:5595 β€” `a.list-group-item.active, a.list-group-item.active:hover, a.list-group-item.active: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.
AC6 Β· Visual & motion safety Β· Animation without a prefers-reduced-motion guard Β· Γ—5
  • Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:2634 β€” `.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.
  • Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:5450 β€” `.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.
  • Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:5463 β€” `.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.
  • Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:6002 β€” `.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.
  • Animation without a prefers-reduced-motion guard docs/assets/themes/apache/bootstrap/css/bootstrap.css:6389 β€” `.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.
GD1 Β· Unfinished & placeholder code Β· Unfinished stub Β· Γ—5
  • Unfinished stub β€” body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:357 β€” `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.
  • Unfinished stub β€” body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:366 β€” `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.
  • Unfinished stub β€” body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:370 β€” `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.
  • Unfinished stub β€” body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:377 β€” `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.
  • Unfinished stub β€” body is a "not implemented" error thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:385 β€” `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.
IC1 Β· Incompleteness & stubs Β· Unfinished stub Β· Γ—5
  • Unfinished stub β€” throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:357 β€” `getDelegationToken` throws an exception whose message says it isn't finished β€” a not-implemented stub wearing an ordinary exception. Implement it or remove it.
  • Unfinished stub β€” throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:366 β€” `setApplicationName` throws an exception whose message says it isn't finished β€” a not-implemented stub wearing an ordinary exception. Implement it or remove it.
  • Unfinished stub β€” throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:370 β€” `cancelDelegationToken` throws an exception whose message says it isn't finished β€” a not-implemented stub wearing an ordinary exception. Implement it or remove it.
  • Unfinished stub β€” throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:377 β€” `renewDelegationToken` throws an exception whose message says it isn't finished β€” a not-implemented stub wearing an ordinary exception. Implement it or remove it.
  • Unfinished stub β€” throws a "not implemented" exception thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:385 β€” `getQueryId` throws an exception whose message says it isn't finished β€” a not-implemented stub wearing an ordinary exception. Implement it or remove it.
X3 Β· Exception handling Β· Swallowed exception (empty catch) Β· Γ—4
  • Swallowed exception (empty catch) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThreadPoolExecutorWithOomHook.scala:48 β€” 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.
  • Swallowed exception (empty catch) server/src/main/scala/org/apache/livy/server/recovery/FileSystemStateStore.scala:107 β€” 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.
  • Swallowed exception (empty catch) REDACTED:170 β€” 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.
  • Swallowed exception (empty catch) client-http/src/main/java/org/apache/livy/client/http/HttpClient.java:122 β€” 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.
X3 Β· Exception handling Β· Swallowed exception (caught, then discarded) Β· Γ—4
  • Swallowed exception (caught, then discarded) server/src/main/scala/org/apache/livy/package.scala:54 β€” `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.
  • Swallowed exception (caught, then discarded) server/src/main/scala/org/apache/livy/server/LivySessionMetrics.scala:57 β€” `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.
  • Swallowed exception (caught, then discarded) REDACTED:154 β€” `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.
  • Swallowed exception (caught, then discarded) repl/scala-2.13/src/main/scala/org/apache/livy/repl/SparkInterpreter.scala:144 β€” `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.
D3 Β· God Classes Β· FileTooLong Β· Γ—3
  • FileTooLong: utils/SparkKubernetesApp.scala server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala β€” FileTooLong β€” 676 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 176 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: cli/ThriftCLIService.scala thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala β€” FileTooLong β€” 568 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ThriftCLIService (50-752). The bar is 500 significant lines; this is 68 over it, 1.14× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β€” the parts that share the same inputs and are named together β€” into its own unit in a sibling file, and have the original call them.
  • FileTooLong: interactive/InteractiveSession.scala server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala β€” FileTooLong β€” 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D29 Β· Static Analysis (SAST) Β· REDACTED
  • REDACTED
  • REDACTED
D36 Β· Supply-chain Provenance & Signing Β· REDACTED
  • REDACTED
  • REDACTED
D4 Β· Code Duplication Β· Edited copy of a member (12 corresponding lines) Β· Γ—2
  • Edited copy of a member (12 corresponding lines) rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:615 β€” rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:615-626 | rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:337-351 β€” These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below β€” the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain β€” factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftBinaryCLIService.scala:165 β€” thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftBinaryCLIService.scala:165-176 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpCLIService.scala:159-170 β€” These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below β€” the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain β€” factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D6 Β· Cohesion (LCOM4) Β· Low cohesion Β· Γ—2
  • Low cohesion: PythonInterpreter (LCOM4 5) repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:217 β€” PythonInterpreter's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable β€” your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected β€” and which would otherwise dominate this list β€” are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SessionServlet (LCOM4 4) server/src/main/scala/org/apache/livy/server/SessionServlet.scala:42 β€” SessionServlet's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable β€” your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected β€” and which would otherwise dominate this list β€” are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
AC6 Β· Visual & motion safety Β· Low contrast colour pair in CSS (3.4 Β· Γ—1
  • Low contrast colour pair in CSS (3.4:1) docs/assets/themes/apache/css/style.css:46 β€” `.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.
AC6 Β· Visual & motion safety Β· Low contrast colour pair in CSS (2.9 Β· Γ—1
  • Low contrast colour pair in CSS (2.9:1) docs/assets/themes/apache/css/style.css:326 β€” `.tag_box a.active` sets color: #FFF on background-color: #57A957 β€” 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 Β· Cyclomatic Complexity Β· InteractiveSession.prepareBuilderProp (cyclomatic 27) Β· Γ—1
  • InteractiveSession.prepareBuilderProp (cyclomatic 27) server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala:211 β€” InteractiveSession.prepareBuilderProp has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 Β· Cyclomatic Complexity Β· LivyServer.start (cyclomatic 21) Β· Γ—1
  • LivyServer.start (cyclomatic 21) server/src/main/scala/org/apache/livy/server/LivyServer.scala:67 β€” LivyServer.start has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 Β· Cyclomatic Complexity Β· ColumnBuffer.ensureCapacity (cyclomatic 19) Β· Γ—1
  • ColumnBuffer.ensureCapacity (cyclomatic 19) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:359 β€” ColumnBuffer.ensureCapacity has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 Β· Cyclomatic Complexity Β· ColumnBuffer.getValues (cyclomatic 18) Β· Γ—1
  • ColumnBuffer.getValues (cyclomatic 18) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:212 β€” ColumnBuffer.getValues has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 Β· Cyclomatic Complexity Β· AbstractSparkInterpreter.executeLines (cyclomatic 17) Β· Γ—1
  • AbstractSparkInterpreter.executeLines (cyclomatic 17) repl/src/main/scala/org/apache/livy/repl/AbstractSparkInterpreter.scala:255 β€” AbstractSparkInterpreter.executeLines has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 Β· Cyclomatic Complexity Β· LivyThriftSessionManager.processSessionConf (cyclomatic 17) Β· Γ—1
  • LivyThriftSessionManager.processSessionConf (cyclomatic 17) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:594 β€” LivyThriftSessionManager.processSessionConf has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform β€” the same kind of value, with no behaviour of its own β€” a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 Β· Cyclomatic Complexity Β· SparkUtils.toJavaSQLType (cyclomatic 17) Β· Γ—1
  • SparkUtils.toJavaSQLType (cyclomatic 17) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/SparkUtils.java:113 β€” SparkUtils.toJavaSQLType has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 Β· Cyclomatic Complexity Β· ThriftHttpServlet.doPost (cyclomatic 16) Β· Γ—1
  • ThriftHttpServlet.doPost (cyclomatic 16) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpServlet.scala:76 β€” ThriftHttpServlet.doPost has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D15 Β· Churn × Complexity Hotspots Β· Hotspot Β· Γ—1
  • Hotspot: server/src/main/scala/org/apache/livy/server/LivyServer.scala server/src/main/scala/org/apache/livy/server/LivyServer.scala:67 β€” server/src/main/scala/org/apache/livy/server/LivyServer.scala changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in LivyServer.start at line 67. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-22..2026-10-20, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-22 12:53:15 -04:00' --until='2026-10-20 12:53:15 -04:00' --full-history --no-merges -- server/src/main/scala/org/apache/livy/server/LivyServer.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each β€” a difference of several commits on a file whose history was re-landed or reverted inside the window.
D17 Β· Explicit Debt Β· HackComment Β· Γ—1
  • HackComment client-http/src/test/scala/org/apache/livy/client/http/HttpClientSpec.scala:256 β€” // Hack warning: keep the session object available so that individual tests can mock β€” a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 Β· Cognitive Complexity Β· InteractiveSession.prepareBuilderProp (cognitive 42) Β· Γ—1
  • InteractiveSession.prepareBuilderProp (cognitive 42) server/src/main/scala/org/apache/livy/server/interactive/InteractiveSession.scala:211 β€” InteractiveSession.prepareBuilderProp has cognitive complexity 42 (threshold 15). Drivers by points: if/else 29 (34 pts), match/switch 4 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth β€” checks laid out side by side rather than stacked β€” so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 Β· Cognitive Complexity Β· AbstractSparkInterpreter.executeLines (cognitive 30) Β· Γ—1
  • AbstractSparkInterpreter.executeLines (cognitive 30) repl/src/main/scala/org/apache/livy/repl/AbstractSparkInterpreter.scala:255 β€” AbstractSparkInterpreter.executeLines has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 5 (13 pts), boolean chains 2 (nesting depth added 15). The drivers above price the dispatch low by construction β€” a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full β€” so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 Β· Cognitive Complexity Β· SessionManager.collectGarbage (cognitive 29) Β· Γ—1
  • SessionManager.collectGarbage (cognitive 29) server/src/main/scala/org/apache/livy/sessions/SessionManager.scala:171 β€” SessionManager.collectGarbage has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 2, match/switch 2 (nesting depth added 13). The drivers above price the dispatch low by construction β€” a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full β€” so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 Β· Cognitive Complexity Β· CreateInteractiveRequest.toString (cognitive 28) Β· Γ—1
  • CreateInteractiveRequest.toString (cognitive 28) server/src/main/scala/org/apache/livy/server/interactive/CreateInteractiveRequest.scala:41 β€” CreateInteractiveRequest.toString has cognitive complexity 28 (threshold 15). Drivers by points: if/else 28. To reduce it, split the body: this score is breadth rather than depth β€” many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 Β· Cognitive Complexity Β· CreateBatchRequest.toString (cognitive 26) Β· Γ—1
  • CreateBatchRequest.toString (cognitive 26) server/src/main/scala/org/apache/livy/server/batch/CreateBatchRequest.scala:39 β€” CreateBatchRequest.toString has cognitive complexity 26 (threshold 15). Drivers by points: if/else 26. To reduce it, split the body: this score is breadth rather than depth β€” many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 Β· Cognitive Complexity Β· ThriftHttpServlet.doPost (cognitive 26) Β· Γ—1
  • ThriftHttpServlet.doPost (cognitive 26) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpServlet.scala:76 β€” ThriftHttpServlet.doPost has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· ContextLauncher.startDriver (cognitive 25) Β· Γ—1
  • ContextLauncher.startDriver (cognitive 25) rsc/src/main/java/org/apache/livy/rsc/ContextLauncher.java:155 β€” ContextLauncher.startDriver has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 2 (6 pts), boolean chains 1, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· GetColumnsJob.fetchCatalogObjects (cognitive 25) Β· Γ—1
  • GetColumnsJob.fetchCatalogObjects (cognitive 25) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/GetColumnsJob.java:51 β€” GetColumnsJob.fetchCatalogObjects has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 3 (15 pts), loops 3 (6 pts), if/else 1 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· LivyThriftSessionManager.startTimeoutChecker (cognitive 24) Β· Γ—1
  • LivyThriftSessionManager.startTimeoutChecker (cognitive 24) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:358 β€” LivyThriftSessionManager.startTimeoutChecker has cognitive complexity 24 (threshold 15). Drivers by points: error handling 3 (10 pts), if/else 3 (8 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· fake_shell.magic_table (cognitive 24) Β· Γ—1
  • fake_shell.magic_table (cognitive 24) REDACTED:393 β€” fake_shell.magic_table has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), error handling 2 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· LivyServer.start (cognitive 23) Β· Γ—1
  • LivyServer.start (cognitive 23) server/src/main/scala/org/apache/livy/server/LivyServer.scala:67 β€” LivyServer.start has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (18 pts), match/switch 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth β€” checks laid out side by side rather than stacked β€” so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 Β· Cognitive Complexity Β· fake_shell.main (cognitive 22) Β· Γ—1
  • fake_shell.main (cognitive 22) REDACTED:508 β€” fake_shell.main has cognitive complexity 22 (threshold 15). Drivers by points: error handling 7 (14 pts), if/else 4 (6 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· merge_livy_pr.resolve_jira_issue (cognitive 21) Β· Γ—1
  • merge_livy_pr.resolve_jira_issue (cognitive 21) REDACTED:230 β€” merge_livy_pr.resolve_jira_issue has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· ThriftBinaryCLIService.initServer (cognitive 19) Β· Γ—1
  • ThriftBinaryCLIService.initServer (cognitive 19) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftBinaryCLIService.scala:47 β€” ThriftBinaryCLIService.initServer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· SparkEntries.sparkSession (cognitive 19) Β· Γ—1
  • SparkEntries.sparkSession (cognitive 19) rsc/src/main/java/org/apache/livy/rsc/driver/SparkEntries.java:61 β€” SparkEntries.sparkSession has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 1 (4 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth β€” most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 Β· Cognitive Complexity Β· ColumnBuffer.ensureCapacity (cognitive 19) Β· Γ—1
  • ColumnBuffer.ensureCapacity (cognitive 19) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:359 β€” ColumnBuffer.ensureCapacity has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction β€” a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full β€” so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 Β· Cognitive Complexity Β· merge_livy_pr.main (cognitive 19) Β· Γ—1
  • merge_livy_pr.main (cognitive 19) REDACTED:352 β€” merge_livy_pr.main has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth β€” checks laid out side by side rather than stacked β€” so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 Β· Cognitive Complexity Β· fake_shell.parse_code_into_nodes (cognitive 19) Β· Γ—1
  • fake_shell.parse_code_into_nodes (cognitive 19) REDACTED:244 β€” fake_shell.parse_code_into_nodes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· LivyThriftSessionManager.incrementConnections (cognitive 18) Β· Γ—1
  • LivyThriftSessionManager.incrementConnections (cognitive 18) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:482 β€” LivyThriftSessionManager.incrementConnections has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (18 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· LivyClientBuilder.build (cognitive 18) Β· Γ—1
  • LivyClientBuilder.build (cognitive 18) api/src/main/java/org/apache/livy/LivyClientBuilder.java:120 β€” LivyClientBuilder.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 3 (6 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· RSCClient.stop (cognitive 18) Β· Γ—1
  • RSCClient.stop (cognitive 18) rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:213 β€” RSCClient.stop has cognitive complexity 18 (threshold 15). Drivers by points: error handling 3 (8 pts), if/else 4 (7 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· SparkKubernetesApp.monitorSparkKubernetesApp (cognitive 17) Β· Γ—1
  • SparkKubernetesApp.monitorSparkKubernetesApp (cognitive 17) server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:350 β€” SparkKubernetesApp.monitorSparkKubernetesApp has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), error handling 4 (5 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth β€” checks laid out side by side rather than stacked β€” so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 Β· Cognitive Complexity Β· LivyThriftSessionManager.getOrCreateLivySession (cognitive 17) Β· Γ—1
  • LivyThriftSessionManager.getOrCreateLivySession (cognitive 17) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:161 β€” LivyThriftSessionManager.getOrCreateLivySession has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 4 (8 pts) (nesting depth added 9). The drivers above price the dispatch low by construction β€” a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full β€” so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 Β· Cognitive Complexity Β· SparkUtils.toJavaSQLType (cognitive 17) Β· Γ—1
  • SparkUtils.toJavaSQLType (cognitive 17) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/SparkUtils.java:113 β€” SparkUtils.toJavaSQLType has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. To reduce it, split the body: this score is breadth rather than depth β€” many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 Β· Cognitive Complexity Β· TUGIAssumingProcessor.process (cognitive 16) Β· Γ—1
  • TUGIAssumingProcessor.process (cognitive 16) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthBridgeServer.scala:217 β€” TUGIAssumingProcessor.process has cognitive complexity 16 (threshold 15). Drivers by points: error handling 7 (10 pts), if/else 6 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· PlainSaslServer.evaluateResponse (cognitive 16) Β· Γ—1
  • PlainSaslServer.evaluateResponse (cognitive 16) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/PlainSaslServer.scala:50 β€” PlainSaslServer.evaluateResponse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 3, error handling 3, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth β€” many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 Β· Cognitive Complexity Β· JobHandleImpl.get (cognitive 16) Β· Γ—1
  • JobHandleImpl.get (cognitive 16) client-http/src/main/java/org/apache/livy/client/http/JobHandleImpl.java:173 β€” JobHandleImpl.get has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 Β· Cognitive Complexity Β· ColumnBuffer.getValues (cognitive 16) Β· Γ—1
  • ColumnBuffer.getValues (cognitive 16) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:212 β€” ColumnBuffer.getValues has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (15 pts), match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 Β· Static Analysis (SAST) Β· REDACTED Β· Γ—1
  • REDACTED
D3 Β· God Classes Β· TooManyMethods Β· Γ—1
  • TooManyMethods: LivyCLIService thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:36 β€” TooManyMethods β€” 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D36 Β· Supply-chain Provenance & Signing Β· REDACTED Β· Γ—1
  • REDACTED
D36 Β· Supply-chain Provenance & Signing Β· REDACTED Β· Γ—1
  • REDACTED
D4 Β· Code Duplication Β· Edited copy of a member (17 corresponding lines) Β· Γ—1
  • Edited copy of a member (17 corresponding lines) server/src/main/scala/org/apache/livy/server/batch/CreateBatchRequest.scala:39 β€” server/src/main/scala/org/apache/livy/server/batch/CreateBatchRequest.scala:39-55 | server/src/main/scala/org/apache/livy/server/interactive/CreateInteractiveRequest.scala:41-58 β€” These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below β€” the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain β€” factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 Β· Code Duplication Β· Edited copies of one member (3 members, 17+ corresponding lines) Β· Γ—1
  • Edited copies of one member (3 members, 17+ corresponding lines) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:132 β€” thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:132-151 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:154-170 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:173-189 β€” These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 Β· Code Duplication Β· Edited copies of one member (4 members, 16+ corresponding lines) Β· Γ—1
  • Edited copies of one member (4 members, 16+ corresponding lines) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/operation/GetColumnsOperation.scala:37 β€” thriftserver/server/src/main/scala/org/apache/livy/thriftserver/operation/GetColumnsOperation.scala:37-55 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/operation/GetFunctionsOperation.scala:36-53 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/operation/GetSchemasOperation.scala:35-50 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/operation/GetTablesOperation.scala:37-55 β€” These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 Β· Code Duplication Β· Edited copy of a member (15 corresponding lines) Β· Γ—1
  • Edited copy of a member (15 corresponding lines) repl/src/main/scala/org/apache/livy/repl/ReplDriver.scala:106 β€” repl/src/main/scala/org/apache/livy/repl/ReplDriver.scala:106-120 | repl/src/main/scala/org/apache/livy/repl/ReplDriver.scala:122-142 β€” These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below β€” the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain β€” factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 Β· Code Duplication Β· Edited copies of one member (7 members, 13+ corresponding lines) Β· Γ—1
  • Edited copies of one member (7 members, 13+ corresponding lines) thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:426 β€” thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:426-438 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:441-454 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:457-474 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:477-489 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:492-509 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:512-528 | thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:640-656 β€” These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 Β· Code Duplication Β· Edited copy of a member (4 corresponding lines) Β· Γ—1
  • Edited copy of a member (4 corresponding lines) server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:492 β€” server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:492-496 | server/src/main/scala/org/apache/livy/utils/SparkYarnApp.scala:244-247 β€” These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below β€” the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain β€” factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 Β· Code Duplication Β· Duplicated block (7–8 lines × 2) Β· Γ—1
  • Duplicated block (7–8 lines × 2) thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/GetColumnsJob.java:53 β€” thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/GetColumnsJob.java:53-60 | thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/GetTablesJob.java:57-63 β€” the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach β€” a file they already depend on, or a new one alongside them β€” and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/GetColumnsJob.java:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand β€” widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 Β· Code Duplication Β· Duplicated block (6 lines × 2) Β· Γ—1
  • Duplicated block (6 lines × 2) rsc/src/main/java/org/apache/livy/rsc/driver/SparkEntries.java:71 β€” rsc/src/main/java/org/apache/livy/rsc/driver/SparkEntries.java:71-76 | rsc/src/main/java/org/apache/livy/rsc/driver/SparkEntries.java:117-122 β€” both copies are in the same file, so extract the block into one function there and call it from each site β€” the copies drift apart the first time only one of them is edited.
P12 Β· CI test-gate honesty Β· Coverage collected but not gated Β· Γ—1
  • Coverage collected but not gated β€” CI collects a coverage report but no step enforces a minimum β€” coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration β€” the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited β€” matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
R1 Β· Type Safety Β· Type Safety Β· Γ—1
  • 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.
X1 Β· Async correctness Β· Future started here is not kept Β· Γ—1
  • Future started here is not kept repl/src/main/scala/org/apache/livy/repl/Session.scala:163 β€” 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.
X18 Β· Disposal-pattern correctness Β· Owned disposable field is never released Β· Γ—1
  • Owned disposable field is never released server/src/main/scala/org/apache/livy/server/LivyServer.scala:109 β€” `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.
X18 Β· Disposal-pattern correctness Β· Disposable created and abandoned in the function that made it Β· Γ—1
  • Disposable created and abandoned in the function that made it repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:89 β€” `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`.
Minor β€” 130 finding(s)
D34 Β· Knowledge Freshness Β· Orphaned file Β· Γ—89
  • Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyCLIService.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file repl/src/main/scala/org/apache/livy/repl/AbstractSparkInterpreter.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file repl/src/main/scala/org/apache/livy/repl/SparkRInterpreter.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthBridgeServer.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/ColumnBuffer.java:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyOperationManager.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftBinaryCLIService.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file client-common/src/main/java/org/apache/livy/client/common/ClientConf.java:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpCLIService.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file server/src/main/scala/org/apache/livy/server/SessionServlet.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file client-http/src/main/java/org/apache/livy/client/http/JobHandleImpl.java:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file scala-api/src/main/scala/org/apache/livy/scalaapi/ScalaJobHandle.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyExecuteStatementOperation.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/AuthFactory.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file server/src/main/scala/org/apache/livy/utils/LivySparkUtils.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/session/src/main/java/org/apache/livy/thriftserver/session/SparkUtils.java:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file server/src/main/scala/org/apache/livy/utils/SparkProcessBuilder.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/auth/PlainSaslServer.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file server/src/main/scala/org/apache/livy/server/recovery/FileSystemStateStore.scala:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file rsc/src/main/java/org/apache/livy/rsc/driver/SparkEntries.java:1 β€” No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 64 more in this group β€” see findings.md.
X4 Β· Structured logging Β· Interpolated log message defeats structured logging Β· Γ—16
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/RSCClient.java:247 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:301 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:318 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:334 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:380 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:382 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:97 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:105 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:126 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/rpc/RpcServer.java:129 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/driver/JobWrapper.java:70 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:283 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:319 β€” `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.
  • Interpolated log message defeats structured logging rsc/src/main/java/org/apache/livy/rsc/driver/RSCDriver.java:520 β€” `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.
  • Interpolated log message defeats structured logging client-common/src/main/java/org/apache/livy/client/common/ClientConf.java:225 β€” `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.
  • Interpolated log message defeats structured logging client-common/src/main/java/org/apache/livy/client/common/ClientConf.java:233 β€” `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.
X10 Β· Duplicated predicate Β· Duplicated predicate Β· Γ—4
  • Duplicated predicate server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:489 β€” `process.isDefined && !process.get.isAlive && process.get.exitValue() != 0` appears character-identically in 2 files β€” server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala, server/src/main/scala/org/apache/livy/utils/SparkYarnApp.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala:493 β€” `state != SparkApp.State.FAILED && state != SparkApp.State.FINISHED && state != SparkApp.State.KILLED` appears character-identically in 2 files β€” server/src/main/scala/org/apache/livy/utils/SparkKubernetesApp.scala, server/src/main/scala/org/apache/livy/utils/SparkYarnApp.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala:104 β€” `sys.env.getOrElse("SPARK_YARN_MODE", "") == "true" || (conf.get("spark.master", "").toLowerCase == "yarn" && conf.get("spark.submit.deployMo…` appears character-identically in 2 files β€” repl/src/main/scala/org/apache/livy/repl/PythonInterpreter.scala, repl/src/main/scala/org/apache/livy/repl/SparkRInterpreter.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate repl/scala-2.12/src/main/scala/org/apache/livy/repl/SparkInterpreter.scala:69 β€” `u.getProtocol == "file" && new File(u.getPath).isFile` appears character-identically in 2 files β€” repl/scala-2.12/src/main/scala/org/apache/livy/repl/SparkInterpreter.scala, repl/scala-2.13/src/main/scala/org/apache/livy/repl/SparkInterpreter.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D34 Β· Knowledge Freshness Β· Most significant orphaned file Β· Γ—3
  • Most significant orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftCLIService.scala:1 β€” One of the orphaned files carrying the most lost knowledge β€” ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file thriftserver/server/src/main/scala/org/apache/livy/thriftserver/LivyThriftSessionManager.scala:1 β€” One of the orphaned files carrying the most lost knowledge β€” ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file rsc/src/main/java/org/apache/livy/rsc/rpc/Rpc.java:1 β€” One of the orphaned files carrying the most lost knowledge β€” ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D16 Β· Bus Factor Β· Off-boarding risk Β· Γ—1
  • Off-boarding risk: anonymized user #1 β€” If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: thriftserver/server/src/main/scala/org/apache/livy/thriftserver/cli/ThriftHttpServlet.scala, client-http/src/main/java/org/apache/livy/client/http/LivyConnection.java, server/src/main/scala/org/apache/livy/server/auth/LdapAuthenticationHandlerImpl.scala. Pair on, review, or document these before any departure.
D16 Β· Bus Factor Β· Further sole-owners (lower concentration) Β· Γ—1
  • Further sole-owners (lower concentration) β€” 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold β€” folded into the bus-factor score and metrics (5 single-owned of 53 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 53 of the 183 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) β€” spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: server/src/main/scala/org/apache/livy/server/LivySessionMetrics.scala, server/src/main/scala/org/apache/livy/server/recovery/RecoveryServlet.scala.
D20 Β· ADR Quality Β· No ADRs found Β· Γ—1
  • No ADRs found REDACTED:370 β€” No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these β€” unnumbered files outside any recognised directory, without those headings β€” is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `REDACTED` makes this repository a deployable product (line 370).
D29 Β· Static Analysis (SAST) Β· REDACTED Β· Γ—1
  • REDACTED
D34 Β· Knowledge Freshness Β· Concentrated knowledge decay Β· Γ—1
  • Concentrated knowledge decay β€” 92 of 119 significant files have no living knowledge, while the repository is still being changed at a low rate (25 commit(s) in the last 90 days) β€” so this is one repo-wide knowledge-decay state, not 92 separate risks. 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. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
D36 Β· Supply-chain Provenance & Signing Β· REDACTED Β· Γ—1
  • REDACTED
D36 Β· Supply-chain Provenance & Signing Β· REDACTED Β· Γ—1
  • REDACTED
D36 Β· Supply-chain Provenance & Signing Β· REDACTED Β· Γ—1
  • REDACTED
D40 Β· Network Egress Confinement Β· No network policy Β· Γ—1
  • No network policy β€” No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
IC1 Β· Incompleteness & stubs Β· Disabled test Β· Γ—1
  • Disabled test integration-test/src/test/scala/org/apache/livy/test/JobApiIT.scala:138 β€” A test is skipped/ignored β€” coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
M2 Β· Architecture documentation Β· No ADRs Β· Γ—1
  • No ADRs β€” 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.
M2 Β· Architecture documentation Β· No architecture diagram/doc Β· Γ—1
  • No architecture diagram/doc β€” 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.
P2 Β· Observability Β· Logging is not universal Β· Γ—1
  • Logging is not universal β€” 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`.
P4 Β· Deployment & Rollback Β· No rollback/health safety Β· Γ—1
  • No rollback/health safety β€” 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.
P6 Β· Release Hygiene Β· No changelog Β· Γ—1
  • No changelog β€” 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.)
S1 Β· Web-Security Posture Β· Secure cookie flags not detected Β· Γ—1
  • Secure cookie flags not detected β€” 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.)
X5 Β· Nullable reference types Β· Scala's null is not held to the type system everywhere Β· Γ—1
  • Scala's null is not held to the type system everywhere β€” 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.
X7 Β· Silent fallback defaults Β· Silent fallback default in catch Β· Γ—1
  • Silent fallback default in catch server/src/main/scala/org/apache/livy/server/LivySessionMetrics.scala:57 β€” `getValue` (in `register`) swallows every exception into `0` β€” a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch case or in the Scaladoc, and the row stops firing.
Minor β€” 2 finding(s)
D12 Β· Dependency Hygiene Β· Outdated Β· Γ—2
  • Outdated: github-pages β€” `github-pages` is resolved to 142 in the committed Gemfile.lock but 233 is the current release on rubygems.org, and docs/Gemfile declares no version requirement for it, so nothing but the lockfile is holding it back. This build is therefore missing every fix published since, including any security fix. This crosses a major version, so read the changelog before taking it. Run `bundle update github-pages` and commit the updated Gemfile.lock.
  • Outdated: rouge β€” `rouge` is resolved to 1.11.1 in the committed Gemfile.lock but 5.1.0 is the current release on rubygems.org, and docs/Gemfile declares no version requirement for it, so nothing but the lockfile is holding it back. This build is therefore missing every fix published since, including any security fix. This crosses a major version, so read the changelog before taking it. Run `bundle update rouge` and commit the updated Gemfile.lock.

Appendix B β€” Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension β€” the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative β€” never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json β€” kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 Β· Secrets (history)gitleaksβ€”gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c702b35d115b482d9b7c487c8bd55b16/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 Β· Secrets (history)gitleaksβ€”gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c702b35d115b482d9b7c487c8bd55b16/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 Β· Static Analysis (SAST)semgrepβ€”semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude docs/assets/themes/apache/jquery .17artifacts/raw/semgrep.json
D30 Β· Dependency Vulnerabilitiesosv-scannerβ€”osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .27artifacts/raw/osv-scanner.json
D31 Β· IaC & Container Securitytrivyβ€”trivy config --format json --quiet .17artifacts/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 Policydisclosureβ€”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 Enforcementruntime-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 Dependenciesosv-scannerβ€”osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1da79-e6cc-7b72-aa04-1676c5e1626a Β· every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric β€” drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md