Executive summary
scalameta/munit falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 60 out of 100 and is rated Adequate, and all 12 of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 50, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 10 points. Completing the README is another step, worth about 6 points. Raising Maturity to 70 would lift the score to about 67.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one secret can leak from the build pipeline. Pinning each tool to an exact version, setting a waiting period for automatic updates and limiting the secret to its own step would close these risks.
The product code is 6,351 lines, about €10,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Maturity rose from 50 to 70, the lowest score rated Strong, the score would rise from 60 to about 67.
Fixed since the last survey: 1 finding
- Dependency Vulnerabilities · High CVE: [GHSA redacted] package-lock.json
Rebuild cost: about €10,000 · Estimate
| Cost to rebuild | €3,300 to €17,000, for 55 to 175 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.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,351 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 java.lang.annotation | 2 munit.ValueTransforms | 3 munit.diff.Delta | 4 munit.internal.FutureCompat | 5 munit.internal.MacroCompat | 6 munit.internal.PlatformCompat | 7 munit.internal.io | 8 munit.internal.io.PlatformIO | 9 munit.internal.junitinterface.RunSettings | 10 munit.sbtmunit.MUnitTestReport | 11 org.junit | 12 website.core.Footer | 13 website.pages | 14 website.pages.en | 15 munit.MUnitRunner | 16 munit.SuiteTransforms | 17 munit.TestTransforms | 18 munit.diff | 19 munit.diff.Delta.TYPE | 20 munit.internal.junitinterface.RunSettings.LogMode | 21 munit.sbtmunit | 22 org.junit.experimental.categories | 23 org.junit.runner.notification | 24 munit.diff.console | 25 munit.internal.junitinterface.MUnitRunNotifier | 26 munit.sbtmunit.MUnitPlugin | 27 org.junit.runner | 28 org.junit.runner.manipulation | 29 munit.internal.junitinterface | 30 (global) | 31 munit | 32 docs | 33 munit.FunFixtures | 34 munit.TestValues | 35 munit.docs | 36 munit.internal | 37 munit.internal.console |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 java.lang.annotation | |||||||||||||||||||||||||||||||||||||
| 2 munit.ValueTransforms | |||||||||||||||||||||||||||||||||||||
| 3 munit.diff.Delta | |||||||||||||||||||||||||||||||||||||
| 4 munit.internal.FutureCompat | |||||||||||||||||||||||||||||||||||||
| 5 munit.internal.MacroCompat | |||||||||||||||||||||||||||||||||||||
| 6 munit.internal.PlatformCompat | |||||||||||||||||||||||||||||||||||||
| 7 munit.internal.io | |||||||||||||||||||||||||||||||||||||
| 8 munit.internal.io.PlatformIO | |||||||||||||||||||||||||||||||||||||
| 9 munit.internal.junitinterface.RunSettings | |||||||||||||||||||||||||||||||||||||
| 10 munit.sbtmunit.MUnitTestReport | |||||||||||||||||||||||||||||||||||||
| 11 org.junit | |||||||||||||||||||||||||||||||||||||
| 12 website.core.Footer | |||||||||||||||||||||||||||||||||||||
| 13 website.pages | |||||||||||||||||||||||||||||||||||||
| 14 website.pages.en | |||||||||||||||||||||||||||||||||||||
| 15 munit.MUnitRunner | 1 | ||||||||||||||||||||||||||||||||||||
| 16 munit.SuiteTransforms | 1 | ||||||||||||||||||||||||||||||||||||
| 17 munit.TestTransforms | 1 | ||||||||||||||||||||||||||||||||||||
| 18 munit.diff | 4 | ||||||||||||||||||||||||||||||||||||
| 19 munit.diff.Delta.TYPE | 3 | ||||||||||||||||||||||||||||||||||||
| 20 munit.internal.junitinterface.RunSettings.LogMode | 5 | ||||||||||||||||||||||||||||||||||||
| 21 munit.sbtmunit | 6 | ||||||||||||||||||||||||||||||||||||
| 22 org.junit.experimental.categories | 1 | ||||||||||||||||||||||||||||||||||||
| 23 org.junit.runner.notification | 2 | ||||||||||||||||||||||||||||||||||||
| 24 munit.diff.console | 1 | ||||||||||||||||||||||||||||||||||||
| 25 munit.internal.junitinterface.MUnitRunNotifier | 1 | ||||||||||||||||||||||||||||||||||||
| 26 munit.sbtmunit.MUnitPlugin | 1 | ||||||||||||||||||||||||||||||||||||
| 27 org.junit.runner | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 28 org.junit.runner.manipulation | 1 | ||||||||||||||||||||||||||||||||||||
| 29 munit.internal.junitinterface | 1 | 6 | 15 | 9 | |||||||||||||||||||||||||||||||||
| 30 (global) | 1 | ||||||||||||||||||||||||||||||||||||
| 31 munit | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 2 | 2 | 7 | |||||||||||||||||||||||||
| 32 docs | 1 | ||||||||||||||||||||||||||||||||||||
| 33 munit.FunFixtures | 2 | ||||||||||||||||||||||||||||||||||||
| 34 munit.TestValues | 1 | ||||||||||||||||||||||||||||||||||||
| 35 munit.docs | 1 | ||||||||||||||||||||||||||||||||||||
| 36 munit.internal | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 munit.internal.console | 1 | 1 | 3 |
15→31 munit.MUnitRunner uses munit part of a loop✕
- Connections
- 1 pair of types, where a type in munit.MUnitRunner uses a type in munit.
- The types involved
munit.MUnitRunner.BeforeAllResult→munit.AnyFixture
- Direction
- munit.MUnitRunner uses munit, so a change to munit can break munit.MUnitRunner, while a change to munit.MUnitRunner can't break munit.
- 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.
16→31 munit.SuiteTransforms uses munit part of a loop✕
- Connections
- 1 pair of types, where a type in munit.SuiteTransforms uses a type in munit.
- The types involved
munit.SuiteTransforms.SuiteTransform→munit.Test
- Direction
- munit.SuiteTransforms uses munit, so a change to munit can break munit.SuiteTransforms, while a change to munit.SuiteTransforms can't break munit.
- 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.
17→31 munit.TestTransforms uses munit part of a loop✕
- Connections
- 1 pair of types, where a type in munit.TestTransforms uses a type in munit.
- The types involved
munit.TestTransforms.TestTransform→munit.Test
- Direction
- munit.TestTransforms uses munit, so a change to munit can break munit.TestTransforms, while a change to munit.TestTransforms can't break munit.
- 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.
18→3 munit.diff uses munit.diff.Delta✕
- Connections
- 4 pairs of types, where a type in munit.diff uses a type in munit.diff.Delta.
- The types involved
munit.diff.ChangeDelta→munit.diff.Delta.TYPEmunit.diff.DeleteDelta→munit.diff.Delta.TYPEmunit.diff.Delta→munit.diff.Delta.TYPEmunit.diff.InsertDelta→munit.diff.Delta.TYPE
- Direction
- munit.diff uses munit.diff.Delta, so a change to munit.diff.Delta can break munit.diff, while a change to munit.diff can't break munit.diff.Delta.
- Position
- Below the diagonal: munit.diff uses a module listed above it, which is the healthy direction.
19→3 munit.diff.Delta.TYPE uses munit.diff.Delta✕
- Connections
- 3 pairs of types, where a type in munit.diff.Delta.TYPE uses a type in munit.diff.Delta.
- The types involved
munit.diff.Delta.TYPE.CHANGE→munit.diff.Delta.TYPEmunit.diff.Delta.TYPE.DELETE→munit.diff.Delta.TYPEmunit.diff.Delta.TYPE.INSERT→munit.diff.Delta.TYPE
- Direction
- munit.diff.Delta.TYPE uses munit.diff.Delta, so a change to munit.diff.Delta can break munit.diff.Delta.TYPE, while a change to munit.diff.Delta.TYPE can't break munit.diff.Delta.
- Position
- Below the diagonal: munit.diff.Delta.TYPE uses a module listed above it, which is the healthy direction.
20→9 munit.internal.junitinterface.RunSettings.LogMode uses munit.internal.junitinterface.RunSettings✕
- Connections
- 5 pairs of types, where a type in munit.internal.junitinterface.RunSettings.LogMode uses a type in munit.internal.junitinterface.RunSettings.
- The types involved
munit.internal.junitinterface.RunSettings.LogMode.Debug→munit.internal.junitinterface.RunSettings.LogModemunit.internal.junitinterface.RunSettings.LogMode.Error→munit.internal.junitinterface.RunSettings.LogModemunit.internal.junitinterface.RunSettings.LogMode.Info→munit.internal.junitinterface.RunSettings.LogModemunit.internal.junitinterface.RunSettings.LogMode.Trace→munit.internal.junitinterface.RunSettings.LogModemunit.internal.junitinterface.RunSettings.LogMode.Warn→munit.internal.junitinterface.RunSettings.LogMode
- Direction
- munit.internal.junitinterface.RunSettings.LogMode uses munit.internal.junitinterface.RunSettings, so a change to munit.internal.junitinterface.RunSettings can break munit.internal.junitinterface.RunSettings.LogMode, while a change to munit.internal.junitinterface.RunSettings.LogMode can't break munit.internal.junitinterface.RunSettings.
- Position
- Below the diagonal: munit.internal.junitinterface.RunSettings.LogMode uses a module listed above it, which is the healthy direction.
21→10 munit.sbtmunit uses munit.sbtmunit.MUnitTestReport✕
- Connections
- 6 pairs of types, where a type in munit.sbtmunit uses a type in munit.sbtmunit.MUnitTestReport.
- The types involved
munit.sbtmunit.MUnitGcpListener→munit.sbtmunit.MUnitTestReport.Summarymunit.sbtmunit.MUnitLocalListener→munit.sbtmunit.MUnitTestReport.Summarymunit.sbtmunit.MUnitReportListener→munit.sbtmunit.MUnitTestReport.Summarymunit.sbtmunit.MUnitTestsListener→munit.sbtmunit.MUnitTestReport.Summarymunit.sbtmunit.MUnitTestsListener→munit.sbtmunit.MUnitTestReport.TestEventmunit.sbtmunit.MUnitTestsListener→munit.sbtmunit.MUnitTestReport.TestException
- Direction
- munit.sbtmunit uses munit.sbtmunit.MUnitTestReport, so a change to munit.sbtmunit.MUnitTestReport can break munit.sbtmunit, while a change to munit.sbtmunit can't break munit.sbtmunit.MUnitTestReport.
- Position
- Below the diagonal: munit.sbtmunit uses a module listed above it, which is the healthy direction.
22→1 org.junit.experimental.categories uses java.lang.annotation✕
- Connections
- 1 pair of types, where a type in org.junit.experimental.categories uses a type in java.lang.annotation.
- The types involved
org.junit.experimental.categories.Category→java.lang.annotation.Annotation
- Direction
- org.junit.experimental.categories uses java.lang.annotation, so a change to java.lang.annotation can break org.junit.experimental.categories, while a change to org.junit.experimental.categories can't break java.lang.annotation.
- Position
- Below the diagonal: org.junit.experimental.categories uses a module listed above it, which is the healthy direction.
23→27 org.junit.runner.notification uses org.junit.runner part of a loop✕
- Connections
- 2 pairs of types, where a type in org.junit.runner.notification uses a type in org.junit.runner.
- The types involved
org.junit.runner.notification.Failure→org.junit.runner.Descriptionorg.junit.runner.notification.RunNotifier→org.junit.runner.Description
- Direction
- org.junit.runner.notification uses org.junit.runner, so a change to org.junit.runner can break org.junit.runner.notification, while a change to org.junit.runner.notification can't break org.junit.runner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→18 munit.diff.console uses munit.diff✕
- Connections
- 1 pair of types, where a type in munit.diff.console uses a type in munit.diff.
- The types involved
munit.diff.console.Printers→munit.diff.Printer
- Direction
- munit.diff.console uses munit.diff, so a change to munit.diff can break munit.diff.console, while a change to munit.diff.console can't break munit.diff.
- Position
- Below the diagonal: munit.diff.console uses a module listed above it, which is the healthy direction.
25→23 munit.internal.junitinterface.MUnitRunNotifier uses org.junit.runner.notification✕
- Connections
- 1 pair of types, where a type in munit.internal.junitinterface.MUnitRunNotifier uses a type in org.junit.runner.notification.
- The types involved
munit.internal.junitinterface.MUnitRunNotifier.TestStatus→org.junit.runner.notification.Failure
- Direction
- munit.internal.junitinterface.MUnitRunNotifier uses org.junit.runner.notification, so a change to org.junit.runner.notification can break munit.internal.junitinterface.MUnitRunNotifier, while a change to munit.internal.junitinterface.MUnitRunNotifier can't break org.junit.runner.notification.
- Position
- Below the diagonal: munit.internal.junitinterface.MUnitRunNotifier uses a module listed above it, which is the healthy direction.
26→21 munit.sbtmunit.MUnitPlugin uses munit.sbtmunit✕
- Connections
- 1 pair of types, where a type in munit.sbtmunit.MUnitPlugin uses a type in munit.sbtmunit.
- The types involved
munit.sbtmunit.MUnitPlugin.autoImport→munit.sbtmunit.MUnitReportListener
- Direction
- munit.sbtmunit.MUnitPlugin uses munit.sbtmunit, so a change to munit.sbtmunit can break munit.sbtmunit.MUnitPlugin, while a change to munit.sbtmunit.MUnitPlugin can't break munit.sbtmunit.
- Position
- Below the diagonal: munit.sbtmunit.MUnitPlugin uses a module listed above it, which is the healthy direction.
27→1 org.junit.runner uses java.lang.annotation✕
- Connections
- 2 pairs of types, where a type in org.junit.runner uses a type in java.lang.annotation.
- The types involved
org.junit.runner.Description→java.lang.annotation.Annotationorg.junit.runner.RunWith→java.lang.annotation.Annotation
- Direction
- org.junit.runner uses java.lang.annotation, so a change to java.lang.annotation can break org.junit.runner, while a change to org.junit.runner can't break java.lang.annotation.
- Position
- Below the diagonal: org.junit.runner uses a module listed above it, which is the healthy direction.
27→23 org.junit.runner uses org.junit.runner.notification✕
- Connections
- 1 pair of types, where a type in org.junit.runner uses a type in org.junit.runner.notification.
- The types involved
org.junit.runner.Runner→org.junit.runner.notification.RunNotifier
- Direction
- org.junit.runner uses org.junit.runner.notification, so a change to org.junit.runner.notification can break org.junit.runner, while a change to org.junit.runner can't break org.junit.runner.notification.
- Position
- Below the diagonal: org.junit.runner uses a module listed above it, which is the healthy direction.
28→27 org.junit.runner.manipulation uses org.junit.runner✕
- Connections
- 1 pair of types, where a type in org.junit.runner.manipulation uses a type in org.junit.runner.
- The types involved
org.junit.runner.manipulation.Filter→org.junit.runner.Description
- Direction
- org.junit.runner.manipulation uses org.junit.runner, so a change to org.junit.runner can break org.junit.runner.manipulation, while a change to org.junit.runner.manipulation can't break org.junit.runner.
- Position
- Below the diagonal: org.junit.runner.manipulation uses a module listed above it, which is the healthy direction.
29→9 munit.internal.junitinterface uses munit.internal.junitinterface.RunSettings✕
- Connections
- 1 pair of types, where a type in munit.internal.junitinterface uses a type in munit.internal.junitinterface.RunSettings.
- The types involved
munit.internal.junitinterface.RunSettings→munit.internal.junitinterface.RunSettings.LogMode
- Direction
- munit.internal.junitinterface uses munit.internal.junitinterface.RunSettings, so a change to munit.internal.junitinterface.RunSettings can break munit.internal.junitinterface, while a change to munit.internal.junitinterface can't break munit.internal.junitinterface.RunSettings.
- Position
- Below the diagonal: munit.internal.junitinterface uses a module listed above it, which is the healthy direction.
29→23 munit.internal.junitinterface uses org.junit.runner.notification✕
- Connections
- 6 pairs of types, where a type in munit.internal.junitinterface uses a type in org.junit.runner.notification.
- The types involved
munit.internal.junitinterface.EmptyRunner→org.junit.runner.notification.RunNotifiermunit.internal.junitinterface.ErrorEvent→org.junit.runner.notification.Failuremunit.internal.junitinterface.EventDispatcher→org.junit.runner.notification.Failuremunit.internal.junitinterface.JUnitRunnerWrapper→org.junit.runner.notification.RunNotifiermunit.internal.junitinterface.MUnitRunNotifier→org.junit.runner.notification.Failuremunit.internal.junitinterface.MUnitRunNotifier→org.junit.runner.notification.RunNotifier
- Direction
- munit.internal.junitinterface uses org.junit.runner.notification, so a change to org.junit.runner.notification can break munit.internal.junitinterface, while a change to munit.internal.junitinterface can't break org.junit.runner.notification.
- Position
- Below the diagonal: munit.internal.junitinterface uses a module listed above it, which is the healthy direction.
29→27 munit.internal.junitinterface uses org.junit.runner✕
- Connections
- 15 pairs of types, where a type in munit.internal.junitinterface uses a type in org.junit.runner.
- The types involved
munit.internal.junitinterface.EmptyRunner→org.junit.runner.Descriptionmunit.internal.junitinterface.EmptyRunner→org.junit.runner.Runnermunit.internal.junitinterface.EventDispatcher→org.junit.runner.Descriptionmunit.internal.junitinterface.GlobFilter→org.junit.runner.Descriptionmunit.internal.junitinterface.InfoEvent→org.junit.runner.Descriptionmunit.internal.junitinterface.JUnitComputer→org.junit.runner.Runnermunit.internal.junitinterface.JUnitFramework→org.junit.runner.Runnermunit.internal.junitinterface.JUnitRunner→org.junit.runner.Runnermunit.internal.junitinterface.JUnitRunnerWrapper→org.junit.runner.Descriptionmunit.internal.junitinterface.JUnitRunnerWrapper→org.junit.runner.Runnermunit.internal.junitinterface.MUnitRunNotifier→org.junit.runner.Descriptionmunit.internal.junitinterface.SilentFilterRequest→org.junit.runner.Runnermunit.internal.junitinterface.TagFilter→org.junit.runner.Descriptionmunit.internal.junitinterface.TagsFilter→org.junit.runner.Descriptionmunit.internal.junitinterface.TestFilter→org.junit.runner.Description
- Direction
- munit.internal.junitinterface uses org.junit.runner, so a change to org.junit.runner can break munit.internal.junitinterface, while a change to munit.internal.junitinterface can't break org.junit.runner.
- Position
- Below the diagonal: munit.internal.junitinterface uses a module listed above it, which is the healthy direction.
29→28 munit.internal.junitinterface uses org.junit.runner.manipulation✕
- Connections
- 9 pairs of types, where a type in munit.internal.junitinterface uses a type in org.junit.runner.manipulation.
- The types involved
munit.internal.junitinterface.GlobFilter→org.junit.runner.manipulation.Filtermunit.internal.junitinterface.JUnitRunnerWrapper→org.junit.runner.manipulation.Filtermunit.internal.junitinterface.JUnitRunnerWrapper→org.junit.runner.manipulation.Filterablemunit.internal.junitinterface.MySuite→org.junit.runner.manipulation.Filtermunit.internal.junitinterface.MySuite→org.junit.runner.manipulation.Filterablemunit.internal.junitinterface.SilentFilterRequest→org.junit.runner.manipulation.Filtermunit.internal.junitinterface.TagFilter→org.junit.runner.manipulation.Filtermunit.internal.junitinterface.TagsFilter→org.junit.runner.manipulation.Filtermunit.internal.junitinterface.TestFilter→org.junit.runner.manipulation.Filter
- Direction
- munit.internal.junitinterface uses org.junit.runner.manipulation, so a change to org.junit.runner.manipulation can break munit.internal.junitinterface, while a change to munit.internal.junitinterface can't break org.junit.runner.manipulation.
- Position
- Below the diagonal: munit.internal.junitinterface uses a module listed above it, which is the healthy direction.
30→29 (global) uses munit.internal.junitinterface✕
- Connections
- 1 pair of types, where a type in (global) uses a type in munit.internal.junitinterface.
- The types involved
munit→munit.internal.junitinterface.Tag
- Direction
- (global) uses munit.internal.junitinterface, so a change to munit.internal.junitinterface can break (global), while a change to (global) can't break munit.internal.junitinterface.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
31→1 munit uses java.lang.annotation✕
- Connections
- 3 pairs of types, where a type in munit uses a type in java.lang.annotation.
- The types involved
munit.IgnoreSuite→java.lang.annotation.Annotationmunit.Tag→java.lang.annotation.Annotationmunit.Test→java.lang.annotation.Annotation
- Direction
- munit uses java.lang.annotation, so a change to java.lang.annotation can break munit, while a change to munit can't break java.lang.annotation.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→2 munit uses munit.ValueTransforms✕
- Connections
- 1 pair of types, where a type in munit uses a type in munit.ValueTransforms.
- The types involved
munit.ValueTransforms→munit.ValueTransforms.ValueTransform
- Direction
- munit uses munit.ValueTransforms, so a change to munit.ValueTransforms can break munit, while a change to munit can't break munit.ValueTransforms.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→5 munit uses munit.internal.MacroCompat✕
- Connections
- 1 pair of types, where a type in munit uses a type in munit.internal.MacroCompat.
- The types involved
munit.Location→munit.internal.MacroCompat.LocationMacro
- Direction
- munit uses munit.internal.MacroCompat, so a change to munit.internal.MacroCompat can break munit, while a change to munit can't break munit.internal.MacroCompat.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→11 munit uses org.junit✕
- Connections
- 1 pair of types, where a type in munit uses a type in org.junit.
- The types involved
munit.ComparisonFailException→org.junit.ComparisonFailure
- Direction
- munit uses org.junit, so a change to org.junit can break munit, while a change to munit can't break org.junit.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→15 munit uses munit.MUnitRunner✕
- Connections
- 1 pair of types, where a type in munit uses a type in munit.MUnitRunner.
- The types involved
munit.MUnitRunner→munit.MUnitRunner.BeforeAllResult
- Direction
- munit uses munit.MUnitRunner, so a change to munit.MUnitRunner can break munit, while a change to munit can't break munit.MUnitRunner.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→16 munit uses munit.SuiteTransforms✕
- Connections
- 1 pair of types, where a type in munit uses a type in munit.SuiteTransforms.
- The types involved
munit.SuiteTransforms→munit.SuiteTransforms.SuiteTransform
- Direction
- munit uses munit.SuiteTransforms, so a change to munit.SuiteTransforms can break munit, while a change to munit can't break munit.SuiteTransforms.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→17 munit uses munit.TestTransforms✕
- Connections
- 1 pair of types, where a type in munit uses a type in munit.TestTransforms.
- The types involved
munit.TestTransforms→munit.TestTransforms.TestTransform
- Direction
- munit uses munit.TestTransforms, so a change to munit.TestTransforms can break munit, while a change to munit can't break munit.TestTransforms.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→18 munit uses munit.diff✕
- Connections
- 3 pairs of types, where a type in munit uses a type in munit.diff.
- The types involved
munit.Assertions→munit.diff.Printermunit.Compare→munit.diff.DiffOptionsmunit.Diffs→munit.diff.DiffOptions
- Direction
- munit uses munit.diff, so a change to munit.diff can break munit, while a change to munit can't break munit.diff.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→23 munit uses org.junit.runner.notification✕
- Connections
- 1 pair of types, where a type in munit uses a type in org.junit.runner.notification.
- The types involved
munit.MUnitRunner→org.junit.runner.notification.RunNotifier
- Direction
- munit uses org.junit.runner.notification, so a change to org.junit.runner.notification can break munit, while a change to munit can't break org.junit.runner.notification.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→27 munit uses org.junit.runner✕
- Connections
- 2 pairs of types, where a type in munit uses a type in org.junit.runner.
- The types involved
munit.MUnitRunner→org.junit.runner.Descriptionmunit.MUnitRunner→org.junit.runner.Runner
- Direction
- munit uses org.junit.runner, so a change to org.junit.runner can break munit, while a change to munit can't break org.junit.runner.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→28 munit uses org.junit.runner.manipulation✕
- Connections
- 2 pairs of types, where a type in munit uses a type in org.junit.runner.manipulation.
- The types involved
munit.MUnitRunner→org.junit.runner.manipulation.Filtermunit.MUnitRunner→org.junit.runner.manipulation.Filterable
- Direction
- munit uses org.junit.runner.manipulation, so a change to org.junit.runner.manipulation can break munit, while a change to munit can't break org.junit.runner.manipulation.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
31→29 munit uses munit.internal.junitinterface✕
- Connections
- 7 pairs of types, where a type in munit uses a type in munit.internal.junitinterface.
- The types involved
munit.MUnitRunner→munit.internal.junitinterface.Configurablemunit.MUnitRunner→munit.internal.junitinterface.Settingsmunit.PendingComment→munit.internal.junitinterface.PendingCommentTagmunit.PendingComment→munit.internal.junitinterface.Tagmunit.Tag→munit.internal.junitinterface.Tagmunit.Test→munit.internal.junitinterface.Tagmunit.TestOptions→munit.internal.junitinterface.Tag
- Direction
- munit uses munit.internal.junitinterface, so a change to munit.internal.junitinterface can break munit, while a change to munit can't break munit.internal.junitinterface.
- Position
- Below the diagonal: munit uses a module listed above it, which is the healthy direction.
32→31 docs uses munit✕
- Connections
- 1 pair of types, where a type in docs uses a type in munit.
- The types involved
docs.Docs→munit.FunSuite
- Direction
- docs uses munit, so a change to munit can break docs, while a change to docs can't break munit.
- Position
- Below the diagonal: docs uses a module listed above it, which is the healthy direction.
33→31 munit.FunFixtures uses munit✕
- Connections
- 2 pairs of types, where a type in munit.FunFixtures uses a type in munit.
- The types involved
munit.FunFixtures.FunFixture→munit.Locationmunit.FunFixtures.FunFixture→munit.TestOptions
- Direction
- munit.FunFixtures uses munit, so a change to munit can break munit.FunFixtures, while a change to munit.FunFixtures can't break munit.
- Position
- Below the diagonal: munit.FunFixtures uses a module listed above it, which is the healthy direction.
34→31 munit.TestValues uses munit✕
- Connections
- 1 pair of types, where a type in munit.TestValues uses a type in munit.
- The types involved
munit.TestValues.FlakyFailure→munit.FailException
- Direction
- munit.TestValues uses munit, so a change to munit can break munit.TestValues, while a change to munit.TestValues can't break munit.
- Position
- Below the diagonal: munit.TestValues uses a module listed above it, which is the healthy direction.
35→31 munit.docs uses munit✕
- Connections
- 1 pair of types, where a type in munit.docs uses a type in munit.
- The types involved
munit.docs.Docs→munit.FunSuite
- Direction
- munit.docs uses munit, so a change to munit can break munit.docs, while a change to munit.docs can't break munit.
- Position
- Below the diagonal: munit.docs uses a module listed above it, which is the healthy direction.
36→29 munit.internal uses munit.internal.junitinterface✕
- Connections
- 1 pair of types, where a type in munit.internal uses a type in munit.internal.junitinterface.
- The types involved
munit.internal.MUnitFingerprint→munit.internal.junitinterface.CustomFingerprint
- Direction
- munit.internal uses munit.internal.junitinterface, so a change to munit.internal.junitinterface can break munit.internal, while a change to munit.internal can't break munit.internal.junitinterface.
- Position
- Below the diagonal: munit.internal uses a module listed above it, which is the healthy direction.
36→31 munit.internal uses munit✕
- Connections
- 1 pair of types, where a type in munit.internal uses a type in munit.
- The types involved
munit.internal.PlatformCompat→munit.MUnitRunner
- Direction
- munit.internal uses munit, so a change to munit can break munit.internal, while a change to munit.internal can't break munit.
- Position
- Below the diagonal: munit.internal uses a module listed above it, which is the healthy direction.
37→8 munit.internal.console uses munit.internal.io.PlatformIO✕
- Connections
- 1 pair of types, where a type in munit.internal.console uses a type in munit.internal.io.PlatformIO.
- The types involved
munit.internal.console.Lines→munit.internal.io.PlatformIO.Path
- Direction
- munit.internal.console uses munit.internal.io.PlatformIO, so a change to munit.internal.io.PlatformIO can break munit.internal.console, while a change to munit.internal.console can't break munit.internal.io.PlatformIO.
- Position
- Below the diagonal: munit.internal.console uses a module listed above it, which is the healthy direction.
37→18 munit.internal.console uses munit.diff✕
- Connections
- 1 pair of types, where a type in munit.internal.console uses a type in munit.diff.
- The types involved
munit.internal.console.Printers→munit.diff.Printer
- Direction
- munit.internal.console uses munit.diff, so a change to munit.diff can break munit.internal.console, while a change to munit.internal.console can't break munit.diff.
- Position
- Below the diagonal: munit.internal.console uses a module listed above it, which is the healthy direction.
37→31 munit.internal.console uses munit✕
- Connections
- 3 pairs of types, where a type in munit.internal.console uses a type in munit.
- The types involved
munit.internal.console.Lines→munit.Cluesmunit.internal.console.Lines→munit.Locationmunit.internal.console.Printers→munit.Location
- Direction
- munit.internal.console uses munit, so a change to munit can break munit.internal.console, while a change to munit.internal.console can't break munit.
- Position
- Below the diagonal: munit.internal.console 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 |
|---|---|---|
| A05:2025 — Injection | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; 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; Expand the README with getting-started, architecture overview and a project map.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +9.8 pts | Low | ADR Quality |
| 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.2 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +6.3 pts | Medium | Documentation (README) |
| Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with RichLogger.java, Printers.scala, JUnitTask.java. | +2.7 pts | Low | Knowledge Freshness |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.9 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.9 pts | Low | Bus Factor |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +2.5 pts | Medium | Nullable reference types |
| Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| junit-interface/src/main/java/munit/internal/junitinterface/EventDispatcher.java | 7.0 | Mixed | Cognitive Complexity: EventDispatcher.trimStackTrace (cognitive 18) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| junit-interface/src/main/java/munit/internal/junitinterface/JUnitRunner.java | 7.4 | Mixed | Cyclomatic Complexity: JUnitRunner.<init> (cyclomatic 39) |
| munit/js-native/src/main/scala/munit/internal/junitinterface/JUnitFramework.scala | 7.8 | Mixed | Cyclomatic Complexity: JUnitFramework.parseRunSettings (cyclomatic 28) |
| munit/shared/src/main/scala/munit/internal/console/Printers.scala | 7.8 | Mixed | Cyclomatic Complexity: Printers.print (cyclomatic 27) |
| munit/js-native/src/main/scala/munit/internal/junitinterface/JUnitReporter.scala | 7.8 | Mixed | Cognitive Complexity: JUnitReporter.logStackTracePart (cognitive 23) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| .tool-versions | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: Node.js 16 |
| junit-interface/src/main/java/munit/internal/junitinterface/RichLogger.java | 8.5 | Near-clean | Cognitive Complexity: RichLogger.logStackTracePart (cognitive 23) |
| munit-diff/shared/src/main/scala/munit/diff/MyersDiff.scala | 8.5 | Near-clean | Cognitive Complexity: MyersDiff.buildPath (cognitive 20) |
| munit/jvm/src/main/scala/munit/internal/PlatformCompat.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (19–20 lines × 2) |
| munit/jvm/src/main/scala/munit/internal/io/PlatformIO.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| munit/js/src/main/scala/munit/internal/PlatformCompat.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| munit/shared/src/main/scala/munit/ComparisonFailException.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| junit-interface/src/main/java/munit/internal/junitinterface/CustomRunners.java | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 60 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 60 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, 51 of 64 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- 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, 160 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.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/google/cloud/google-cloud-storage/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D21 Naming 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `munit/shared/src/main/scala-3/munit/internal/MacroCompat.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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").
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was JUnitRunner.<init> at 39.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with JUnitRunner.<init> (cyclomatic 39), JUnitFramework.parseRunSettings (cyclomatic 28), Printers.print (cyclomatic 27). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was JUnitFramework.parseRunSettings at 28.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with JUnitFramework.parseRunSettings (cognitive 28), Printers.print (cognitive 26), JUnitRunner.<init> (cognitive 24). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with JUnitRunner.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
5 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with PlatformCompat.scala, CustomRunners.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (19–20 lines × 2) finding(s) in Code Duplication — start with PlatformCompat.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with PlatformIO.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
5 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; 1 module(s) off the main sequence, with abstractness counted on 4 of the 5 (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 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 13 classes have LCOM4 above 3.
D9 · Test Distribution
86 test methods: 86 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 86 test case(s) across 22 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is junit-interface/src/main/java/munit/internal/junitinterface/EventDispatcher.java. Counted over 29 of the 141 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 6351 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
13 finding(s): 0 critical, 12 high, 1 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `munit/shared/src/main/scala-3/munit/internal/MacroCompat.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
6 of 29 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is junit-interface/src/main/java/munit/internal/junitinterface/RichLogger.java. Counted over 29 of the 141 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 6 Orphaned file finding(s) in Knowledge Freshness — start with RichLogger.java, Printers.scala, JUnitTask.java. — One of this dimension's main actionable groups (6 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
Strongest change-coupling: EventDispatcher.java↔JUnitRunner.java 60%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with EventDispatcher.java. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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
1 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .tool-versions. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `mkdirs`'s body only throws UnsupportedOperationException — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — munit/js/src/main/scala/munit/internal/io/File.scala:26
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×4) — tests/js/src/test/scala/munit/DurationJSSuite.scala:11, tests/shared/src/main/scala/munit/SkippedFrameworkSuite.scala:9, tests/shared/src/main/scala/munit/SkippedFrameworkSuite.scala:10, …
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 46 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 a build/run or getting-started section, no a testing section, 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.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — junit-interface/src/main/java/munit/internal/junitinterface/EventDispatcher.java:96
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — junit-interface/src/main/java/munit/internal/junitinterface/RichLogger.java:149
- `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — junit-interface/src/main/java/munit/internal/junitinterface/RunSettings.java:113
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 107 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 | 64% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 90% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 50% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 79% | Strong | Solid. |
| Security | 63% | 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 — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2888 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
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 5 pinned sbt dependency coordinate(s) were read from its 3 sbt build file(s), but Maven Central could not be asked for the licence of 4 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/google/cloud/google-cloud-storage/2.71.0/google-cloud-storage-2.71.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript, Scala not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Scala surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .scala source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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 (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 21 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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, JavaScript/TypeScript source (2 module(s), 149 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, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Java and Scala code has 7,050 production line(s), 4 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- S1 Web-Security Posture — No web surface: 138 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were 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; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- 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 Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) 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 — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) munit/js/src/main/scala/munit/internal/PlatformCompat.scala:75
- Duplicated block (7 lines × 2) junit-interface/src/main/java/munit/internal/junitinterface/CustomRunners.java:32
- Swallowed exception (caught, then discarded) junit-interface/src/main/java/munit/internal/junitinterface/RichLogger.java:149
- Swallowed exception (caught, then discarded) junit-interface/src/main/java/munit/internal/junitinterface/RunSettings.java:113
- JUnitRunner.<init> (cyclomatic 39) junit-interface/src/main/java/munit/internal/junitinterface/JUnitRunner.java:30
- JUnitFramework.parseRunSettings (cyclomatic 28) munit/js-native/src/main/scala/munit/internal/junitinterface/JUnitFramework.scala:42
- Printers.print (cyclomatic 27) munit/shared/src/main/scala/munit/internal/console/Printers.scala:21
- JUnitFramework.parseRunSettings (cognitive 28) munit/js-native/src/main/scala/munit/internal/junitinterface/JUnitFramework.scala:42
- Printers.print (cognitive 26) munit/shared/src/main/scala/munit/internal/console/Printers.scala:21
- JUnitRunner.<init> (cognitive 24) junit-interface/src/main/java/munit/internal/junitinterface/JUnitRunner.java:30
- JUnitReporter.logStackTracePart (cognitive 23) munit/js-native/src/main/scala/munit/internal/junitinterface/JUnitReporter.scala:211
- RichLogger.logStackTracePart (cognitive 23) junit-interface/src/main/java/munit/internal/junitinterface/RichLogger.java:84
- MyersDiff.buildPath (cognitive 20) munit-diff/shared/src/main/scala/munit/diff/MyersDiff.scala:53
- EventDispatcher.trimStackTrace (cognitive 18) junit-interface/src/main/java/munit/internal/junitinterface/EventDispatcher.java:274
- JUnitReporter.stackTraceElementToString (cognitive 17) munit/js-native/src/main/scala/munit/internal/junitinterface/JUnitReporter.scala:275
- REDACTED
- MethodTooLong: JUnitRunner.<init> junit-interface/src/main/java/munit/internal/junitinterface/JUnitRunner.java:30
- Change coupling: EventDispatcher.java ↔ JUnitRunner.java junit-interface/src/main/java/munit/internal/junitinterface/EventDispatcher.java:1
- REDACTED
- Duplicated block (19–20 lines × 2) munit/jvm/src/main/scala/munit/internal/PlatformCompat.scala:48
- Duplicated block (15 lines × 2) munit/jvm/src/main/scala/munit/internal/io/PlatformIO.scala:6
- Duplicated block (6 lines × 2) munit/shared/src/main/scala/munit/ComparisonFailException.scala:57
- End-of-life runtime: Node.js 16 .tool-versions:1
- Off the main sequence: munitDiff
- Swallowed exception (empty catch) junit-interface/src/main/java/munit/internal/junitinterface/EventDispatcher.java:96
Minor — 23 finding(s)
- Orphaned file junit-interface/src/main/java/munit/internal/junitinterface/RichLogger.java:1
- Orphaned file munit/shared/src/main/scala/munit/internal/console/Printers.scala:1
- Orphaned file junit-interface/src/main/java/munit/internal/junitinterface/JUnitTask.java:1
- Orphaned file munit-sbt/src/main/scala/munit/sbtmunit/MUnitPlugin.scala:1
- Orphaned file munit-diff/shared/src/main/scala/munit/diff/Printer.scala:1
- Orphaned file junit-interface/src/main/java/munit/internal/junitinterface/JUnitComputer.java:1
- Disabled test tests/js/src/test/scala/munit/DurationJSSuite.scala:11
- Disabled test tests/shared/src/main/scala/munit/SkippedFrameworkSuite.scala:9
- Disabled test tests/shared/src/main/scala/munit/SkippedFrameworkSuite.scala:10
- Disabled test tests/shared/src/main/scala/munit/SkippedFrameworkSuite.scala:11
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- Method throws UnsupportedOperationException munit/js/src/main/scala/munit/internal/io/File.scala:26
- Thin README readme.md:1
- No ADRs
- No architecture diagram/doc
- No release approval gate
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fff830030e334af8802bace243eb652c/history.json --exit-code 0 --source . | 2 | 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-fff830030e334af8802bace243eb652c/tree.json --exit-code 0 --source . | 1 | 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 . | 13 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `munit/shared/src/main/scala-3/munit/internal/MacroCompat.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |