Executive summary
testcontainers/testcontainers-scala is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because we found no recorded design decisions and no architecture document or diagram. It scores 64 out of 100, which the At risk rating leaves unchanged.
Maturity, at 52, is the weakest lens and counts most in the score. The best first step is making the naming consistent, worth about 11 points. Having someone learn and document the nine files no active contributor knows comes next, worth about 7 points. Raising Maturity to 70 would lift the score to about 71.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers, and one password or key is open to anyone who can read the repository. Pinning each tool to an exact version, updating the vulnerable packages and replacing the exposed password or key would close these risks. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 3,717 lines, about €8,100 to rebuild.
If Maturity rose from 52 to 70, the lowest score rated Strong, the score would rise from 64 to about 71.
New since the last survey: 4 findings
- Code Duplication · Edited copy of a member (30 corresponding lines) test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/scalatest/TestContainersForAll.scala
- Code Duplication · Edited copy of a member (29 corresponding lines) test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/ForAllTestContainer.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) test-framework/specs2/src/main/scala/com/dimafeng/testcontainers/specs2/TestContainersForAll.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersForEach.scala
Fixed since the last survey: 1 finding
- Secret Scanning · Leaked secret: REDACTED modules/db2/src/main/scala/com/dimafeng/testcontainers/Db2Container.scala
Rebuild cost: about €8,100 · Estimate
| Cost to rebuild | €2,700 to €14,000, for 45 to 142 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,717 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 lifecycle | 2 DockerComposeContainer | 3 GenericContainer | 4 com.dimafeng.testcontainers | 5 GenericContainer.Def | 6 BigtableEmulatorContainer | 7 CassandraContainer | 8 ClickHouseContainer | 9 CockroachContainer | 10 ConfluentKafkaContainer | 11 CouchbaseContainer | 12 Db2Container | 13 ElasticsearchContainer | 14 FirestoreEmulatorContainer | 15 FixedHostPortGenericContainer | 16 InfluxDBContainer | 17 K3sContainer | 18 KafkaContainer | 19 LocalStackContainer | 20 LocalStackV2Container | 21 MSSQLServerContainer | 22 MariaDBContainer | 23 MilvusContainer | 24 MinIOContainer | 25 MockServerContainer | 26 MongoDBContainer | 27 MySQLContainer | 28 Neo4jContainer | 29 NginxContainer | 30 OpensearchContainer | 31 OracleContainer | 32 OrientDBContainer | 33 PostgreSQLContainer | 34 PrestoContainer | 35 PubSubEmulatorContainer | 36 PulsarContainer | 37 QdrantContainer | 38 RabbitMQContainer | 39 RedisContainer | 40 RedpandaContainer |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 lifecycle | ||||||||||||||||||||||||||||||||||||||||
| 2 DockerComposeContainer | 7 | |||||||||||||||||||||||||||||||||||||||
| 3 GenericContainer | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 com.dimafeng.testcontainers | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 5 GenericContainer.Def | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 BigtableEmulatorContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 CassandraContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 ClickHouseContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 CockroachContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 ConfluentKafkaContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 CouchbaseContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 Db2Container | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 ElasticsearchContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 FirestoreEmulatorContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 FixedHostPortGenericContainer | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 InfluxDBContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 K3sContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 KafkaContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 LocalStackContainer | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 LocalStackV2Container | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 MSSQLServerContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 MariaDBContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 MilvusContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 MinIOContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 MockServerContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 MongoDBContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 MySQLContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 Neo4jContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 NginxContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 OpensearchContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 OracleContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 OrientDBContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 PostgreSQLContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 PrestoContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 PubSubEmulatorContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 PulsarContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 QdrantContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 RabbitMQContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 RedisContainer | 2 | |||||||||||||||||||||||||||||||||||||||
| 40 RedpandaContainer | 2 |
2→4 DockerComposeContainer uses com.dimafeng.testcontainers part of a loop✕
- Connections
- 7 pairs of types, where a type in DockerComposeContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.DockerComposeContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.DockerComposeContainer.Def→com.dimafeng.testcontainers.DockerComposeContainercom.dimafeng.testcontainers.DockerComposeContainer.Def→com.dimafeng.testcontainers.ExposedServicecom.dimafeng.testcontainers.DockerComposeContainer.Def→com.dimafeng.testcontainers.ScaledServicecom.dimafeng.testcontainers.DockerComposeContainer.Def→com.dimafeng.testcontainers.ServiceLogConsumercom.dimafeng.testcontainers.DockerComposeContainer.Def→com.dimafeng.testcontainers.Servicescom.dimafeng.testcontainers.DockerComposeContainer.Def→com.dimafeng.testcontainers.WaitingForService
- Direction
- DockerComposeContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break DockerComposeContainer, while a change to DockerComposeContainer can't break com.dimafeng.testcontainers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→4 GenericContainer uses com.dimafeng.testcontainers part of a loop✕
- Connections
- 1 pair of types, where a type in GenericContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.GenericContainer.Def→com.dimafeng.testcontainers.ContainerDef
- Direction
- GenericContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break GenericContainer, while a change to GenericContainer can't break com.dimafeng.testcontainers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→1 com.dimafeng.testcontainers uses lifecycle✕
- Connections
- 3 pairs of types, where a type in com.dimafeng.testcontainers uses a type in lifecycle.
- The types involved
com.dimafeng.testcontainers.Container→com.dimafeng.testcontainers.lifecycle.Stoppablecom.dimafeng.testcontainers.LazyContainer→com.dimafeng.testcontainers.lifecycle.TestLifecycleAwarecom.dimafeng.testcontainers.MultipleContainers→com.dimafeng.testcontainers.lifecycle.TestLifecycleAware
- Direction
- com.dimafeng.testcontainers uses lifecycle, so a change to lifecycle can break com.dimafeng.testcontainers, while a change to com.dimafeng.testcontainers can't break lifecycle.
- Position
- Below the diagonal: com.dimafeng.testcontainers uses a module listed above it, which is the healthy direction.
4→2 com.dimafeng.testcontainers uses DockerComposeContainer✕
- Connections
- 1 pair of types, where a type in com.dimafeng.testcontainers uses a type in DockerComposeContainer.
- The types involved
com.dimafeng.testcontainers.DockerComposeContainer→com.dimafeng.testcontainers.DockerComposeContainer.ComposeFile
- Direction
- com.dimafeng.testcontainers uses DockerComposeContainer, so a change to DockerComposeContainer can break com.dimafeng.testcontainers, while a change to com.dimafeng.testcontainers can't break DockerComposeContainer.
- Position
- Below the diagonal: com.dimafeng.testcontainers uses a module listed above it, which is the healthy direction.
4→3 com.dimafeng.testcontainers uses GenericContainer✕
- Connections
- 2 pairs of types, where a type in com.dimafeng.testcontainers uses a type in GenericContainer.
- The types involved
com.dimafeng.testcontainers.GenericContainer→com.dimafeng.testcontainers.GenericContainer.DockerImagecom.dimafeng.testcontainers.GenericContainer→com.dimafeng.testcontainers.GenericContainer.FileSystemBind
- Direction
- com.dimafeng.testcontainers uses GenericContainer, so a change to GenericContainer can break com.dimafeng.testcontainers, while a change to com.dimafeng.testcontainers can't break GenericContainer.
- Position
- Below the diagonal: com.dimafeng.testcontainers uses a module listed above it, which is the healthy direction.
5→3 GenericContainer.Def uses GenericContainer✕
- Connections
- 3 pairs of types, where a type in GenericContainer.Def uses a type in GenericContainer.
- The types involved
com.dimafeng.testcontainers.GenericContainer.Def.Default→com.dimafeng.testcontainers.GenericContainer.Defcom.dimafeng.testcontainers.GenericContainer.Def.Default→com.dimafeng.testcontainers.GenericContainer.DockerImagecom.dimafeng.testcontainers.GenericContainer.Def.Default→com.dimafeng.testcontainers.GenericContainer.FileSystemBind
- Direction
- GenericContainer.Def uses GenericContainer, so a change to GenericContainer can break GenericContainer.Def, while a change to GenericContainer.Def can't break GenericContainer.
- Position
- Below the diagonal: GenericContainer.Def uses a module listed above it, which is the healthy direction.
6→4 BigtableEmulatorContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in BigtableEmulatorContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.BigtableEmulatorContainer.Def→com.dimafeng.testcontainers.BigtableEmulatorContainercom.dimafeng.testcontainers.BigtableEmulatorContainer.Def→com.dimafeng.testcontainers.ContainerDef
- Direction
- BigtableEmulatorContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break BigtableEmulatorContainer, while a change to BigtableEmulatorContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: BigtableEmulatorContainer uses a module listed above it, which is the healthy direction.
7→4 CassandraContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in CassandraContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.CassandraContainer.Def→com.dimafeng.testcontainers.CassandraContainercom.dimafeng.testcontainers.CassandraContainer.Def→com.dimafeng.testcontainers.ContainerDef
- Direction
- CassandraContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break CassandraContainer, while a change to CassandraContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: CassandraContainer uses a module listed above it, which is the healthy direction.
8→4 ClickHouseContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in ClickHouseContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.ClickHouseContainer.Def→com.dimafeng.testcontainers.ClickHouseContainercom.dimafeng.testcontainers.ClickHouseContainer.Def→com.dimafeng.testcontainers.ContainerDef
- Direction
- ClickHouseContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break ClickHouseContainer, while a change to ClickHouseContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: ClickHouseContainer uses a module listed above it, which is the healthy direction.
9→4 CockroachContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in CockroachContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.CockroachContainer.Def→com.dimafeng.testcontainers.CockroachContainercom.dimafeng.testcontainers.CockroachContainer.Def→com.dimafeng.testcontainers.ContainerDef
- Direction
- CockroachContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break CockroachContainer, while a change to CockroachContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: CockroachContainer uses a module listed above it, which is the healthy direction.
10→4 ConfluentKafkaContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in ConfluentKafkaContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.ConfluentKafkaContainer.Def→com.dimafeng.testcontainers.ConfluentKafkaContainercom.dimafeng.testcontainers.ConfluentKafkaContainer.Def→com.dimafeng.testcontainers.ContainerDef
- Direction
- ConfluentKafkaContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break ConfluentKafkaContainer, while a change to ConfluentKafkaContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: ConfluentKafkaContainer uses a module listed above it, which is the healthy direction.
11→4 CouchbaseContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in CouchbaseContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.CouchbaseContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.CouchbaseContainer.Def→com.dimafeng.testcontainers.CouchbaseContainer
- Direction
- CouchbaseContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break CouchbaseContainer, while a change to CouchbaseContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: CouchbaseContainer uses a module listed above it, which is the healthy direction.
12→4 Db2Container uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in Db2Container uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.Db2Container.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.Db2Container.Def→com.dimafeng.testcontainers.Db2Container
- Direction
- Db2Container uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break Db2Container, while a change to Db2Container can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: Db2Container uses a module listed above it, which is the healthy direction.
13→4 ElasticsearchContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in ElasticsearchContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.ElasticsearchContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.ElasticsearchContainer.Def→com.dimafeng.testcontainers.ElasticsearchContainer
- Direction
- ElasticsearchContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break ElasticsearchContainer, while a change to ElasticsearchContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: ElasticsearchContainer uses a module listed above it, which is the healthy direction.
14→4 FirestoreEmulatorContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in FirestoreEmulatorContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.FirestoreEmulatorContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.FirestoreEmulatorContainer.Def→com.dimafeng.testcontainers.FirestoreEmulatorContainer
- Direction
- FirestoreEmulatorContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break FirestoreEmulatorContainer, while a change to FirestoreEmulatorContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: FirestoreEmulatorContainer uses a module listed above it, which is the healthy direction.
15→3 FixedHostPortGenericContainer uses GenericContainer✕
- Connections
- 1 pair of types, where a type in FixedHostPortGenericContainer uses a type in GenericContainer.
- The types involved
com.dimafeng.testcontainers.FixedHostPortGenericContainer.Def→com.dimafeng.testcontainers.GenericContainer.FileSystemBind
- Direction
- FixedHostPortGenericContainer uses GenericContainer, so a change to GenericContainer can break FixedHostPortGenericContainer, while a change to FixedHostPortGenericContainer can't break GenericContainer.
- Position
- Below the diagonal: FixedHostPortGenericContainer uses a module listed above it, which is the healthy direction.
15→4 FixedHostPortGenericContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in FixedHostPortGenericContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.FixedHostPortGenericContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.FixedHostPortGenericContainer.Def→com.dimafeng.testcontainers.FixedHostPortGenericContainer
- Direction
- FixedHostPortGenericContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break FixedHostPortGenericContainer, while a change to FixedHostPortGenericContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: FixedHostPortGenericContainer uses a module listed above it, which is the healthy direction.
16→4 InfluxDBContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in InfluxDBContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.InfluxDBContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.InfluxDBContainer.Def→com.dimafeng.testcontainers.InfluxDBContainer
- Direction
- InfluxDBContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break InfluxDBContainer, while a change to InfluxDBContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: InfluxDBContainer uses a module listed above it, which is the healthy direction.
17→4 K3sContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in K3sContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.K3sContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.K3sContainer.Def→com.dimafeng.testcontainers.K3sContainer
- Direction
- K3sContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break K3sContainer, while a change to K3sContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: K3sContainer uses a module listed above it, which is the healthy direction.
18→4 KafkaContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in KafkaContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.KafkaContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.KafkaContainer.Def→com.dimafeng.testcontainers.KafkaContainer
- Direction
- KafkaContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break KafkaContainer, while a change to KafkaContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: KafkaContainer uses a module listed above it, which is the healthy direction.
19→4 LocalStackContainer uses com.dimafeng.testcontainers✕
- Connections
- 3 pairs of types, where a type in LocalStackContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.LocalStackContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.LocalStackContainer.Def→com.dimafeng.testcontainers.LocalStackContainercom.dimafeng.testcontainers.LocalStackContainer.Def→com.dimafeng.testcontainers.Service
- Direction
- LocalStackContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break LocalStackContainer, while a change to LocalStackContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: LocalStackContainer uses a module listed above it, which is the healthy direction.
20→4 LocalStackV2Container uses com.dimafeng.testcontainers✕
- Connections
- 3 pairs of types, where a type in LocalStackV2Container uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.LocalStackV2Container.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.LocalStackV2Container.Def→com.dimafeng.testcontainers.LocalStackV2Containercom.dimafeng.testcontainers.LocalStackV2Container.Def→com.dimafeng.testcontainers.Service
- Direction
- LocalStackV2Container uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break LocalStackV2Container, while a change to LocalStackV2Container can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: LocalStackV2Container uses a module listed above it, which is the healthy direction.
21→4 MSSQLServerContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in MSSQLServerContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.MSSQLServerContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.MSSQLServerContainer.Def→com.dimafeng.testcontainers.MSSQLServerContainer
- Direction
- MSSQLServerContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break MSSQLServerContainer, while a change to MSSQLServerContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: MSSQLServerContainer uses a module listed above it, which is the healthy direction.
22→4 MariaDBContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in MariaDBContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.MariaDBContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.MariaDBContainer.Def→com.dimafeng.testcontainers.MariaDBContainer
- Direction
- MariaDBContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break MariaDBContainer, while a change to MariaDBContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: MariaDBContainer uses a module listed above it, which is the healthy direction.
23→4 MilvusContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in MilvusContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.MilvusContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.MilvusContainer.Def→com.dimafeng.testcontainers.MilvusContainer
- Direction
- MilvusContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break MilvusContainer, while a change to MilvusContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: MilvusContainer uses a module listed above it, which is the healthy direction.
24→4 MinIOContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in MinIOContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.MinIOContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.MinIOContainer.Def→com.dimafeng.testcontainers.MinIOContainer
- Direction
- MinIOContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break MinIOContainer, while a change to MinIOContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: MinIOContainer uses a module listed above it, which is the healthy direction.
25→4 MockServerContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in MockServerContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.MockServerContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.MockServerContainer.Def→com.dimafeng.testcontainers.MockServerContainer
- Direction
- MockServerContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break MockServerContainer, while a change to MockServerContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: MockServerContainer uses a module listed above it, which is the healthy direction.
26→4 MongoDBContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in MongoDBContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.MongoDBContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.MongoDBContainer.Def→com.dimafeng.testcontainers.MongoDBContainer
- Direction
- MongoDBContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break MongoDBContainer, while a change to MongoDBContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: MongoDBContainer uses a module listed above it, which is the healthy direction.
27→4 MySQLContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in MySQLContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.MySQLContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.MySQLContainer.Def→com.dimafeng.testcontainers.MySQLContainer
- Direction
- MySQLContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break MySQLContainer, while a change to MySQLContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: MySQLContainer uses a module listed above it, which is the healthy direction.
28→4 Neo4jContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in Neo4jContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.Neo4jContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.Neo4jContainer.Def→com.dimafeng.testcontainers.Neo4jContainer
- Direction
- Neo4jContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break Neo4jContainer, while a change to Neo4jContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: Neo4jContainer uses a module listed above it, which is the healthy direction.
29→4 NginxContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in NginxContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.NginxContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.NginxContainer.Def→com.dimafeng.testcontainers.NginxContainer
- Direction
- NginxContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break NginxContainer, while a change to NginxContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: NginxContainer uses a module listed above it, which is the healthy direction.
30→4 OpensearchContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in OpensearchContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.OpensearchContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.OpensearchContainer.Def→com.dimafeng.testcontainers.OpensearchContainer
- Direction
- OpensearchContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break OpensearchContainer, while a change to OpensearchContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: OpensearchContainer uses a module listed above it, which is the healthy direction.
31→4 OracleContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in OracleContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.OracleContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.OracleContainer.Def→com.dimafeng.testcontainers.OracleContainer
- Direction
- OracleContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break OracleContainer, while a change to OracleContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: OracleContainer uses a module listed above it, which is the healthy direction.
32→4 OrientDBContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in OrientDBContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.OrientDBContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.OrientDBContainer.Def→com.dimafeng.testcontainers.OrientDBContainer
- Direction
- OrientDBContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break OrientDBContainer, while a change to OrientDBContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: OrientDBContainer uses a module listed above it, which is the healthy direction.
33→4 PostgreSQLContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in PostgreSQLContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.PostgreSQLContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.PostgreSQLContainer.Def→com.dimafeng.testcontainers.PostgreSQLContainer
- Direction
- PostgreSQLContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break PostgreSQLContainer, while a change to PostgreSQLContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: PostgreSQLContainer uses a module listed above it, which is the healthy direction.
34→4 PrestoContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in PrestoContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.PrestoContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.PrestoContainer.Def→com.dimafeng.testcontainers.PrestoContainer
- Direction
- PrestoContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break PrestoContainer, while a change to PrestoContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: PrestoContainer uses a module listed above it, which is the healthy direction.
35→4 PubSubEmulatorContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in PubSubEmulatorContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.PubSubEmulatorContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.PubSubEmulatorContainer.Def→com.dimafeng.testcontainers.PubSubEmulatorContainer
- Direction
- PubSubEmulatorContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break PubSubEmulatorContainer, while a change to PubSubEmulatorContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: PubSubEmulatorContainer uses a module listed above it, which is the healthy direction.
36→4 PulsarContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in PulsarContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.PulsarContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.PulsarContainer.Def→com.dimafeng.testcontainers.PulsarContainer
- Direction
- PulsarContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break PulsarContainer, while a change to PulsarContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: PulsarContainer uses a module listed above it, which is the healthy direction.
37→4 QdrantContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in QdrantContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.QdrantContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.QdrantContainer.Def→com.dimafeng.testcontainers.QdrantContainer
- Direction
- QdrantContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break QdrantContainer, while a change to QdrantContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: QdrantContainer uses a module listed above it, which is the healthy direction.
38→4 RabbitMQContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in RabbitMQContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.RabbitMQContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.RabbitMQContainer.Def→com.dimafeng.testcontainers.RabbitMQContainer
- Direction
- RabbitMQContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break RabbitMQContainer, while a change to RabbitMQContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: RabbitMQContainer uses a module listed above it, which is the healthy direction.
39→4 RedisContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in RedisContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.RedisContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.RedisContainer.Def→com.dimafeng.testcontainers.RedisContainer
- Direction
- RedisContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break RedisContainer, while a change to RedisContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: RedisContainer uses a module listed above it, which is the healthy direction.
40→4 RedpandaContainer uses com.dimafeng.testcontainers✕
- Connections
- 2 pairs of types, where a type in RedpandaContainer uses a type in com.dimafeng.testcontainers.
- The types involved
com.dimafeng.testcontainers.RedpandaContainer.Def→com.dimafeng.testcontainers.ContainerDefcom.dimafeng.testcontainers.RedpandaContainer.Def→com.dimafeng.testcontainers.RedpandaContainer
- Direction
- RedpandaContainer uses com.dimafeng.testcontainers, so a change to com.dimafeng.testcontainers can break RedpandaContainer, while a change to RedpandaContainer can't break com.dimafeng.testcontainers.
- Position
- Below the diagonal: RedpandaContainer 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 — 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 |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 `s3URL` spells `URL` where 16 names in the project spell it `Url` finding(s) in Naming Consistency — start with MinIOContainer.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 9 Orphaned file finding(s) in Knowledge Freshness — start with TestContainersSuite.scala (2), TestContainersFixtures.scala, GenericContainer.scala.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 `s3URL` spells `URL` where 16 names in the project spell it `Url` finding(s) in Naming Consistency — start with MinIOContainer.scala. | +10.6 pts | Low | Naming Consistency |
| Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with TestContainersSuite.scala (2), TestContainersFixtures.scala, GenericContainer.scala. | +6.7 pts | Low | 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. | +8.8 pts | Medium | Architecture documentation |
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +3.9 pts | Low | Secret Scanning |
| Expand the README with getting-started, architecture overview and a project map. | +4.8 pts | Medium | Documentation (README) |
| Resolve the 1 Banned license finding(s) in License Compliance. | +2.2 pts | Low | License Compliance |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +2.9 pts | Medium | Security & performance tooling |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +2.8 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersForEach.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/scalatest/TestContainersForAll.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (30 corresponding lines) |
| test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/ForAllTestContainer.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (29 corresponding lines) |
| test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersForAll.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/src/main/scala/com/dimafeng/testcontainers/Container.scala | 8.5 | Near-clean | God Classes: TooManyMethods: SingleContainer |
| test-framework/specs2/src/main/scala/com/dimafeng/testcontainers/specs2/TestContainersForAll.scala | 8.5 | Near-clean | Code Duplication: Edited copy of a member (11 corresponding lines) |
| test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersSuite.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| modules/minio/src/main/scala/com/dimafeng/testcontainers/MinIOContainer.scala | 9.5 | Near-clean | Naming Consistency: `s3URL` spells `URL` where 16 names in the project spell it `Url` |
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 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 42 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, 44 of 85 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 77 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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: it declares a published package (build.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — 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.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'java.sql.Connection' is imported (modules/trino/src/main/scala/com/dimafeng/testcontainers/TrinoContainer.scala:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'java.sql.Connection' is imported (modules/trino/src/main/scala/com/dimafeng/testcontainers/TrinoContainer.scala:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'java.sql.Connection' is imported (modules/trino/src/main/scala/com/dimafeng/testcontainers/TrinoContainer.scala:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
Limitations & what we did not check
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Container.scala. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 4.4 % of the production lines (163 of 3,717) are in a reported copy. A further 4 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 7 of the 7 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 (11 corresponding lines) finding(s) in Code Duplication — start with TestContainersForAll.scala, TestContainersForEach.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (30 corresponding lines) finding(s) in Code Duplication — start with TestContainersForAll.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (29 corresponding lines) finding(s) in Code Duplication — start with ForAllTestContainer.scala. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
45 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 3 module(s) off the main sequence, with abstractness counted on 43 of the 45 (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 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D12 · Dependency Hygiene
30 outdated direct sbt declarations. 69 of 70 direct declarations were graded against Maven Central (1 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
1 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
1 of 69 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 2 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 1 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 1 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.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 13 of the 76 production source files in this repository: 59 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
D17 · Explicit Debt
2 deducted task-comment markers across 3717 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with TestContainersForAll.scala, TestContainersForEach.scala. — One of this dimension's main actionable groups (2 warning-level).
D21 · Naming Consistency
1 naming inconsistencies among 17 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `s3URL` spells `URL` where 16 names in the project spell it `Url` finding(s) in Naming Consistency — start with MinIOContainer.scala. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. 7 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. 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
- No action in Static Analysis (SAST) — all 7 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 (7 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 1 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
9 of 17 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/fixtures/TestContainersFixtures.scala. Counted over 17 of the 76 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 9 Orphaned file finding(s) in Knowledge Freshness — start with TestContainersSuite.scala (2), TestContainersFixtures.scala, GenericContainer.scala. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×9) — test-framework/munit/src/test/scala/com/dimafeng/testcontainers/munit/TestContainerForAllSpec.scala:153, test-framework/munit/src/test/scala/com/dimafeng/testcontainers/munit/TestContainerForEachSpec.scala:170, test-framework/munit/src/test/scala/com/dimafeng/testcontainers/munit/TestContainersForAllSpec.scala:247, …
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)
- The root README is 92 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X27 · Collection changed while being enumerated
X5 · Nullable reference types
- No build over this repository's 53 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 52% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'java.sql.Connection' (modules/trino/src/main/scala/com/dimafeng/testcontainers/TrinoContainer.scala:3) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'java.sql.Connection' (modules/trino/src/main/scala/com/dimafeng/testcontainers/TrinoContainer.scala:3) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'java.sql.Connection' (modules/trino/src/main/scala/com/dimafeng/testcontainers/TrinoContainer.scala:3) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~3297 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (3717 LoC, 200 module-visible types across 47 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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) — 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.
- 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 included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 82 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (1 module(s), 54 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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.
- S1 Web-Security Posture — No web surface: 53 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — 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
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: mysql:mysql-connector-java
- REDACTED
Serious — 16 finding(s)
- Off the main sequence: specs2
- Off the main sequence: jdbc
- Off the main sequence: core
- TodoComment test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersForAll.scala:64
- TodoComment test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersForEach.scala:56
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) test-framework/specs2/src/main/scala/com/dimafeng/testcontainers/specs2/TestContainersForAll.scala:22
- Edited copy of a member (11 corresponding lines) test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersForEach.scala:42
- TooManyMethods: SingleContainer core/src/main/scala/com/dimafeng/testcontainers/Container.scala:31
- REDACTED
- Edited copy of a member (30 corresponding lines) test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/scalatest/TestContainersForAll.scala:62
- Edited copy of a member (29 corresponding lines) test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/ForAllTestContainer.scala:31
- Duplicated block (23 lines × 2) test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/ForAllTestContainer.scala:36
- Duplicated block (17 lines × 2) test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/scalatest/TestContainersForAll.scala:69
- Duplicated block (11 lines × 2) test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersSuite.scala:97
Minor — 26 finding(s)
- Orphaned file test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/fixtures/TestContainersFixtures.scala:1
- Orphaned file core/src/main/scala/com/dimafeng/testcontainers/GenericContainer.scala:1
- Orphaned file core/src/main/scala/com/dimafeng/testcontainers/FixedHostPortGenericContainer.scala:1
- Orphaned file test-framework/munit/src/main/scala/com/dimafeng/testcontainers/munit/TestContainersSuite.scala:1
- Orphaned file test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/scalatest/TestContainersSuite.scala:1
- Orphaned file modules/gcloud/src/main/scala/com/dimafeng/testcontainers/PubSubEmulatorContainer.scala:1
- Orphaned file test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/scalatest/TestContainersForAll.scala:1
- Orphaned file test-framework/scalatest/src/main/scala/com/dimafeng/testcontainers/scalatest/TestContainersForEach.scala:1
- Orphaned file modules/rabbitmq/src/main/scala/com/dimafeng/testcontainers/RabbitMQContainer.scala:1
- Disabled test test-framework/munit/src/test/scala/com/dimafeng/testcontainers/munit/TestContainerForAllSpec.scala:153
- Disabled test test-framework/munit/src/test/scala/com/dimafeng/testcontainers/munit/TestContainerForEachSpec.scala:170
- Disabled test test-framework/munit/src/test/scala/com/dimafeng/testcontainers/munit/TestContainersForAllSpec.scala:247
- Disabled test test-framework/munit/src/test/scala/com/dimafeng/testcontainers/munit/TestContainersForEachSpec.scala:247
- Disabled test test-framework/scalatest/src/test/scala/com/dimafeng/testcontainers/ContainerSpec.scala:172
- Disabled test test-framework/scalatest/src/test/scala/com/dimafeng/testcontainers/scalatest/TestContainerForAllSpec.scala:146
- Disabled test test-framework/scalatest/src/test/scala/com/dimafeng/testcontainers/scalatest/TestContainerForEachSpec.scala:146
- Disabled test test-framework/scalatest/src/test/scala/com/dimafeng/testcontainers/scalatest/TestContainersForAllSpec.scala:218
- Disabled test test-framework/scalatest/src/test/scala/com/dimafeng/testcontainers/scalatest/TestContainersForEachSpec.scala:215
- `s3URL` spells `URL` where 16 names in the project spell it `Url` modules/minio/src/main/scala/com/dimafeng/testcontainers/MinIOContainer.scala:19
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- Scala's null is not held to the type system everywhere
Minor — 30 finding(s)
- Outdated: com.amazonaws:aws-java-sdk-s3
- Outdated: com.amazonaws:aws-java-sdk-sqs
- Outdated: com.datastax.oss:java-driver-core
- Outdated: com.google.cloud:google-cloud-bigtable
- Outdated: com.google.cloud:google-cloud-firestore
- Outdated: com.google.cloud:google-cloud-pubsub
- Outdated: com.oracle.database.jdbc:ojdbc8
- Outdated: com.redis:testcontainers-redis
- Outdated: com.softwaremill.sttp.client3:core_2.12
- Outdated: com.yugabyte:java-driver-core
- Outdated: com.yugabyte:jdbc-yugabytedb
- Outdated: io.milvus:milvus-sdk-java
- Outdated: io.qdrant:client
- Outdated: io.rest-assured:scala-support
- Outdated: mysql:mysql-connector-java
- Outdated: org.apache.kafka:kafka-clients
- Outdated: org.codehaus.groovy:groovy
- Outdated: org.influxdb:influxdb-java
- Outdated: org.mock-server:mockserver-client-java
- Outdated: org.mockito:mockito-core
- Outdated: org.neo4j.driver:neo4j-java-driver
- Outdated: org.opensearch:opensearch-testcontainers
- Outdated: org.postgresql:postgresql
- Outdated: org.scalameta:munit_2.12
- Outdated: org.scalatest:scalatest_2.12
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-b5b56c4bc5cb41d4a062dae08f7e3f04/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-b5b56c4bc5cb41d4a062dae08f7e3f04/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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-50668b8fe12a4154b2c72af412b2b1f3 | 4 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | 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. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-50668b8fe12a4154b2c72af412b2b1f3 | 0 | artifacts/raw/osv-scanner.json |