Executive summary
AbsaOSS/spline falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 51 out of 100 and is rated Adequate, and ten of its 11 critical findings are security problems.
Production Readiness, at 39, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 7 points. Having someone learn and document the 70 files no active contributor knows comes next, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 59.
Four known security holes in the packages the code depends on can be used by attackers. Four 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. Switching the validation back on would fix the two security checks on connections or logins switched off. The loop of files that import each other needs breaking.
The product code is 13,788 lines, about €17,000 to rebuild.
If Production Readiness rose from 39 to 70, the lowest score rated Strong, the score would rise from 51 to about 59.
New since the last survey: 7 findings
- Code Duplication · Edited copy of a member (79 corresponding lines) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala
- Code Duplication · Edited copy of a member (53 corresponding lines) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/AttrOrExprRef.scala
- Code Duplication · Edited copy of a member (21 corresponding lines) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/LabelRepositoryImpl.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) consumer-rest-core/src/main/scala/za/co/absa/spline/consumer/rest/controller/DataSourcesController.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) test-data-generator/src/main/scala/za/co/absa/spline/testdatagen/generators/Graph.scala
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 21 findings
- Code Duplication · Duplicated block (6 lines × 2) admin/src/main/scala/za/co/absa/spline/admin/AdminCLI.scala
- Code Duplication · Duplicated block (6 lines × 2) admin/src/main/scala/za/co/absa/spline/admin/AdminCLI.scala
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] commons/pom.xml
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,600 to €28,000, for 93 to 294 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 13,788 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 arangodb-foxx-services.src.main.persistence.model | 2 arangodb-foxx-services.src.main.services.txm.tx-manager | 3 za.co.absa.spline.common.AsyncCallRetryer | 4 za.co.absa.spline.common.graph.GraphImplicits | 5 za.co.absa.spline.common.rest | 6 za.co.absa.spline.consumer.service.model.ExpressionEdge | 7 za.co.absa.spline.gateway.kafka.listener.handler | 8 za.co.absa.spline.persistence | 9 za.co.absa.spline.persistence.model | 10 za.co.absa.spline.producer.model.v1_1 | 11 za.co.absa.spline.producer.model.v1_2 | 12 arangodb-foxx-services.src.main.services | 13 arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator | 14 arangodb-foxx-services.src.main.services.txm.tx-manager-impl | 15 com.arangodb.internal | 16 za.co.absa.spline.arango | 17 za.co.absa.spline.arango.foxx | 18 za.co.absa.spline.common | 19 za.co.absa.spline.consumer.service.model | 20 za.co.absa.spline.producer.model.v1_1.OperationLike | 21 za.co.absa.spline.producer.model.v1_2.OperationLike | 22 za.co.absa.spline.producer.modelmapper | 23 za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 | 24 za.co.absa.spline.producer.service.model | 25 za.co.absa.spline.producer.service.repo | 26 za.co.absa.spline.admin | 27 za.co.absa.spline.arango.AuxiliaryDBAction | 28 za.co.absa.spline.arango.OnDBExistsAction | 29 za.co.absa.spline.consumer.rest.controller.LineageDetailedController | 30 za.co.absa.spline.consumer.rest.controller.OperationDetailsController | 31 za.co.absa.spline.consumer.rest.model | 32 za.co.absa.spline.consumer.service.model.DataSourceActionType | 33 za.co.absa.spline.consumer.service.repo | 34 za.co.absa.spline.gateway.kafka.listener | 35 za.co.absa.spline.producer.modelmapper.v1_0 | 36 za.co.absa.spline.producer.rest.controller | 37 za.co.absa.spline.admin.AdminCLI | 38 za.co.absa.spline.admin.InputConsole | 39 za.co.absa.spline.consumer.rest.controller | 40 za.co.absa.spline.producer.modelmapper.v1_0.spark |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 arangodb-foxx-services.src.main.persistence.model | ||||||||||||||||||||||||||||||||||||||||
| 2 arangodb-foxx-services.src.main.services.txm.tx-manager | ||||||||||||||||||||||||||||||||||||||||
| 3 za.co.absa.spline.common.AsyncCallRetryer | ||||||||||||||||||||||||||||||||||||||||
| 4 za.co.absa.spline.common.graph.GraphImplicits | ||||||||||||||||||||||||||||||||||||||||
| 5 za.co.absa.spline.common.rest | ||||||||||||||||||||||||||||||||||||||||
| 6 za.co.absa.spline.consumer.service.model.ExpressionEdge | ||||||||||||||||||||||||||||||||||||||||
| 7 za.co.absa.spline.gateway.kafka.listener.handler | ||||||||||||||||||||||||||||||||||||||||
| 8 za.co.absa.spline.persistence | ||||||||||||||||||||||||||||||||||||||||
| 9 za.co.absa.spline.persistence.model | ||||||||||||||||||||||||||||||||||||||||
| 10 za.co.absa.spline.producer.model.v1_1 | ||||||||||||||||||||||||||||||||||||||||
| 11 za.co.absa.spline.producer.model.v1_2 | ||||||||||||||||||||||||||||||||||||||||
| 12 arangodb-foxx-services.src.main.services | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 arangodb-foxx-services.src.main.services.txm.tx-manager-impl | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 com.arangodb.internal | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 za.co.absa.spline.arango | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 za.co.absa.spline.arango.foxx | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 za.co.absa.spline.common | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 za.co.absa.spline.consumer.service.model | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 za.co.absa.spline.producer.model.v1_1.OperationLike | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 za.co.absa.spline.producer.model.v1_2.OperationLike | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 za.co.absa.spline.producer.modelmapper | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 za.co.absa.spline.producer.service.model | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 za.co.absa.spline.producer.service.repo | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 za.co.absa.spline.admin | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 27 za.co.absa.spline.arango.AuxiliaryDBAction | 8 | |||||||||||||||||||||||||||||||||||||||
| 28 za.co.absa.spline.arango.OnDBExistsAction | 3 | |||||||||||||||||||||||||||||||||||||||
| 29 za.co.absa.spline.consumer.rest.controller.LineageDetailedController | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 za.co.absa.spline.consumer.rest.controller.OperationDetailsController | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 za.co.absa.spline.consumer.rest.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 za.co.absa.spline.consumer.service.model.DataSourceActionType | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 za.co.absa.spline.consumer.service.repo | 26 | |||||||||||||||||||||||||||||||||||||||
| 34 za.co.absa.spline.gateway.kafka.listener | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 za.co.absa.spline.producer.modelmapper.v1_0 | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 za.co.absa.spline.producer.rest.controller | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 za.co.absa.spline.admin.AdminCLI | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 za.co.absa.spline.admin.InputConsole | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 za.co.absa.spline.consumer.rest.controller | 12 | 1 | 10 | |||||||||||||||||||||||||||||||||||||
| 40 za.co.absa.spline.producer.modelmapper.v1_0.spark | 2 | 8 |
12→1 arangodb-foxx-services.src.main.services uses arangodb-foxx-services.src.main.persistence.model✕
- Connections
- 1 pair of types, where a type in arangodb-foxx-services.src.main.services uses a type in arangodb-foxx-services.src.main.persistence.model.
- The types involved
arangodb-foxx-services.src.main.services.store→arangodb-foxx-services.src.main.persistence.model.CollectionName
- Direction
- arangodb-foxx-services.src.main.services uses arangodb-foxx-services.src.main.persistence.model, so a change to arangodb-foxx-services.src.main.persistence.model can break arangodb-foxx-services.src.main.services, while a change to arangodb-foxx-services.src.main.services can't break arangodb-foxx-services.src.main.persistence.model.
- Position
- Below the diagonal: arangodb-foxx-services.src.main.services uses a module listed above it, which is the healthy direction.
13→1 arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator uses arangodb-foxx-services.src.main.persistence.model✕
- Connections
- 1 pair of types, where a type in arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator uses a type in arangodb-foxx-services.src.main.persistence.model.
- The types involved
arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator.SubscribableTxManagerDecorator→arangodb-foxx-services.src.main.persistence.model.TxEvent
- Direction
- arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator uses arangodb-foxx-services.src.main.persistence.model, so a change to arangodb-foxx-services.src.main.persistence.model can break arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator, while a change to arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator can't break arangodb-foxx-services.src.main.persistence.model.
- Position
- Below the diagonal: arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator uses a module listed above it, which is the healthy direction.
13→2 arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator uses arangodb-foxx-services.src.main.services.txm.tx-manager✕
- Connections
- 1 pair of types, where a type in arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator uses a type in arangodb-foxx-services.src.main.services.txm.tx-manager.
- The types involved
arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator.SubscribableTxManagerDecorator→arangodb-foxx-services.src.main.services.txm.tx-manager.TxManager
- Direction
- arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator uses arangodb-foxx-services.src.main.services.txm.tx-manager, so a change to arangodb-foxx-services.src.main.services.txm.tx-manager can break arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator, while a change to arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator can't break arangodb-foxx-services.src.main.services.txm.tx-manager.
- Position
- Below the diagonal: arangodb-foxx-services.src.main.services.txm.subcribable-tx-manager-decorator uses a module listed above it, which is the healthy direction.
14→2 arangodb-foxx-services.src.main.services.txm.tx-manager-impl uses arangodb-foxx-services.src.main.services.txm.tx-manager✕
- Connections
- 1 pair of types, where a type in arangodb-foxx-services.src.main.services.txm.tx-manager-impl uses a type in arangodb-foxx-services.src.main.services.txm.tx-manager.
- The types involved
arangodb-foxx-services.src.main.services.txm.tx-manager-impl.TxManagerImpl→arangodb-foxx-services.src.main.services.txm.tx-manager.TxManager
- Direction
- arangodb-foxx-services.src.main.services.txm.tx-manager-impl uses arangodb-foxx-services.src.main.services.txm.tx-manager, so a change to arangodb-foxx-services.src.main.services.txm.tx-manager can break arangodb-foxx-services.src.main.services.txm.tx-manager-impl, while a change to arangodb-foxx-services.src.main.services.txm.tx-manager-impl can't break arangodb-foxx-services.src.main.services.txm.tx-manager.
- Position
- Below the diagonal: arangodb-foxx-services.src.main.services.txm.tx-manager-impl uses a module listed above it, which is the healthy direction.
15→5 com.arangodb.internal uses za.co.absa.spline.common.rest✕
- Connections
- 1 pair of types, where a type in com.arangodb.internal uses a type in za.co.absa.spline.common.rest.
- The types involved
com.arangodb.internal.InternalArangoDatabaseOps→za.co.absa.spline.common.rest.RESTClient
- Direction
- com.arangodb.internal uses za.co.absa.spline.common.rest, so a change to za.co.absa.spline.common.rest can break com.arangodb.internal, while a change to com.arangodb.internal can't break za.co.absa.spline.common.rest.
- Position
- Below the diagonal: com.arangodb.internal uses a module listed above it, which is the healthy direction.
16→8 za.co.absa.spline.arango uses za.co.absa.spline.persistence✕
- Connections
- 4 pairs of types, where a type in za.co.absa.spline.arango uses a type in za.co.absa.spline.persistence.
- The types involved
za.co.absa.spline.arango.ArangoManagerFactory→za.co.absa.spline.persistence.ArangoConnectionURLza.co.absa.spline.arango.ArangoManagerFactoryImpl→za.co.absa.spline.persistence.ArangoConnectionURLza.co.absa.spline.arango.ArangoManagerImpl→za.co.absa.spline.persistence.DryRunnableza.co.absa.spline.arango.DataRetentionManager→za.co.absa.spline.persistence.DryRunnable
- Direction
- za.co.absa.spline.arango uses za.co.absa.spline.persistence, so a change to za.co.absa.spline.persistence can break za.co.absa.spline.arango, while a change to za.co.absa.spline.arango can't break za.co.absa.spline.persistence.
- Position
- Below the diagonal: za.co.absa.spline.arango uses a module listed above it, which is the healthy direction.
16→9 za.co.absa.spline.arango uses za.co.absa.spline.persistence.model✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.arango uses a type in za.co.absa.spline.persistence.model.
- The types involved
za.co.absa.spline.arango.DatabaseCreateOptions→za.co.absa.spline.persistence.model.CollectionDef
- Direction
- za.co.absa.spline.arango uses za.co.absa.spline.persistence.model, so a change to za.co.absa.spline.persistence.model can break za.co.absa.spline.arango, while a change to za.co.absa.spline.arango can't break za.co.absa.spline.persistence.model.
- Position
- Below the diagonal: za.co.absa.spline.arango uses a module listed above it, which is the healthy direction.
17→8 za.co.absa.spline.arango.foxx uses za.co.absa.spline.persistence✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.arango.foxx uses a type in za.co.absa.spline.persistence.
- The types involved
za.co.absa.spline.arango.foxx.FoxxManagerImpl→za.co.absa.spline.persistence.DryRunnable
- Direction
- za.co.absa.spline.arango.foxx uses za.co.absa.spline.persistence, so a change to za.co.absa.spline.persistence can break za.co.absa.spline.arango.foxx, while a change to za.co.absa.spline.arango.foxx can't break za.co.absa.spline.persistence.
- Position
- Below the diagonal: za.co.absa.spline.arango.foxx uses a module listed above it, which is the healthy direction.
18→3 za.co.absa.spline.common uses za.co.absa.spline.common.AsyncCallRetryer✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.common uses a type in za.co.absa.spline.common.AsyncCallRetryer.
- The types involved
za.co.absa.spline.common.AsyncCallRetryer→za.co.absa.spline.common.AsyncCallRetryer.FailedAttempt
- Direction
- za.co.absa.spline.common uses za.co.absa.spline.common.AsyncCallRetryer, so a change to za.co.absa.spline.common.AsyncCallRetryer can break za.co.absa.spline.common, while a change to za.co.absa.spline.common can't break za.co.absa.spline.common.AsyncCallRetryer.
- Position
- Below the diagonal: za.co.absa.spline.common uses a module listed above it, which is the healthy direction.
19→6 za.co.absa.spline.consumer.service.model uses za.co.absa.spline.consumer.service.model.ExpressionEdge✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.consumer.service.model uses a type in za.co.absa.spline.consumer.service.model.ExpressionEdge.
- The types involved
za.co.absa.spline.consumer.service.model.ExpressionEdge→za.co.absa.spline.consumer.service.model.ExpressionEdge.ExpressionEdgeType
- Direction
- za.co.absa.spline.consumer.service.model uses za.co.absa.spline.consumer.service.model.ExpressionEdge, so a change to za.co.absa.spline.consumer.service.model.ExpressionEdge can break za.co.absa.spline.consumer.service.model, while a change to za.co.absa.spline.consumer.service.model can't break za.co.absa.spline.consumer.service.model.ExpressionEdge.
- Position
- Below the diagonal: za.co.absa.spline.consumer.service.model uses a module listed above it, which is the healthy direction.
19→9 za.co.absa.spline.consumer.service.model uses za.co.absa.spline.persistence.model✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.consumer.service.model uses a type in za.co.absa.spline.persistence.model.
- The types involved
za.co.absa.spline.consumer.service.model.ExpressionEdge→za.co.absa.spline.persistence.model.Edge
- Direction
- za.co.absa.spline.consumer.service.model uses za.co.absa.spline.persistence.model, so a change to za.co.absa.spline.persistence.model can break za.co.absa.spline.consumer.service.model, while a change to za.co.absa.spline.consumer.service.model can't break za.co.absa.spline.persistence.model.
- Position
- Below the diagonal: za.co.absa.spline.consumer.service.model uses a module listed above it, which is the healthy direction.
20→4 za.co.absa.spline.producer.model.v1_1.OperationLike uses za.co.absa.spline.common.graph.GraphImplicits✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.model.v1_1.OperationLike uses a type in za.co.absa.spline.common.graph.GraphImplicits.
- The types involved
za.co.absa.spline.producer.model.v1_1.OperationLike.OpNav→za.co.absa.spline.common.graph.GraphImplicits.DAGNodeIdMapping
- Direction
- za.co.absa.spline.producer.model.v1_1.OperationLike uses za.co.absa.spline.common.graph.GraphImplicits, so a change to za.co.absa.spline.common.graph.GraphImplicits can break za.co.absa.spline.producer.model.v1_1.OperationLike, while a change to za.co.absa.spline.producer.model.v1_1.OperationLike can't break za.co.absa.spline.common.graph.GraphImplicits.
- Position
- Below the diagonal: za.co.absa.spline.producer.model.v1_1.OperationLike uses a module listed above it, which is the healthy direction.
20→10 za.co.absa.spline.producer.model.v1_1.OperationLike uses za.co.absa.spline.producer.model.v1_1✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.model.v1_1.OperationLike uses a type in za.co.absa.spline.producer.model.v1_1.
- The types involved
za.co.absa.spline.producer.model.v1_1.OperationLike.OpNav→za.co.absa.spline.producer.model.v1_1.OperationLike
- Direction
- za.co.absa.spline.producer.model.v1_1.OperationLike uses za.co.absa.spline.producer.model.v1_1, so a change to za.co.absa.spline.producer.model.v1_1 can break za.co.absa.spline.producer.model.v1_1.OperationLike, while a change to za.co.absa.spline.producer.model.v1_1.OperationLike can't break za.co.absa.spline.producer.model.v1_1.
- Position
- Below the diagonal: za.co.absa.spline.producer.model.v1_1.OperationLike uses a module listed above it, which is the healthy direction.
21→4 za.co.absa.spline.producer.model.v1_2.OperationLike uses za.co.absa.spline.common.graph.GraphImplicits✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.model.v1_2.OperationLike uses a type in za.co.absa.spline.common.graph.GraphImplicits.
- The types involved
za.co.absa.spline.producer.model.v1_2.OperationLike.OpNav→za.co.absa.spline.common.graph.GraphImplicits.DAGNodeIdMapping
- Direction
- za.co.absa.spline.producer.model.v1_2.OperationLike uses za.co.absa.spline.common.graph.GraphImplicits, so a change to za.co.absa.spline.common.graph.GraphImplicits can break za.co.absa.spline.producer.model.v1_2.OperationLike, while a change to za.co.absa.spline.producer.model.v1_2.OperationLike can't break za.co.absa.spline.common.graph.GraphImplicits.
- Position
- Below the diagonal: za.co.absa.spline.producer.model.v1_2.OperationLike uses a module listed above it, which is the healthy direction.
21→11 za.co.absa.spline.producer.model.v1_2.OperationLike uses za.co.absa.spline.producer.model.v1_2✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.model.v1_2.OperationLike uses a type in za.co.absa.spline.producer.model.v1_2.
- The types involved
za.co.absa.spline.producer.model.v1_2.OperationLike.OpNav→za.co.absa.spline.producer.model.v1_2.OperationLike
- Direction
- za.co.absa.spline.producer.model.v1_2.OperationLike uses za.co.absa.spline.producer.model.v1_2, so a change to za.co.absa.spline.producer.model.v1_2 can break za.co.absa.spline.producer.model.v1_2.OperationLike, while a change to za.co.absa.spline.producer.model.v1_2.OperationLike can't break za.co.absa.spline.producer.model.v1_2.
- Position
- Below the diagonal: za.co.absa.spline.producer.model.v1_2.OperationLike uses a module listed above it, which is the healthy direction.
22→11 za.co.absa.spline.producer.modelmapper uses za.co.absa.spline.producer.model.v1_2✕
- Connections
- 2 pairs of types, where a type in za.co.absa.spline.producer.modelmapper uses a type in za.co.absa.spline.producer.model.v1_2.
- The types involved
za.co.absa.spline.producer.modelmapper.ModelMapper→za.co.absa.spline.producer.model.v1_2.ExecutionEventza.co.absa.spline.producer.modelmapper.ModelMapper→za.co.absa.spline.producer.model.v1_2.ExecutionPlan
- Direction
- za.co.absa.spline.producer.modelmapper uses za.co.absa.spline.producer.model.v1_2, so a change to za.co.absa.spline.producer.model.v1_2 can break za.co.absa.spline.producer.modelmapper, while a change to za.co.absa.spline.producer.modelmapper can't break za.co.absa.spline.producer.model.v1_2.
- Position
- Below the diagonal: za.co.absa.spline.producer.modelmapper uses a module listed above it, which is the healthy direction.
23→4 za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 uses za.co.absa.spline.common.graph.GraphImplicits✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 uses a type in za.co.absa.spline.common.graph.GraphImplicits.
- The types involved
za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10.OpNav→za.co.absa.spline.common.graph.GraphImplicits.DAGNodeIdMapping
- Direction
- za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 uses za.co.absa.spline.common.graph.GraphImplicits, so a change to za.co.absa.spline.common.graph.GraphImplicits can break za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10, while a change to za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 can't break za.co.absa.spline.common.graph.GraphImplicits.
- Position
- Below the diagonal: za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 uses a module listed above it, which is the healthy direction.
23→11 za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 uses za.co.absa.spline.producer.model.v1_2✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 uses a type in za.co.absa.spline.producer.model.v1_2.
- The types involved
za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10.OpNav→za.co.absa.spline.producer.model.v1_2.OperationLike
- Direction
- za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 uses za.co.absa.spline.producer.model.v1_2, so a change to za.co.absa.spline.producer.model.v1_2 can break za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10, while a change to za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 can't break za.co.absa.spline.producer.model.v1_2.
- Position
- Below the diagonal: za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10 uses a module listed above it, which is the healthy direction.
24→9 za.co.absa.spline.producer.service.model uses za.co.absa.spline.persistence.model✕
- Connections
- 7 pairs of types, where a type in za.co.absa.spline.producer.service.model uses a type in za.co.absa.spline.persistence.model.
- The types involved
za.co.absa.spline.producer.service.model.ExecutionPlanPersistentModel→za.co.absa.spline.persistence.model.Attributeza.co.absa.spline.producer.service.model.ExecutionPlanPersistentModel→za.co.absa.spline.persistence.model.Edgeza.co.absa.spline.producer.service.model.ExecutionPlanPersistentModel→za.co.absa.spline.persistence.model.ExecutionPlanza.co.absa.spline.producer.service.model.ExecutionPlanPersistentModel→za.co.absa.spline.persistence.model.Expressionza.co.absa.spline.producer.service.model.ExecutionPlanPersistentModel→za.co.absa.spline.persistence.model.Operationza.co.absa.spline.producer.service.model.ExecutionPlanPersistentModel→za.co.absa.spline.persistence.model.Schemaza.co.absa.spline.producer.service.model.ExecutionPlanPersistentModelBuilder→za.co.absa.spline.persistence.model.Edge
- Direction
- za.co.absa.spline.producer.service.model uses za.co.absa.spline.persistence.model, so a change to za.co.absa.spline.persistence.model can break za.co.absa.spline.producer.service.model, while a change to za.co.absa.spline.producer.service.model can't break za.co.absa.spline.persistence.model.
- Position
- Below the diagonal: za.co.absa.spline.producer.service.model uses a module listed above it, which is the healthy direction.
24→11 za.co.absa.spline.producer.service.model uses za.co.absa.spline.producer.model.v1_2✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.service.model uses a type in za.co.absa.spline.producer.model.v1_2.
- The types involved
za.co.absa.spline.producer.service.model.ExecutionPlanPersistentModelBuilder→za.co.absa.spline.producer.model.v1_2.AttrOrExprRef
- Direction
- za.co.absa.spline.producer.service.model uses za.co.absa.spline.producer.model.v1_2, so a change to za.co.absa.spline.producer.model.v1_2 can break za.co.absa.spline.producer.service.model, while a change to za.co.absa.spline.producer.service.model can't break za.co.absa.spline.producer.model.v1_2.
- Position
- Below the diagonal: za.co.absa.spline.producer.service.model uses a module listed above it, which is the healthy direction.
25→9 za.co.absa.spline.producer.service.repo uses za.co.absa.spline.persistence.model✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.service.repo uses a type in za.co.absa.spline.persistence.model.
- The types involved
za.co.absa.spline.producer.service.repo.ExecutionProducerRepositoryImpl→za.co.absa.spline.persistence.model.ExecutionPlan
- Direction
- za.co.absa.spline.producer.service.repo uses za.co.absa.spline.persistence.model, so a change to za.co.absa.spline.persistence.model can break za.co.absa.spline.producer.service.repo, while a change to za.co.absa.spline.producer.service.repo can't break za.co.absa.spline.persistence.model.
- Position
- Below the diagonal: za.co.absa.spline.producer.service.repo uses a module listed above it, which is the healthy direction.
25→11 za.co.absa.spline.producer.service.repo uses za.co.absa.spline.producer.model.v1_2✕
- Connections
- 2 pairs of types, where a type in za.co.absa.spline.producer.service.repo uses a type in za.co.absa.spline.producer.model.v1_2.
- The types involved
za.co.absa.spline.producer.service.repo.ExecutionProducerRepository→za.co.absa.spline.producer.model.v1_2.ExecutionEventza.co.absa.spline.producer.service.repo.ExecutionProducerRepository→za.co.absa.spline.producer.model.v1_2.ExecutionPlan
- Direction
- za.co.absa.spline.producer.service.repo uses za.co.absa.spline.producer.model.v1_2, so a change to za.co.absa.spline.producer.model.v1_2 can break za.co.absa.spline.producer.service.repo, while a change to za.co.absa.spline.producer.service.repo can't break za.co.absa.spline.producer.model.v1_2.
- Position
- Below the diagonal: za.co.absa.spline.producer.service.repo uses a module listed above it, which is the healthy direction.
26→8 za.co.absa.spline.admin uses za.co.absa.spline.persistence✕
- Connections
- 4 pairs of types, where a type in za.co.absa.spline.admin uses a type in za.co.absa.spline.persistence.
- The types involved
za.co.absa.spline.admin.ConsoleUserInteractor→za.co.absa.spline.persistence.ArangoConnectionURLza.co.absa.spline.admin.InteractiveArangoManagerFactoryProxy→za.co.absa.spline.persistence.ArangoConnectionURLza.co.absa.spline.admin.NonInteractiveUserInteractor→za.co.absa.spline.persistence.ArangoConnectionURLza.co.absa.spline.admin.UserInteractor→za.co.absa.spline.persistence.ArangoConnectionURL
- Direction
- za.co.absa.spline.admin uses za.co.absa.spline.persistence, so a change to za.co.absa.spline.persistence can break za.co.absa.spline.admin, while a change to za.co.absa.spline.admin can't break za.co.absa.spline.persistence.
- Position
- Below the diagonal: za.co.absa.spline.admin uses a module listed above it, which is the healthy direction.
26→16 za.co.absa.spline.admin uses za.co.absa.spline.arango✕
- Connections
- 4 pairs of types, where a type in za.co.absa.spline.admin uses a type in za.co.absa.spline.arango.
- The types involved
za.co.absa.spline.admin.DBExec→za.co.absa.spline.arango.AuxiliaryDBActionza.co.absa.spline.admin.DBInit→za.co.absa.spline.arango.DatabaseCreateOptionsza.co.absa.spline.admin.InteractiveArangoManagerFactoryProxy→za.co.absa.spline.arango.ArangoManagerza.co.absa.spline.admin.InteractiveArangoManagerFactoryProxy→za.co.absa.spline.arango.ArangoManagerFactory
- Direction
- za.co.absa.spline.admin uses za.co.absa.spline.arango, so a change to za.co.absa.spline.arango can break za.co.absa.spline.admin, while a change to za.co.absa.spline.admin can't break za.co.absa.spline.arango.
- Position
- Below the diagonal: za.co.absa.spline.admin uses a module listed above it, which is the healthy direction.
27→16 za.co.absa.spline.arango.AuxiliaryDBAction uses za.co.absa.spline.arango✕
- Connections
- 8 pairs of types, where a type in za.co.absa.spline.arango.AuxiliaryDBAction uses a type in za.co.absa.spline.arango.
- The types involved
za.co.absa.spline.arango.AuxiliaryDBAction.CheckDBAccess→za.co.absa.spline.arango.AuxiliaryDBActionza.co.absa.spline.arango.AuxiliaryDBAction.FoxxReinstall→za.co.absa.spline.arango.AuxiliaryDBActionza.co.absa.spline.arango.AuxiliaryDBAction.IndicesCreate→za.co.absa.spline.arango.AuxiliaryDBActionza.co.absa.spline.arango.AuxiliaryDBAction.IndicesDelete→za.co.absa.spline.arango.AuxiliaryDBActionza.co.absa.spline.arango.AuxiliaryDBAction.SearchAnalyzerCreate→za.co.absa.spline.arango.AuxiliaryDBActionza.co.absa.spline.arango.AuxiliaryDBAction.SearchAnalyzerDelete→za.co.absa.spline.arango.AuxiliaryDBActionza.co.absa.spline.arango.AuxiliaryDBAction.SearchViewsCreate→za.co.absa.spline.arango.AuxiliaryDBActionza.co.absa.spline.arango.AuxiliaryDBAction.SearchViewsDelete→za.co.absa.spline.arango.AuxiliaryDBAction
- Direction
- za.co.absa.spline.arango.AuxiliaryDBAction uses za.co.absa.spline.arango, so a change to za.co.absa.spline.arango can break za.co.absa.spline.arango.AuxiliaryDBAction, while a change to za.co.absa.spline.arango.AuxiliaryDBAction can't break za.co.absa.spline.arango.
- Position
- Below the diagonal: za.co.absa.spline.arango.AuxiliaryDBAction uses a module listed above it, which is the healthy direction.
28→16 za.co.absa.spline.arango.OnDBExistsAction uses za.co.absa.spline.arango✕
- Connections
- 3 pairs of types, where a type in za.co.absa.spline.arango.OnDBExistsAction uses a type in za.co.absa.spline.arango.
- The types involved
za.co.absa.spline.arango.OnDBExistsAction.Drop→za.co.absa.spline.arango.OnDBExistsActionza.co.absa.spline.arango.OnDBExistsAction.Fail→za.co.absa.spline.arango.OnDBExistsActionza.co.absa.spline.arango.OnDBExistsAction.Skip→za.co.absa.spline.arango.OnDBExistsAction
- Direction
- za.co.absa.spline.arango.OnDBExistsAction uses za.co.absa.spline.arango, so a change to za.co.absa.spline.arango can break za.co.absa.spline.arango.OnDBExistsAction, while a change to za.co.absa.spline.arango.OnDBExistsAction can't break za.co.absa.spline.arango.
- Position
- Below the diagonal: za.co.absa.spline.arango.OnDBExistsAction uses a module listed above it, which is the healthy direction.
29→19 za.co.absa.spline.consumer.rest.controller.LineageDetailedController uses za.co.absa.spline.consumer.service.model✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.consumer.rest.controller.LineageDetailedController uses a type in za.co.absa.spline.consumer.service.model.
- The types involved
za.co.absa.spline.consumer.rest.controller.LineageDetailedController.AttributeLineageAndImpact→za.co.absa.spline.consumer.service.model.AttributeGraph
- Direction
- za.co.absa.spline.consumer.rest.controller.LineageDetailedController uses za.co.absa.spline.consumer.service.model, so a change to za.co.absa.spline.consumer.service.model can break za.co.absa.spline.consumer.rest.controller.LineageDetailedController, while a change to za.co.absa.spline.consumer.rest.controller.LineageDetailedController can't break za.co.absa.spline.consumer.service.model.
- Position
- Below the diagonal: za.co.absa.spline.consumer.rest.controller.LineageDetailedController uses a module listed above it, which is the healthy direction.
30→19 za.co.absa.spline.consumer.rest.controller.OperationDetailsController uses za.co.absa.spline.consumer.service.model✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.consumer.rest.controller.OperationDetailsController uses a type in za.co.absa.spline.consumer.service.model.
- The types involved
za.co.absa.spline.consumer.rest.controller.OperationDetailsController.NodeToExprAssemblyConverter→za.co.absa.spline.consumer.service.model.ExpressionNode
- Direction
- za.co.absa.spline.consumer.rest.controller.OperationDetailsController uses za.co.absa.spline.consumer.service.model, so a change to za.co.absa.spline.consumer.service.model can break za.co.absa.spline.consumer.rest.controller.OperationDetailsController, while a change to za.co.absa.spline.consumer.rest.controller.OperationDetailsController can't break za.co.absa.spline.consumer.service.model.
- Position
- Below the diagonal: za.co.absa.spline.consumer.rest.controller.OperationDetailsController uses a module listed above it, which is the healthy direction.
31→19 za.co.absa.spline.consumer.rest.model uses za.co.absa.spline.consumer.service.model✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.consumer.rest.model uses a type in za.co.absa.spline.consumer.service.model.
- The types involved
za.co.absa.spline.consumer.rest.model.LabelQuery→za.co.absa.spline.consumer.service.model.Label
- Direction
- za.co.absa.spline.consumer.rest.model uses za.co.absa.spline.consumer.service.model, so a change to za.co.absa.spline.consumer.service.model can break za.co.absa.spline.consumer.rest.model, while a change to za.co.absa.spline.consumer.rest.model can't break za.co.absa.spline.consumer.service.model.
- Position
- Below the diagonal: za.co.absa.spline.consumer.rest.model uses a module listed above it, which is the healthy direction.
32→19 za.co.absa.spline.consumer.service.model.DataSourceActionType uses za.co.absa.spline.consumer.service.model✕
- Connections
- 2 pairs of types, where a type in za.co.absa.spline.consumer.service.model.DataSourceActionType uses a type in za.co.absa.spline.consumer.service.model.
- The types involved
za.co.absa.spline.consumer.service.model.DataSourceActionType.Read→za.co.absa.spline.consumer.service.model.DataSourceActionTypeza.co.absa.spline.consumer.service.model.DataSourceActionType.Write→za.co.absa.spline.consumer.service.model.DataSourceActionType
- Direction
- za.co.absa.spline.consumer.service.model.DataSourceActionType uses za.co.absa.spline.consumer.service.model, so a change to za.co.absa.spline.consumer.service.model can break za.co.absa.spline.consumer.service.model.DataSourceActionType, while a change to za.co.absa.spline.consumer.service.model.DataSourceActionType can't break za.co.absa.spline.consumer.service.model.
- Position
- Below the diagonal: za.co.absa.spline.consumer.service.model.DataSourceActionType uses a module listed above it, which is the healthy direction.
33→19 za.co.absa.spline.consumer.service.repo uses za.co.absa.spline.consumer.service.model✕
- Connections
- 26 pairs of types, where a type in za.co.absa.spline.consumer.service.repo uses a type in za.co.absa.spline.consumer.service.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
za.co.absa.spline.consumer.service.repo.AbstractExecutionEventRepository→za.co.absa.spline.consumer.service.model.Labelza.co.absa.spline.consumer.service.repo.AbstractExecutionEventRepository→za.co.absa.spline.consumer.service.model.PageRequestza.co.absa.spline.consumer.service.repo.AbstractExecutionEventRepository→za.co.absa.spline.consumer.service.model.SortRequestza.co.absa.spline.consumer.service.repo.DataSourceRepository→za.co.absa.spline.consumer.service.model.DataSourceActionTypeza.co.absa.spline.consumer.service.repo.DataSourceRepositoryImpl→za.co.absa.spline.consumer.service.model.DataSourceActionTypeza.co.absa.spline.consumer.service.repo.DataSourceRepositoryImpl→za.co.absa.spline.consumer.service.model.Labelza.co.absa.spline.consumer.service.repo.DataSourceRepositoryImpl→za.co.absa.spline.consumer.service.model.PageRequestza.co.absa.spline.consumer.service.repo.DataSourceRepositoryImpl→za.co.absa.spline.consumer.service.model.SortRequestza.co.absa.spline.consumer.service.repo.ExecutionEventRepositoryImpl→za.co.absa.spline.consumer.service.model.Labelza.co.absa.spline.consumer.service.repo.ExecutionEventRepositoryImpl→za.co.absa.spline.consumer.service.model.PageRequestza.co.absa.spline.consumer.service.repo.ExecutionEventRepositoryImpl→za.co.absa.spline.consumer.service.model.SortRequestza.co.absa.spline.consumer.service.repo.ExecutionPlanRepository→za.co.absa.spline.consumer.service.model.AttributeGraphza.co.absa.spline.consumer.service.repo.ExecutionPlanRepository→za.co.absa.spline.consumer.service.model.LineageDetailedza.co.absa.spline.consumer.service.repo.ExecutionPlanRepository→za.co.absa.spline.consumer.service.model.PageRequestza.co.absa.spline.consumer.service.repo.ExecutionPlanRepository→za.co.absa.spline.consumer.service.model.SortRequestza.co.absa.spline.consumer.service.repo.ExecutionPlanRepositoryImpl→za.co.absa.spline.consumer.service.model.AttributeGraphza.co.absa.spline.consumer.service.repo.ExecutionPlanRepositoryImpl→za.co.absa.spline.consumer.service.model.LineageDetailedza.co.absa.spline.consumer.service.repo.ExecutionPlanRepositoryImpl→za.co.absa.spline.consumer.service.model.PageRequestza.co.absa.spline.consumer.service.repo.ExecutionPlanRepositoryImpl→za.co.absa.spline.consumer.service.model.SortRequestza.co.absa.spline.consumer.service.repo.ExpressionRepository→za.co.absa.spline.consumer.service.model.ExpressionGraphza.co.absa.spline.consumer.service.repo.ExpressionRepositoryImpl→za.co.absa.spline.consumer.service.model.ExpressionGraphza.co.absa.spline.consumer.service.repo.ImpactLineageRepositoryImpl→za.co.absa.spline.consumer.service.model.LineageOverviewza.co.absa.spline.consumer.service.repo.ImpactRepository→za.co.absa.spline.consumer.service.model.LineageOverviewza.co.absa.spline.consumer.service.repo.LineageRepository→za.co.absa.spline.consumer.service.model.LineageOverviewza.co.absa.spline.consumer.service.repo.OperationRepository→za.co.absa.spline.consumer.service.model.OperationDetails
- Direction
- za.co.absa.spline.consumer.service.repo uses za.co.absa.spline.consumer.service.model, so a change to za.co.absa.spline.consumer.service.model can break za.co.absa.spline.consumer.service.repo, while a change to za.co.absa.spline.consumer.service.repo can't break za.co.absa.spline.consumer.service.model.
- Position
- Below the diagonal: za.co.absa.spline.consumer.service.repo uses a module listed above it, which is the healthy direction.
34→7 za.co.absa.spline.gateway.kafka.listener uses za.co.absa.spline.gateway.kafka.listener.handler✕
- Connections
- 2 pairs of types, where a type in za.co.absa.spline.gateway.kafka.listener uses a type in za.co.absa.spline.gateway.kafka.listener.handler.
- The types involved
za.co.absa.spline.gateway.kafka.listener.IngestionListener→za.co.absa.spline.gateway.kafka.listener.handler.HandlerV11za.co.absa.spline.gateway.kafka.listener.IngestionListener→za.co.absa.spline.gateway.kafka.listener.handler.HandlerV12
- Direction
- za.co.absa.spline.gateway.kafka.listener uses za.co.absa.spline.gateway.kafka.listener.handler, so a change to za.co.absa.spline.gateway.kafka.listener.handler can break za.co.absa.spline.gateway.kafka.listener, while a change to za.co.absa.spline.gateway.kafka.listener can't break za.co.absa.spline.gateway.kafka.listener.handler.
- Position
- Below the diagonal: za.co.absa.spline.gateway.kafka.listener uses a module listed above it, which is the healthy direction.
34→22 za.co.absa.spline.gateway.kafka.listener uses za.co.absa.spline.producer.modelmapper✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.gateway.kafka.listener uses a type in za.co.absa.spline.producer.modelmapper.
- The types involved
za.co.absa.spline.gateway.kafka.listener.IngestionListener→za.co.absa.spline.producer.modelmapper.ModelMapper
- Direction
- za.co.absa.spline.gateway.kafka.listener uses za.co.absa.spline.producer.modelmapper, so a change to za.co.absa.spline.producer.modelmapper can break za.co.absa.spline.gateway.kafka.listener, while a change to za.co.absa.spline.gateway.kafka.listener can't break za.co.absa.spline.producer.modelmapper.
- Position
- Below the diagonal: za.co.absa.spline.gateway.kafka.listener uses a module listed above it, which is the healthy direction.
34→25 za.co.absa.spline.gateway.kafka.listener uses za.co.absa.spline.producer.service.repo✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.gateway.kafka.listener uses a type in za.co.absa.spline.producer.service.repo.
- The types involved
za.co.absa.spline.gateway.kafka.listener.IngestionListener→za.co.absa.spline.producer.service.repo.ExecutionProducerRepository
- Direction
- za.co.absa.spline.gateway.kafka.listener uses za.co.absa.spline.producer.service.repo, so a change to za.co.absa.spline.producer.service.repo can break za.co.absa.spline.gateway.kafka.listener, while a change to za.co.absa.spline.gateway.kafka.listener can't break za.co.absa.spline.producer.service.repo.
- Position
- Below the diagonal: za.co.absa.spline.gateway.kafka.listener uses a module listed above it, which is the healthy direction.
35→11 za.co.absa.spline.producer.modelmapper.v1_0 uses za.co.absa.spline.producer.model.v1_2✕
- Connections
- 4 pairs of types, where a type in za.co.absa.spline.producer.modelmapper.v1_0 uses a type in za.co.absa.spline.producer.model.v1_2.
- The types involved
za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10→za.co.absa.spline.producer.model.v1_2.ExecutionEventza.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10→za.co.absa.spline.producer.model.v1_2.ExecutionPlanza.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10→za.co.absa.spline.producer.model.v1_2.ExpressionLikeza.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10→za.co.absa.spline.producer.model.v1_2.OperationLike
- Direction
- za.co.absa.spline.producer.modelmapper.v1_0 uses za.co.absa.spline.producer.model.v1_2, so a change to za.co.absa.spline.producer.model.v1_2 can break za.co.absa.spline.producer.modelmapper.v1_0, while a change to za.co.absa.spline.producer.modelmapper.v1_0 can't break za.co.absa.spline.producer.model.v1_2.
- Position
- Below the diagonal: za.co.absa.spline.producer.modelmapper.v1_0 uses a module listed above it, which is the healthy direction.
35→22 za.co.absa.spline.producer.modelmapper.v1_0 uses za.co.absa.spline.producer.modelmapper✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.modelmapper.v1_0 uses a type in za.co.absa.spline.producer.modelmapper.
- The types involved
za.co.absa.spline.producer.modelmapper.v1_0.ModelMapperV10→za.co.absa.spline.producer.modelmapper.ModelMapper
- Direction
- za.co.absa.spline.producer.modelmapper.v1_0 uses za.co.absa.spline.producer.modelmapper, so a change to za.co.absa.spline.producer.modelmapper can break za.co.absa.spline.producer.modelmapper.v1_0, while a change to za.co.absa.spline.producer.modelmapper.v1_0 can't break za.co.absa.spline.producer.modelmapper.
- Position
- Below the diagonal: za.co.absa.spline.producer.modelmapper.v1_0 uses a module listed above it, which is the healthy direction.
36→22 za.co.absa.spline.producer.rest.controller uses za.co.absa.spline.producer.modelmapper✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.producer.rest.controller uses a type in za.co.absa.spline.producer.modelmapper.
- The types involved
za.co.absa.spline.producer.rest.controller.IngestionController→za.co.absa.spline.producer.modelmapper.ModelMapper
- Direction
- za.co.absa.spline.producer.rest.controller uses za.co.absa.spline.producer.modelmapper, so a change to za.co.absa.spline.producer.modelmapper can break za.co.absa.spline.producer.rest.controller, while a change to za.co.absa.spline.producer.rest.controller can't break za.co.absa.spline.producer.modelmapper.
- Position
- Below the diagonal: za.co.absa.spline.producer.rest.controller uses a module listed above it, which is the healthy direction.
36→25 za.co.absa.spline.producer.rest.controller uses za.co.absa.spline.producer.service.repo✕
- Connections
- 2 pairs of types, where a type in za.co.absa.spline.producer.rest.controller uses a type in za.co.absa.spline.producer.service.repo.
- The types involved
za.co.absa.spline.producer.rest.controller.IngestionController→za.co.absa.spline.producer.service.repo.ExecutionProducerRepositoryza.co.absa.spline.producer.rest.controller.StatusController→za.co.absa.spline.producer.service.repo.ExecutionProducerRepository
- Direction
- za.co.absa.spline.producer.rest.controller uses za.co.absa.spline.producer.service.repo, so a change to za.co.absa.spline.producer.service.repo can break za.co.absa.spline.producer.rest.controller, while a change to za.co.absa.spline.producer.rest.controller can't break za.co.absa.spline.producer.service.repo.
- Position
- Below the diagonal: za.co.absa.spline.producer.rest.controller uses a module listed above it, which is the healthy direction.
37→26 za.co.absa.spline.admin.AdminCLI uses za.co.absa.spline.admin✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.admin.AdminCLI uses a type in za.co.absa.spline.admin.
- The types involved
za.co.absa.spline.admin.AdminCLI.AdminCLIConfig→za.co.absa.spline.admin.Command
- Direction
- za.co.absa.spline.admin.AdminCLI uses za.co.absa.spline.admin, so a change to za.co.absa.spline.admin can break za.co.absa.spline.admin.AdminCLI, while a change to za.co.absa.spline.admin.AdminCLI can't break za.co.absa.spline.admin.
- Position
- Below the diagonal: za.co.absa.spline.admin.AdminCLI uses a module listed above it, which is the healthy direction.
38→26 za.co.absa.spline.admin.InputConsole uses za.co.absa.spline.admin✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.admin.InputConsole uses a type in za.co.absa.spline.admin.
- The types involved
za.co.absa.spline.admin.InputConsole.SystemConsole→za.co.absa.spline.admin.InputConsole
- Direction
- za.co.absa.spline.admin.InputConsole uses za.co.absa.spline.admin, so a change to za.co.absa.spline.admin can break za.co.absa.spline.admin.InputConsole, while a change to za.co.absa.spline.admin.InputConsole can't break za.co.absa.spline.admin.
- Position
- Below the diagonal: za.co.absa.spline.admin.InputConsole uses a module listed above it, which is the healthy direction.
39→19 za.co.absa.spline.consumer.rest.controller uses za.co.absa.spline.consumer.service.model✕
- Connections
- 12 pairs of types, where a type in za.co.absa.spline.consumer.rest.controller uses a type in za.co.absa.spline.consumer.service.model.
- The types involved
za.co.absa.spline.consumer.rest.controller.AbstractExecutionEventsController→za.co.absa.spline.consumer.service.model.Labelza.co.absa.spline.consumer.rest.controller.AbstractExecutionEventsController→za.co.absa.spline.consumer.service.model.PageableExecutionEventsResponseza.co.absa.spline.consumer.rest.controller.ExecutionEventsController→za.co.absa.spline.consumer.service.model.PageableExecutionEventsResponseza.co.absa.spline.consumer.rest.controller.ExecutionPlansController→za.co.absa.spline.consumer.service.model.LineageDetailedza.co.absa.spline.consumer.rest.controller.ExecutionPlansController→za.co.absa.spline.consumer.service.model.PageableExecutionPlansResponseza.co.absa.spline.consumer.rest.controller.ImpactOverviewController→za.co.absa.spline.consumer.service.model.LineageOverviewza.co.absa.spline.consumer.rest.controller.LineageDetailedController→za.co.absa.spline.consumer.service.model.LineageDetailedza.co.absa.spline.consumer.rest.controller.LineageOverviewController→za.co.absa.spline.consumer.service.model.LineageOverviewza.co.absa.spline.consumer.rest.controller.OperationDetailsController→za.co.absa.spline.consumer.service.model.Attributeza.co.absa.spline.consumer.rest.controller.OperationDetailsController→za.co.absa.spline.consumer.service.model.DataTypeza.co.absa.spline.consumer.rest.controller.OperationDetailsController→za.co.absa.spline.consumer.service.model.ExpressionGraphza.co.absa.spline.consumer.rest.controller.OperationDetailsController→za.co.absa.spline.consumer.service.model.OperationDetails
- Direction
- za.co.absa.spline.consumer.rest.controller uses za.co.absa.spline.consumer.service.model, so a change to za.co.absa.spline.consumer.service.model can break za.co.absa.spline.consumer.rest.controller, while a change to za.co.absa.spline.consumer.rest.controller can't break za.co.absa.spline.consumer.service.model.
- Position
- Below the diagonal: za.co.absa.spline.consumer.rest.controller uses a module listed above it, which is the healthy direction.
39→29 za.co.absa.spline.consumer.rest.controller uses za.co.absa.spline.consumer.rest.controller.LineageDetailedController✕
- Connections
- 1 pair of types, where a type in za.co.absa.spline.consumer.rest.controller uses a type in za.co.absa.spline.consumer.rest.controller.LineageDetailedController.
- The types involved
za.co.absa.spline.consumer.rest.controller.LineageDetailedController→za.co.absa.spline.consumer.rest.controller.LineageDetailedController.AttributeLineageAndImpact
- Direction
- za.co.absa.spline.consumer.rest.controller uses za.co.absa.spline.consumer.rest.controller.LineageDetailedController, so a change to za.co.absa.spline.consumer.rest.controller.LineageDetailedController can break za.co.absa.spline.consumer.rest.controller, while a change to za.co.absa.spline.consumer.rest.controller can't break za.co.absa.spline.consumer.rest.controller.LineageDetailedController.
- Position
- Below the diagonal: za.co.absa.spline.consumer.rest.controller uses a module listed above it, which is the healthy direction.
39→33 za.co.absa.spline.consumer.rest.controller uses za.co.absa.spline.consumer.service.repo✕
- Connections
- 10 pairs of types, where a type in za.co.absa.spline.consumer.rest.controller uses a type in za.co.absa.spline.consumer.service.repo.
- The types involved
za.co.absa.spline.consumer.rest.controller.DataSourcesController→za.co.absa.spline.consumer.service.repo.DataSourceRepositoryza.co.absa.spline.consumer.rest.controller.ExecutionEventsController→za.co.absa.spline.consumer.service.repo.ExecutionEventRepositoryza.co.absa.spline.consumer.rest.controller.ExecutionPlansController→za.co.absa.spline.consumer.service.repo.DataSourceRepositoryza.co.absa.spline.consumer.rest.controller.ExecutionPlansController→za.co.absa.spline.consumer.service.repo.ExecutionPlanRepositoryza.co.absa.spline.consumer.rest.controller.ImpactOverviewController→za.co.absa.spline.consumer.service.repo.ImpactRepositoryza.co.absa.spline.consumer.rest.controller.LabelsController→za.co.absa.spline.consumer.service.repo.LabelRepositoryza.co.absa.spline.consumer.rest.controller.LineageDetailedController→za.co.absa.spline.consumer.service.repo.ExecutionPlanRepositoryza.co.absa.spline.consumer.rest.controller.LineageOverviewController→za.co.absa.spline.consumer.service.repo.LineageRepositoryza.co.absa.spline.consumer.rest.controller.OperationDetailsController→za.co.absa.spline.consumer.service.repo.ExpressionRepositoryza.co.absa.spline.consumer.rest.controller.OperationDetailsController→za.co.absa.spline.consumer.service.repo.OperationRepository
- Direction
- za.co.absa.spline.consumer.rest.controller uses za.co.absa.spline.consumer.service.repo, so a change to za.co.absa.spline.consumer.service.repo can break za.co.absa.spline.consumer.rest.controller, while a change to za.co.absa.spline.consumer.rest.controller can't break za.co.absa.spline.consumer.service.repo.
- Position
- Below the diagonal: za.co.absa.spline.consumer.rest.controller uses a module listed above it, which is the healthy direction.
40→11 za.co.absa.spline.producer.modelmapper.v1_0.spark uses za.co.absa.spline.producer.model.v1_2✕
- Connections
- 2 pairs of types, where a type in za.co.absa.spline.producer.modelmapper.v1_0.spark uses a type in za.co.absa.spline.producer.model.v1_2.
- The types involved
za.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineExpressionConverter→za.co.absa.spline.producer.model.v1_2.ExpressionLikeza.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineExpressionConverter→za.co.absa.spline.producer.model.v1_2.FunctionalExpression
- Direction
- za.co.absa.spline.producer.modelmapper.v1_0.spark uses za.co.absa.spline.producer.model.v1_2, so a change to za.co.absa.spline.producer.model.v1_2 can break za.co.absa.spline.producer.modelmapper.v1_0.spark, while a change to za.co.absa.spline.producer.modelmapper.v1_0.spark can't break za.co.absa.spline.producer.model.v1_2.
- Position
- Below the diagonal: za.co.absa.spline.producer.modelmapper.v1_0.spark uses a module listed above it, which is the healthy direction.
40→35 za.co.absa.spline.producer.modelmapper.v1_0.spark uses za.co.absa.spline.producer.modelmapper.v1_0✕
- Connections
- 8 pairs of types, where a type in za.co.absa.spline.producer.modelmapper.v1_0.spark uses a type in za.co.absa.spline.producer.modelmapper.v1_0.
- The types involved
za.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSpline04AttributeDependencyResolver→za.co.absa.spline.producer.modelmapper.v1_0.AttributeDependencyResolverza.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineAttributeConverter→za.co.absa.spline.producer.modelmapper.v1_0.AttributeConverterza.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineExecutionPlanComponentConverterFactory→za.co.absa.spline.producer.modelmapper.v1_0.ExecutionPlanComponentConverterFactoryza.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineExecutionPlanComponentConverterFactory→za.co.absa.spline.producer.modelmapper.v1_0.ObjectConverterza.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineExecutionPlanComponentConverterFactory→za.co.absa.spline.producer.modelmapper.v1_0.OperationOutputConverterza.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineExpressionConverter→za.co.absa.spline.producer.modelmapper.v1_0.ExpressionConverterza.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineObjectConverter→za.co.absa.spline.producer.modelmapper.v1_0.ObjectConverterza.co.absa.spline.producer.modelmapper.v1_0.spark.SparkSplineOperationOutputConverter→za.co.absa.spline.producer.modelmapper.v1_0.OperationOutputConverter
- Direction
- za.co.absa.spline.producer.modelmapper.v1_0.spark uses za.co.absa.spline.producer.modelmapper.v1_0, so a change to za.co.absa.spline.producer.modelmapper.v1_0 can break za.co.absa.spline.producer.modelmapper.v1_0.spark, while a change to za.co.absa.spline.producer.modelmapper.v1_0.spark can't break za.co.absa.spline.producer.modelmapper.v1_0.
- Position
- Below the diagonal: za.co.absa.spline.producer.modelmapper.v1_0.spark uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A05:2025 — Injection | 7 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | Medium |
Roadmap
Top priorities: Resolve the 70 Orphaned file finding(s) in Knowledge Freshness — start with AttrOrExprRef.scala (2), operations.scala (2), AdminCLI.scala; 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; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +6.3 pts | Low | ADR Quality |
| Resolve the 70 Orphaned file finding(s) in Knowledge Freshness — start with AttrOrExprRef.scala (2), operations.scala (2), AdminCLI.scala. | +8.2 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.3 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.5 pts | Medium | Security & performance tooling |
| Resolve the 1 redundant comment finding(s) in Comment Value — start with teardown.ts. | +2.0 pts | Low | Comment Value |
| Add tests that import the unreached modules (directly or through their public entry). | +3.6 pts | Medium | Test Coverage |
| Resolve the 1 `ensureNoExecPlanIDCollision` spells `ID` where 69 names in the project… finding(s) in Naming Consistency — start with ExecutionProducerRepositoryImpl.scala. | +1.3 pts | Low | Naming Consistency |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.7 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala | 7.1 | Mixed | Code Duplication: Edited copy of a member (79 corresponding lines) |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| admin/src/main/scala/za/co/absa/spline/admin/AdminCLI.scala | 7.8 | Mixed | Cyclomatic Complexity: AdminCLI.exec (cyclomatic 44) |
| producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/AttrOrExprRef.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/ExecutionEventRepositoryImpl.scala | 7.8 | Mixed | Code Duplication: Duplicated block (38–52 lines × 2) |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/expressions.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| persistence/src/main/scala/za/co/absa/spline/persistence/model/persistentDefs.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| commons/src/main/scala/za/co/absa/spline/common/JsonPath.scala | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| admin/src/main/scala/za/co/absa/spline/arango/ArangoManager.scala | 8.5 | Near-clean | Cognitive Complexity: ArangoManagerImpl.createDatabase (cognitive 57) |
| persistence/src/main/scala/za/co/absa/spline/persistence/migration/Migrator.scala | 8.5 | Near-clean | Cognitive Complexity: Migrator.executeMigration (cognitive 23) |
| consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/LabelRepositoryImpl.scala | 8.5 | Near-clean | Code Duplication: Edited copy of a member (21 corresponding lines) |
| consumer-rest-core/src/main/scala/za/co/absa/spline/consumer/rest/controller/DataSourcesController.scala | 8.5 | Near-clean | Code Duplication: Edited copy of a member (15 corresponding lines) |
| producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/executionPlan.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (31 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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 63 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 63 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 174 of 186 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .scala, and our analyzer cannot run the .scala test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 83.3% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- D10 Test 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. The 14 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 42 test source file(s) (.scala) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 reliability NOT SCORED: this repository's production source includes .scala, and the built-in reliability runner cannot re-run the .scala test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in arangodb-foxx-services/ (6 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
- D12 Dependency Hygiene — 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. Not scored — a Maven build resolved 155 artifact(s) (135 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 71 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 69 of the 264 production source files in this repository: 193 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
- 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — 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 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. `producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/expressions.scala`, `producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_2/expressions.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Spring (Scala), whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:32 -------------------- 30 | USER 1001 31 | ARG PROJECT_BUILD_FINAL_NAME 32 | >>> COPY --chown=1001 target/$PROJECT_BUILD_FINAL_NAME/ /usr/local/tomcat/webapps/ROOT/ 33 | -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref d2ba187d-929a-456f-8e7f-c004ca191d9a::zbbehmeiqvyyt19yo6kqcyoif: "/target": not found; 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.
- 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AdminCLI.exec at 44.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with AdminCLI.exec (cyclomatic 44). — Refactoring it lifts Cyclomatic Complexity from 8.8 to about 10.0/10.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was ArangoManagerImpl.createDatabase at 57.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with ArangoManagerImpl.createDatabase (cognitive 57), AdminCLI.exec (cognitive 43), Migrator.executeMigration (cognitive 23). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
7 duplicated block group(s) detected. 3.1 % of the production lines (428 of 13,788) are in a reported copy. A further 6 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 13 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with DataSourcesController.scala, Graph.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ExecutionEventRepositoryImpl.scala, AttrOrExprRef.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (79 corresponding lines) finding(s) in Code Duplication — start with DataSourceRepositoryImpl.scala. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
14 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 13 of the 14 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 14 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 14 tests. Measured on the JavaScript/TypeScript suite only — at least 42 test source file(s) (.scala) went unread, so its test quality is unmeasured and is not in these counts.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 16 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 97 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 2 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 13788 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with expressions.scala, persistentDefs.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with JsonPath.scala. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 3 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
1 naming inconsistencies among 50 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `ensureNoExecPlanIDCollision` spells `ID` where 69 names in the project… finding(s) in Naming Consistency — start with ExecutionProducerRepositoryImpl.scala. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
1 of 30 judged comments only repeat the code they sit on (3.3 %). 2 comment(s) in another language or script were not judged.
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with teardown.ts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 13 build units (Maven) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 4 high, 3 medium, 0 low. 4 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 1 file(s) — `test-data-generator/src/main/scala/za/co/absa/spline/testdatagen/NumericValue.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
9 finding(s): 0 critical, 4 high, 4 medium, 1 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 0 high, 3 medium, 2 low.
What to do
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
71 of 71 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is persistence/src/main/scala/za/co/absa/spline/persistence/ArangoCode.scala. Counted over 71 of the 264 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 70 Orphaned file finding(s) in Knowledge Freshness — start with AttrOrExprRef.scala (2), operations.scala (2), AdminCLI.scala. — One of this dimension's main actionable groups (70 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with ArangoCode.scala. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 23 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — kafka-gateway/src/main/webapp/index.html:18, rest-gateway/src/main/webapp/index.html:18
- With more than one navigation landmark, each needs an aria-label/aria-labelledby (e.g. "Primary", "Footer") so assistive tech can tell them apart. At least one nav here is unlabelled. (×2) — kafka-gateway/src/main/webapp/index.html:18, rest-gateway/src/main/webapp/index.html:18
- An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. (×2) — kafka-gateway/src/main/webapp/index.html:56, rest-gateway/src/main/webapp/index.html:56
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. — admin/src/main/scala/za/co/absa/spline/admin/AdminCLI.scala:74
- `resourceNotFound` has an empty body — confirm it's an intentional no-op and not an unfinished method. — commons/src/main/scala/za/co/absa/spline/common/webmvc/controller/DefaultRestController.scala:28
- `publicControllerMethods` has an empty body — confirm it's an intentional no-op and not an unfinished method. — producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/ExecutionPlansControllerMessageLengthCapturingAspect.scala:31
- `acceptsEPv10` has an empty body — confirm it's an intentional no-op and not an unfinished method. — producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/ExecutionPlansControllerMessageLengthCapturingAspect.scala:34
- `acceptsEPv11` has an empty body — confirm it's an intentional no-op and not an unfinished method. — producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/ExecutionPlansControllerMessageLengthCapturingAspect.scala:37
- `acceptsEPv12` has an empty body — confirm it's an intentional no-op and not an unfinished method. — producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/ExecutionPlansControllerMessageLengthCapturingAspect.scala:40
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- Only 6/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `consumer-rest-core`, `producer-rest-core`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `arangodb-foxx-services/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — arangodb-foxx-services/package.json:17
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- 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 hygiene
R1 · Type Safety
R10 · Code Duplication
- REDACTED:30 · REDACTED:51 — 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. — REDACTED:30
- persistence/src/main/resources/migration-scripts/0.4.0-0.5.0.js:239 · persistence/src/main/resources/migration-scripts/0.5.0-0.5.4.js:183 · persistence/src/main/resources/migration-scripts/0.5.5-0.6.1.js:36 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — persistence/src/main/resources/migration-scripts/0.4.0-0.5.0.js:239
- REDACTED:68 · arangodb-foxx-services/src/main/routes/plans-router.ts:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:68
- arangodb-foxx-services/src/main/services/impact-overview.ts:39 · arangodb-foxx-services/src/main/services/lineage-overview.ts:39 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — arangodb-foxx-services/src/main/services/impact-overview.ts:39
- persistence/src/main/resources/migration-scripts/0.5.0-0.5.4.js:190 · persistence/src/main/resources/migration-scripts/0.5.5-0.6.1.js:43 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — persistence/src/main/resources/migration-scripts/0.5.0-0.5.4.js:190
- arangodb-foxx-services/src/main/services/prune-database.ts:73 · arangodb-foxx-services/src/main/services/prune-database.ts:119 — 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. — arangodb-foxx-services/src/main/services/prune-database.ts:73
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×29) — persistence/src/main/resources/migration-scripts/0.5.5-0.6.1.js:1, persistence/src/main/resources/migration-scripts/0.4.0-0.5.0.js:1, persistence/src/main/resources/migration-scripts/0.5.0-0.5.4.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 12 application, 6 tooling and 7 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (12 application, 6 tooling, 7 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (arangodb-foxx-services/src/modules/consumer-index-update/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — arangodb-foxx-services/src/modules/consumer-index-update/data-source.last-write.update.ts
- no import path from any entry point (12 application, 6 tooling, 7 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — arangodb-foxx-services/src/modules/consumer-index-update/index.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in rest-gateway/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- arangodb-foxx-services/src/main/services/store.ts → arangodb-foxx-services/src/main/services/txm/index.ts → arangodb-foxx-services/src/main/services/txm/tx-manager-impl.ts → arangodb-foxx-services/src/main/services/store.ts — arangodb-foxx-services/src/main/services/store.ts:20
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `NoopHostnameVerifier.INSTANCE` 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. (×2) — commons/src/main/scala/za/co/absa/spline/common/rest/RESTClientApacheHttpImpl.scala:100, commons/src/main/scala/za/co/absa/spline/common/security/TLSUtils.scala:26
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. This repository constructs a TLS client that accepts any certificate at 2 sites, not one: `commons/src/main/scala/za/co/absa/spline/common/rest/RESTClientApacheHttpImpl.scala:100` (`NoopHostnameVerifier.INSTANCE`), `commons/src/main/scala/za/co/absa/spline/common/security/TLSUtils.scala:26` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain (through `TrustAll`)). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X5 · Nullable reference types
- No build over this repository's 221 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Strong | Solid. |
| Maturity | 43% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 39% | Weak — gated by R4, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Strong | Solid. |
| Accessibility | 76% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase
- 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.
- AC6 Visual & motion safety — No styled element found in the parsed markup — AC6 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — docker build failed (exit 1) — ------ REDACTED:32 -------------------- 30 | USER 1001 31 | ARG PROJECT_BUILD_FINAL_NAME 32 | >>> COPY --chown=1001 target/$PROJECT_BUILD_FINAL_NAME/ /usr/local/tomcat/webapps/ROOT/ 33 | -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref d2ba187d-929a-456f-8e7f-c004ca191d9a::zbbehmeiqvyyt19yo6kqcyoif: "/target": not found; 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.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
- D12 Dependency Hygiene — Not scored — a Maven build resolved 155 artifact(s) (135 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- 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) — 2 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 55 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 5 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (command argument 5); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — 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.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript source (service entry point: producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/IngestionController.scala:30 (@Controller))
- 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 data present for 3 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TLS certificate validation disabled commons/src/main/scala/za/co/absa/spline/common/rest/RESTClientApacheHttpImpl.scala:100
- TLS certificate validation disabled commons/src/main/scala/za/co/absa/spline/common/security/TLSUtils.scala:26
- Import cycle (3 files) arangodb-foxx-services/src/main/services/store.ts:20
Serious — 78 finding(s)
- No test reaches this file persistence/src/main/resources/migration-scripts/0.5.5-0.6.1.js:1
- No test reaches this file persistence/src/main/resources/migration-scripts/0.4.0-0.5.0.js:1
- No test reaches this file persistence/src/main/resources/migration-scripts/0.5.0-0.5.4.js:1
- No test reaches this file persistence/src/main/resources/migration-scripts/0.7.0-1.0.0.js:1
- No test reaches this file arangodb-foxx-services/src/main/services/txm/tx-manager-impl.ts:1
- No test reaches this file arangodb-foxx-services/src/main/services/commons.ts:1
- No test reaches this file arangodb-foxx-services/src/main/services/prune-database.ts:1
- No test reaches this file arangodb-foxx-services/src/main/services/execution-event-store.ts:1
- No test reaches this file arangodb-foxx-services/src/modules/consumer-index-update/data-source.last-write.update.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file arangodb-foxx-services/src/main/services/observed-reads-by-write.ts:1
- No test reaches this file arangodb-foxx-services/src/main/services/execution-plan-store.ts:1
- No test reaches this file arangodb-foxx-services/src/main/services/observed-writes-by-read.ts:1
- No test reaches this file arangodb-foxx-services/src/main/services/store.ts:1
- No test reaches this file arangodb-foxx-services/src/main/utils/graph.ts:1
- No test reaches this file persistence/src/main/resources/migration-scripts/0.6.1-0.7.0.js:1
- No test reaches this file arangodb-foxx-services/src/main/services/impact-overview.ts:1
- No test reaches this file arangodb-foxx-services/src/main/services/lineage-overview.ts:1
- No test reaches this file arangodb-foxx-services/src/scripts/setup.ts:1
- No test reaches this file arangodb-foxx-services/src/main/routes/admin-router.ts:1
- No test reaches this file arangodb-foxx-services/src/main/routes/plans-router.ts:1
- No test reaches this file persistence/src/main/resources/migration-scripts/template.js:1
- No test reaches this file persistence/src/main/resources/migration-scripts/0.6.0-0.6.1.js:1
- No test reaches this file arangodb-foxx-services/src/main/routes/index.ts:1
- No test reaches this file persistence/src/main/resources/migration-scripts/0.5.4-0.5.5.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark kafka-gateway/src/main/webapp/index.html:18
- Page without a main landmark rest-gateway/src/main/webapp/index.html:18
- Multiple navigation landmarks without distinguishing labels kafka-gateway/src/main/webapp/index.html:18
- Multiple navigation landmarks without distinguishing labels rest-gateway/src/main/webapp/index.html:18
- Empty <h6> heading kafka-gateway/src/main/webapp/index.html:56
- Empty <h6> heading rest-gateway/src/main/webapp/index.html:56
- TodoComment producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/expressions.scala:24
- TodoComment persistence/src/main/scala/za/co/absa/spline/persistence/model/persistentDefs.scala:62
- REDACTED
- REDACTED
- Edited copy of a member (15 corresponding lines) consumer-rest-core/src/main/scala/za/co/absa/spline/consumer/rest/controller/DataSourcesController.scala:80
- Edited copy of a member (15 corresponding lines) test-data-generator/src/main/scala/za/co/absa/spline/testdatagen/generators/Graph.scala:51
- Duplicated block (7 lines × 2) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/ExecutionEventRepositoryImpl.scala:88
- Duplicated block (7 lines × 2) producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/AttrOrExprRef.scala:66
- Off the main sequence: arangodb-foxx-api
- Off the main sequence: producer-model
- AdminCLI.exec (cyclomatic 44) admin/src/main/scala/za/co/absa/spline/admin/AdminCLI.scala:72
- FixmeComment commons/src/main/scala/za/co/absa/spline/common/JsonPath.scala:66
- ArangoManagerImpl.createDatabase (cognitive 57) admin/src/main/scala/za/co/absa/spline/arango/ArangoManager.scala:73
- AdminCLI.exec (cognitive 43) admin/src/main/scala/za/co/absa/spline/admin/AdminCLI.scala:72
- Migrator.executeMigration (cognitive 23) persistence/src/main/scala/za/co/absa/spline/persistence/migration/Migrator.scala:78
- REDACTED
- REDACTED
- Edited copy of a member (79 corresponding lines) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala:114
- Edited copy of a member (53 corresponding lines) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala:46
- Edited copy of a member (8 corresponding lines) producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/AttrOrExprRef.scala:65
- Edited copy of a member (21 corresponding lines) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/LabelRepositoryImpl.scala:33
- Duplicated block (41–55 lines × 2) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala:51
- Duplicated block (38–52 lines × 2) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/ExecutionEventRepositoryImpl.scala:50
- Duplicated block (12 lines × 2) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala:184
- Duplicated block (6 lines × 2) consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala:176
- Duplicated block (31 lines × 2) producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/executionPlan.scala:40
- Duplicated block (12 lines × 2 locations) REDACTED:30
- Duplicated block (12 lines × 3 locations) persistence/src/main/resources/migration-scripts/0.4.0-0.5.0.js:239
- Duplicated block (11 lines × 2 locations) REDACTED:68
- Duplicated block (8 lines × 2 locations) arangodb-foxx-services/src/main/services/impact-overview.ts:39
- Duplicated block (7 lines × 2 locations) persistence/src/main/resources/migration-scripts/0.5.0-0.5.4.js:190
- Duplicated block (6 lines × 2 locations) arangodb-foxx-services/src/main/services/prune-database.ts:73
- No typecheck script
- Dead file (~87 LoC) arangodb-foxx-services/src/modules/consumer-index-update/data-source.last-write.update.ts
- Dead file (~17 LoC) arangodb-foxx-services/src/modules/consumer-index-update/index.ts
- Unused dependency '@redocly/cli'
Minor — 96 finding(s)
- Orphaned file admin/src/main/scala/za/co/absa/spline/admin/AdminCLI.scala:1
- Orphaned file producer-services/src/main/scala/za/co/absa/spline/producer/service/model/ExecutionPlanPersistentModelBuilder.scala:1
- Orphaned file persistence/src/main/scala/za/co/absa/spline/persistence/model/persistentDefs.scala:1
- Orphaned file consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/ExecutionPlanRepositoryImpl.scala:1
- Orphaned file admin/src/main/scala/za/co/absa/spline/arango/ArangoManager.scala:1
- Orphaned file commons/src/main/scala/org/apache/commons/configuration2/ConfigurationImplicits.scala:1
- Orphaned file consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/DataSourceRepositoryImpl.scala:1
- Orphaned file producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/handler/HandlerV12.scala:1
- Orphaned file kafka-gateway/src/main/scala/za/co/absa/spline/gateway/kafka/KafkaGatewayConfig.scala:1
- Orphaned file consumer-services/src/main/scala/za/co/absa/spline/consumer/service/repo/ExecutionEventRepositoryImpl.scala:1
- Orphaned file consumer-rest-core/src/main/scala/za/co/absa/spline/consumer/rest/controller/OperationDetailsController.scala:1
- Orphaned file producer-services/src/main/scala/za/co/absa/spline/producer/service/repo/ExecutionProducerRepositoryImpl.scala:1
- Orphaned file arangodb-foxx-services/src/main/services/prune-database.ts:1
- Orphaned file arangodb-foxx-services/src/main/services/commons.ts:1
- Orphaned file test-data-generator/src/main/scala/za/co/absa/spline/testdatagen/generators/Graph.scala:1
- Orphaned file arangodb-foxx-services/src/main/services/txm/tx-manager-impl.ts:1
- Orphaned file arangodb-foxx-api/src/main/scala/za/co/absa/spline/persistence/model/entities.scala:1
- Orphaned file consumer-rest-core/src/main/scala/za/co/absa/spline/consumer/rest/controller/ExecutionPlansController.scala:1
- Orphaned file producer-model-mapper/src/main/scala/za/co/absa/spline/producer/modelmapper/v1_0/ModelMapperV10.scala:1
- Orphaned file persistence/src/main/scala/za/co/absa/spline/persistence/migration/Migrator.scala:1
- Orphaned file consumer-rest-core/src/main/scala/za/co/absa/spline/consumer/rest/controller/DataSourcesController.scala:1
- Orphaned file consumer-rest-core/src/main/scala/za/co/absa/spline/consumer/rest/controller/ExecutionEventsController.scala:1
- Orphaned file test-data-generator/src/main/scala/za/co/absa/spline/testdatagen/GenCLI.scala:1
- Orphaned file commons/src/main/scala/za/co/absa/spline/common/webmvc/ScalaFutureMethodReturnValueHandler.scala:1
- Orphaned file producer-model-mapper/src/main/scala/za/co/absa/spline/producer/modelmapper/v1_0/spark/SparkSplineExpressionConverter.scala:1
- Empty method body commons/src/main/scala/za/co/absa/spline/common/webmvc/controller/DefaultRestController.scala:28
- Empty method body producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/ExecutionPlansControllerMessageLengthCapturingAspect.scala:31
- Empty method body producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/ExecutionPlansControllerMessageLengthCapturingAspect.scala:34
- Empty method body producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/ExecutionPlansControllerMessageLengthCapturingAspect.scala:37
- Empty method body producer-rest-core/src/main/scala/za/co/absa/spline/producer/rest/controller/ExecutionPlansControllerMessageLengthCapturingAspect.scala:40
- Mock-dominated test: on(TX_START_WRITE) arangodb-foxx-services/tests/main/services/txm/subscribable-tx-manager-decorator.spec.ts:131
- Mock-dominated test: on(TX_PRE_COMMIT | TX_POST_COMMIT) arangodb-foxx-services/tests/main/services/txm/subscribable-tx-manager-decorator.spec.ts:147
- Mock-dominated test: on(TX_PRE_ROLLBACK | TX_POST_ROLLBACK) arangodb-foxx-services/tests/main/services/txm/subscribable-tx-manager-decorator.spec.ts:166
- REDACTED
- REDACTED
- No ADRs found rest-gateway/pom.xml:29
- `ensureNoExecPlanIDCollision` spells `ID` where 69 names in the project spell it `Id` producer-services/src/main/scala/za/co/absa/spline/producer/service/repo/ExecutionProducerRepositoryImpl.scala:153
- redundant comment arangodb-foxx-services/src/scripts/teardown.ts:19
- REDACTED
- Concentrated knowledge decay
- Most significant orphaned file persistence/src/main/scala/za/co/absa/spline/persistence/ArangoCode.scala:1
- REDACTED
- Blanket warning suppression admin/src/main/scala/za/co/absa/spline/admin/AdminCLI.scala:74
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST REDACTED:4
- No dependency-update automation arangodb-foxx-services/package.json:17
- No changelog
- Duplicated predicate arangodb-foxx-services/src/main/services/impact-overview.ts:42
- Scala's null is not held to the type system everywhere
Minor — 1 finding(s)
- Off the main sequence: commons
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-545a3241e6524aac94d070edbd10df75/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-545a3241e6524aac94d070edbd10df75/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 9 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_1/expressions.scala`, `producer-model/src/main/scala/za/co/absa/spline/producer/model/v1_2/expressions.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |