Executive summary
com-lihaoyi/utest falls short of our standard for a preview release because 18 files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 58 out of 100 and is rated Adequate, and all five 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 having someone learn and document the 18 files no active contributor knows, worth about 7 points. Recording design decisions comes next, worth about 6 points. Raising Maturity to 62 would lift the score to about 63.
Four 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. Pinning each tool to an exact version and setting a waiting period for automatic updates would close both risks.
The product code is 3,672 lines, about €6,800 to rebuild.
If Maturity rose from 50 to 62, the lowest score rated Strong, the score would rise from 58 to about 63.
Rebuild cost: about €6,800 · Estimate
| Cost to rebuild | €2,300 to €11,000, for 38 to 120 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 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,672 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: which parts of the code depend on which
| uses → | 1 utest.AssertionError | 2 utest.asserts.Asserts | 3 utest.asserts.MacroCompat | 4 utest.framework.GoldenSpanMacros | 5 utest.framework.PortableScalaReflectExcerpts | 6 utest.shaded.stringdiff.MyersDiff | 7 utest.shaded.stringdiff.util.DiffTokenize | 8 utest.test | 9 utest.framework | 10 utest.shaded.stringdiff | 11 utest.shaded.stringdiff.MyersDiff.Operation | 12 utest | 13 utest.TestBuilder | 14 utest.framework.ExecutionContext | 15 utest.framework.GoldenFix | 16 utest.framework.HTree | 17 utest.shaded.stringdiff.DiffElement | 18 utest.shaded.stringdiff.format | 19 utest.shaded.stringdiff.util | 20 utest.CompileError | 21 utest.TestSuite | 22 utest.TestValue | 23 utest.TestsVersionSpecific | 24 utest.runner | 25 utest.asserts | 26 (global) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 utest.AssertionError | ||||||||||||||||||||||||||
| 2 utest.asserts.Asserts | ||||||||||||||||||||||||||
| 3 utest.asserts.MacroCompat | ||||||||||||||||||||||||||
| 4 utest.framework.GoldenSpanMacros | ||||||||||||||||||||||||||
| 5 utest.framework.PortableScalaReflectExcerpts | ||||||||||||||||||||||||||
| 6 utest.shaded.stringdiff.MyersDiff | ||||||||||||||||||||||||||
| 7 utest.shaded.stringdiff.util.DiffTokenize | ||||||||||||||||||||||||||
| 8 utest.test | ||||||||||||||||||||||||||
| 9 utest.framework | 2 | |||||||||||||||||||||||||
| 10 utest.shaded.stringdiff | 2 | |||||||||||||||||||||||||
| 11 utest.shaded.stringdiff.MyersDiff.Operation | 4 | |||||||||||||||||||||||||
| 12 utest | 2 | 1 | 13 | |||||||||||||||||||||||
| 13 utest.TestBuilder | 1 | 4 | ||||||||||||||||||||||||
| 14 utest.framework.ExecutionContext | 1 | |||||||||||||||||||||||||
| 15 utest.framework.GoldenFix | 1 | |||||||||||||||||||||||||
| 16 utest.framework.HTree | 2 | |||||||||||||||||||||||||
| 17 utest.shaded.stringdiff.DiffElement | 4 | |||||||||||||||||||||||||
| 18 utest.shaded.stringdiff.format | 4 | |||||||||||||||||||||||||
| 19 utest.shaded.stringdiff.util | 3 | |||||||||||||||||||||||||
| 20 utest.CompileError | 3 | |||||||||||||||||||||||||
| 21 utest.TestSuite | 1 | 1 | ||||||||||||||||||||||||
| 22 utest.TestValue | 2 | |||||||||||||||||||||||||
| 23 utest.TestsVersionSpecific | 1 | |||||||||||||||||||||||||
| 24 utest.runner | 1 | 1 | ||||||||||||||||||||||||
| 25 utest.asserts | 1 | 2 | 1 | |||||||||||||||||||||||
| 26 (global) | 3 |
9→5 utest.framework uses utest.framework.PortableScalaReflectExcerpts✕
- Connections
- 2 pairs of types, where a type in utest.framework uses a type in utest.framework.PortableScalaReflectExcerpts.
- The types involved
utest.framework.PortableScalaReflectExcerpts→utest.framework.PortableScalaReflectExcerpts.InstantiatableClassutest.framework.PortableScalaReflectExcerpts→utest.framework.PortableScalaReflectExcerpts.LoadableModuleClass
- Direction
- utest.framework uses utest.framework.PortableScalaReflectExcerpts, so a change to utest.framework.PortableScalaReflectExcerpts can break utest.framework, while a change to utest.framework can't break utest.framework.PortableScalaReflectExcerpts.
- Position
- Below the diagonal: utest.framework uses a module listed above it, which is the healthy direction.
10→6 utest.shaded.stringdiff uses utest.shaded.stringdiff.MyersDiff✕
- Connections
- 2 pairs of types, where a type in utest.shaded.stringdiff uses a type in utest.shaded.stringdiff.MyersDiff.
- The types involved
utest.shaded.stringdiff.MyersDiff→utest.shaded.stringdiff.MyersDiff.Operationutest.shaded.stringdiff.MyersInterpret→utest.shaded.stringdiff.MyersDiff.Operation
- Direction
- utest.shaded.stringdiff uses utest.shaded.stringdiff.MyersDiff, so a change to utest.shaded.stringdiff.MyersDiff can break utest.shaded.stringdiff, while a change to utest.shaded.stringdiff can't break utest.shaded.stringdiff.MyersDiff.
- Position
- Below the diagonal: utest.shaded.stringdiff uses a module listed above it, which is the healthy direction.
11→6 utest.shaded.stringdiff.MyersDiff.Operation uses utest.shaded.stringdiff.MyersDiff✕
- Connections
- 4 pairs of types, where a type in utest.shaded.stringdiff.MyersDiff.Operation uses a type in utest.shaded.stringdiff.MyersDiff.
- The types involved
utest.shaded.stringdiff.MyersDiff.Operation.Delete→utest.shaded.stringdiff.MyersDiff.Operationutest.shaded.stringdiff.MyersDiff.Operation.End→utest.shaded.stringdiff.MyersDiff.Operationutest.shaded.stringdiff.MyersDiff.Operation.Insert→utest.shaded.stringdiff.MyersDiff.Operationutest.shaded.stringdiff.MyersDiff.Operation.Start→utest.shaded.stringdiff.MyersDiff.Operation
- Direction
- utest.shaded.stringdiff.MyersDiff.Operation uses utest.shaded.stringdiff.MyersDiff, so a change to utest.shaded.stringdiff.MyersDiff can break utest.shaded.stringdiff.MyersDiff.Operation, while a change to utest.shaded.stringdiff.MyersDiff.Operation can't break utest.shaded.stringdiff.MyersDiff.
- Position
- Below the diagonal: utest.shaded.stringdiff.MyersDiff.Operation uses a module listed above it, which is the healthy direction.
12→1 utest uses utest.AssertionError✕
- Connections
- 2 pairs of types, where a type in utest uses a type in utest.AssertionError.
- The types involved
utest.AssertionError→utest.AssertionError.Printerutest.ColorMessageError→utest.AssertionError.Printer
- Direction
- utest uses utest.AssertionError, so a change to utest.AssertionError can break utest, while a change to utest can't break utest.AssertionError.
- Position
- Below the diagonal: utest uses a module listed above it, which is the healthy direction.
12→8 utest uses utest.test✕
- Connections
- 1 pair of types, where a type in utest uses a type in utest.test.
- The types involved
utest.TestBuilder→utest.test.Apply
- Direction
- utest uses utest.test, so a change to utest.test can break utest, while a change to utest can't break utest.test.
- Position
- Below the diagonal: utest uses a module listed above it, which is the healthy direction.
12→9 utest uses utest.framework✕
- Connections
- 13 pairs of types, where a type in utest uses a type in utest.framework.
- The types involved
utest.TestBuilder→utest.framework.TestCallTreeutest.TestQueryParser→utest.framework.Treeutest.TestRunner→utest.framework.ExecutionContextutest.TestRunner→utest.framework.Executorutest.TestRunner→utest.framework.Formatterutest.TestRunner→utest.framework.HTreeutest.TestRunner→utest.framework.Resultutest.TestRunner→utest.framework.Treeutest.TestSuite→utest.framework.Executorutest.TestSuite→utest.framework.Formatterutest.TestSuite→utest.framework.TestSuitePlatformSpecificutest.Tests→utest.framework.TestCallTreeutest.Tests→utest.framework.Tree
- Direction
- utest uses utest.framework, so a change to utest.framework can break utest, while a change to utest can't break utest.framework.
- Position
- Below the diagonal: utest uses a module listed above it, which is the healthy direction.
13→8 utest.TestBuilder uses utest.test✕
- Connections
- 1 pair of types, where a type in utest.TestBuilder uses a type in utest.test.
- The types involved
utest.TestBuilder.IsTest→utest.test.Apply
- Direction
- utest.TestBuilder uses utest.test, so a change to utest.test can break utest.TestBuilder, while a change to utest.TestBuilder can't break utest.test.
- Position
- Below the diagonal: utest.TestBuilder uses a module listed above it, which is the healthy direction.
13→9 utest.TestBuilder uses utest.framework✕
- Connections
- 4 pairs of types, where a type in utest.TestBuilder uses a type in utest.framework.
- The types involved
utest.TestBuilder.IsTest→utest.framework.Treeutest.TestBuilder.Stats→utest.framework.Treeutest.TestBuilder.Test→utest.framework.Treeutest.TestBuilder.TestMethod→utest.framework.Tree
- Direction
- utest.TestBuilder uses utest.framework, so a change to utest.framework can break utest.TestBuilder, while a change to utest.TestBuilder can't break utest.framework.
- Position
- Below the diagonal: utest.TestBuilder uses a module listed above it, which is the healthy direction.
14→9 utest.framework.ExecutionContext uses utest.framework✕
- Connections
- 1 pair of types, where a type in utest.framework.ExecutionContext uses a type in utest.framework.
- The types involved
utest.framework.ExecutionContext.RunNow→utest.framework.ExecutionContext
- Direction
- utest.framework.ExecutionContext uses utest.framework, so a change to utest.framework can break utest.framework.ExecutionContext, while a change to utest.framework.ExecutionContext can't break utest.framework.
- Position
- Below the diagonal: utest.framework.ExecutionContext uses a module listed above it, which is the healthy direction.
15→9 utest.framework.GoldenFix uses utest.framework✕
- Connections
- 1 pair of types, where a type in utest.framework.GoldenFix uses a type in utest.framework.
- The types involved
utest.framework.GoldenFix.Reporter→utest.framework.GoldenFix
- Direction
- utest.framework.GoldenFix uses utest.framework, so a change to utest.framework can break utest.framework.GoldenFix, while a change to utest.framework.GoldenFix can't break utest.framework.
- Position
- Below the diagonal: utest.framework.GoldenFix uses a module listed above it, which is the healthy direction.
16→9 utest.framework.HTree uses utest.framework✕
- Connections
- 2 pairs of types, where a type in utest.framework.HTree uses a type in utest.framework.
- The types involved
utest.framework.HTree.Leaf→utest.framework.HTreeutest.framework.HTree.Node→utest.framework.HTree
- Direction
- utest.framework.HTree uses utest.framework, so a change to utest.framework can break utest.framework.HTree, while a change to utest.framework.HTree can't break utest.framework.
- Position
- Below the diagonal: utest.framework.HTree uses a module listed above it, which is the healthy direction.
17→10 utest.shaded.stringdiff.DiffElement uses utest.shaded.stringdiff✕
- Connections
- 4 pairs of types, where a type in utest.shaded.stringdiff.DiffElement uses a type in utest.shaded.stringdiff.
- The types involved
utest.shaded.stringdiff.DiffElement.Diff→utest.shaded.stringdiff.DiffElementutest.shaded.stringdiff.DiffElement.InBoth→utest.shaded.stringdiff.DiffElementutest.shaded.stringdiff.DiffElement.InFirst→utest.shaded.stringdiff.DiffElementutest.shaded.stringdiff.DiffElement.InSecond→utest.shaded.stringdiff.DiffElement
- Direction
- utest.shaded.stringdiff.DiffElement uses utest.shaded.stringdiff, so a change to utest.shaded.stringdiff can break utest.shaded.stringdiff.DiffElement, while a change to utest.shaded.stringdiff.DiffElement can't break utest.shaded.stringdiff.
- Position
- Below the diagonal: utest.shaded.stringdiff.DiffElement uses a module listed above it, which is the healthy direction.
18→10 utest.shaded.stringdiff.format uses utest.shaded.stringdiff✕
- Connections
- 4 pairs of types, where a type in utest.shaded.stringdiff.format uses a type in utest.shaded.stringdiff.
- The types involved
utest.shaded.stringdiff.format.AnsiDiffFormat→utest.shaded.stringdiff.DiffElementutest.shaded.stringdiff.format.AnsiDiffFormatBoth→utest.shaded.stringdiff.DiffElementutest.shaded.stringdiff.format.DiffFormat→utest.shaded.stringdiff.DiffElementutest.shaded.stringdiff.format.TextDiffFormat→utest.shaded.stringdiff.DiffElement
- Direction
- utest.shaded.stringdiff.format uses utest.shaded.stringdiff, so a change to utest.shaded.stringdiff can break utest.shaded.stringdiff.format, while a change to utest.shaded.stringdiff.format can't break utest.shaded.stringdiff.
- Position
- Below the diagonal: utest.shaded.stringdiff.format uses a module listed above it, which is the healthy direction.
19→10 utest.shaded.stringdiff.util uses utest.shaded.stringdiff✕
- Connections
- 3 pairs of types, where a type in utest.shaded.stringdiff.util uses a type in utest.shaded.stringdiff.
- The types involved
utest.shaded.stringdiff.util.DiffCollapse→utest.shaded.stringdiff.DiffElementutest.shaded.stringdiff.util.DiffPrettier→utest.shaded.stringdiff.DiffElementutest.shaded.stringdiff.util.DiffTokenize→utest.shaded.stringdiff.DiffElement
- Direction
- utest.shaded.stringdiff.util uses utest.shaded.stringdiff, so a change to utest.shaded.stringdiff can break utest.shaded.stringdiff.util, while a change to utest.shaded.stringdiff.util can't break utest.shaded.stringdiff.
- Position
- Below the diagonal: utest.shaded.stringdiff.util uses a module listed above it, which is the healthy direction.
20→12 utest.CompileError uses utest✕
- Connections
- 3 pairs of types, where a type in utest.CompileError uses a type in utest.
- The types involved
utest.CompileError.CompileTimeOnly→utest.CompileErrorutest.CompileError.Parse→utest.CompileErrorutest.CompileError.Type→utest.CompileError
- Direction
- utest.CompileError uses utest, so a change to utest can break utest.CompileError, while a change to utest.CompileError can't break utest.
- Position
- Below the diagonal: utest.CompileError uses a module listed above it, which is the healthy direction.
21→9 utest.TestSuite uses utest.framework✕
- Connections
- 1 pair of types, where a type in utest.TestSuite uses a type in utest.framework.
- The types involved
utest.TestSuite.Retries→utest.framework.ExecutionContext
- Direction
- utest.TestSuite uses utest.framework, so a change to utest.framework can break utest.TestSuite, while a change to utest.TestSuite can't break utest.framework.
- Position
- Below the diagonal: utest.TestSuite uses a module listed above it, which is the healthy direction.
21→12 utest.TestSuite uses utest✕
- Connections
- 1 pair of types, where a type in utest.TestSuite uses a type in utest.
- The types involved
utest.TestSuite.Retries→utest.TestSuite
- Direction
- utest.TestSuite uses utest, so a change to utest can break utest.TestSuite, while a change to utest.TestSuite can't break utest.
- Position
- Below the diagonal: utest.TestSuite uses a module listed above it, which is the healthy direction.
22→12 utest.TestValue uses utest✕
- Connections
- 2 pairs of types, where a type in utest.TestValue uses a type in utest.
- The types involved
utest.TestValue.Equality→utest.TestValueutest.TestValue.Single→utest.TestValue
- Direction
- utest.TestValue uses utest, so a change to utest can break utest.TestValue, while a change to utest.TestValue can't break utest.
- Position
- Below the diagonal: utest.TestValue uses a module listed above it, which is the healthy direction.
23→12 utest.TestsVersionSpecific uses utest✕
- Connections
- 1 pair of types, where a type in utest.TestsVersionSpecific uses a type in utest.
- The types involved
utest.TestsVersionSpecific.Builder→utest.Tests
- Direction
- utest.TestsVersionSpecific uses utest, so a change to utest can break utest.TestsVersionSpecific, while a change to utest.TestsVersionSpecific can't break utest.
- Position
- Below the diagonal: utest.TestsVersionSpecific uses a module listed above it, which is the healthy direction.
24→9 utest.runner uses utest.framework✕
- Connections
- 1 pair of types, where a type in utest.runner uses a type in utest.framework.
- The types involved
utest.runner.BaseRunner→utest.framework.Tree
- Direction
- utest.runner uses utest.framework, so a change to utest.framework can break utest.runner, while a change to utest.runner can't break utest.framework.
- Position
- Below the diagonal: utest.runner uses a module listed above it, which is the healthy direction.
24→12 utest.runner uses utest✕
- Connections
- 1 pair of types, where a type in utest.runner uses a type in utest.
- The types involved
utest.runner.MasterRunner→utest.TestSuite
- Direction
- utest.runner uses utest, so a change to utest can break utest.runner, while a change to utest.runner can't break utest.
- Position
- Below the diagonal: utest.runner uses a module listed above it, which is the healthy direction.
25→9 utest.asserts uses utest.framework✕
- Connections
- 1 pair of types, where a type in utest.asserts uses a type in utest.framework.
- The types involved
utest.asserts.Tracer→utest.framework.Tree
- Direction
- utest.asserts uses utest.framework, so a change to utest.framework can break utest.asserts, while a change to utest.asserts can't break utest.framework.
- Position
- Below the diagonal: utest.asserts uses a module listed above it, which is the healthy direction.
25→12 utest.asserts uses utest✕
- Connections
- 2 pairs of types, where a type in utest.asserts uses a type in utest.
- The types involved
utest.asserts.AssertsCompanionVersionSpecific→utest.CompileErrorutest.asserts.Util→utest.TestValue
- Direction
- utest.asserts uses utest, so a change to utest can break utest.asserts, while a change to utest.asserts can't break utest.
- Position
- Below the diagonal: utest.asserts uses a module listed above it, which is the healthy direction.
25→20 utest.asserts uses utest.CompileError✕
- Connections
- 1 pair of types, where a type in utest.asserts uses a type in utest.CompileError.
- The types involved
utest.asserts.Tracer→utest.CompileError.Type
- Direction
- utest.asserts uses utest.CompileError, so a change to utest.CompileError can break utest.asserts, while a change to utest.asserts can't break utest.CompileError.
- Position
- Below the diagonal: utest.asserts uses a module listed above it, which is the healthy direction.
26→25 (global) uses utest.asserts✕
- Connections
- 3 pairs of types, where a type in (global) uses a type in utest.asserts.
- The types involved
utest→utest.asserts.Assertsutest→utest.asserts.RetryIntervalutest→utest.asserts.RetryMax
- Direction
- (global) uses utest.asserts, so a change to utest.asserts can break (global), while a change to (global) can't break utest.asserts.
- Position
- Below the diagonal: (global) 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 | 7 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: Resolve the 18 Orphaned file finding(s) in Knowledge Freshness — start with Tracer.scala (2), TestRunner.scala, DiffTokenize.scala; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 1 Off-boarding risk finding(s) in Bus Factor.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 18 Orphaned file finding(s) in Knowledge Freshness — start with Tracer.scala (2), TestRunner.scala, DiffTokenize.scala. | +6.6 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.3 pts | Medium | Architecture documentation |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +2.7 pts | Low | Bus Factor |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.7 pts | Medium | Security & performance tooling |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +1.9 pts | Medium | Documentation (README) |
| 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. | +1.7 pts | Medium | Nullable reference types |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.7 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.7 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| utest/src-jvm/utest/asserts/AssertsPlatformSpecific.scala | 7.4 | Near-clean | Cyclomatic Complexity: AssertsPlatformSpecific.assertGoldenFolder (cyclomatic 16) |
| utest/src/utest/shaded/stringdiff/MyersDiff.scala | 7.8 | Near-clean | Cyclomatic Complexity: MyersDiff.diff (cyclomatic 23) |
| utest/src/utest/shaded/stringdiff/MyersInterpret.scala | 7.8 | Near-clean | Cyclomatic Complexity: MyersInterpret.apply (cyclomatic 21) |
| utest/src-3/utest/Tests.scala | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| utest/src/utest/asserts/Asserts.scala | 8.2 | Near-clean | Explicit Debt: HackComment |
| utest/src/utest/framework/Formatter.scala | 8.5 | Near-clean | Cognitive Complexity: Formatter.formatException (cognitive 21) |
| utest/src-2/utest/asserts/AssertsVersionSpecific.scala | 8.5 | Near-clean | Cognitive Complexity: AssertsCompanionVersionSpecific.assertCompileError (cognitive 20) |
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 54 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 — 54 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, 41 of 52 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) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — no dependency manifest this pass reads for licence data (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so it declares no third-party dependency closure to grade. A gap in the analyzer, NOT a finding that this repository's licences are compliant: a manifest in an ecosystem outside that list, or third-party code copied into the tree, is not read — so this dimension asserts nothing about this repository's licensing in either direction.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.mill), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
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.
- 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.
- 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").
- 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.
- 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 MyersDiff.diff at 23. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DiffCollapse.apply at 19 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: utest/src/utest/shaded/stringdiff/util/DiffCollapse.scala (DiffCollapse.apply at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MyersDiff.diff (cyclomatic 23), MyersInterpret.apply (cyclomatic 21), AssertsPlatformSpecific.assertGoldenFolder (cyclomatic 16). — 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 9.3 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
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was MyersDiff.diff at 62.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with MyersDiff.diff (cognitive 62), AssertsPlatformSpecific.assertGoldenFolder (cognitive 32). — 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 2 together lifts Cognitive Complexity from 8.1 to about 8.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- 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
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AssertsPlatformSpecific.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.
D6 · Cohesion (LCOM4)
0 of 2 classes have LCOM4 above 3.
D9 · Test Distribution
179 test methods: 179 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 179 test case(s) across 29 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
Top hotspots: utest/src/utest/Errors.scala (3×15=45)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with Errors.scala. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is utest/src-jvm/utest/asserts/AssertsPlatformSpecific.scala. Counted over 17 of the 66 production source files in this repository: 48 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
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).
D17 · Explicit Debt
2 deducted task-comment markers across 3672 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with Tests.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with Asserts.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
0 of 1 build units (checkout) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 5 high, 2 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
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 warning-level).
- No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
18 of 18 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is utest/src/utest/TestRunner.scala. Counted over 18 of the 66 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 18 Orphaned file finding(s) in Knowledge Freshness — start with Tracer.scala (2), TestRunner.scala, DiffTokenize.scala. — One of this dimension's main actionable groups (18 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
- Production code isn't grouped under a src/ folder — it all sits under utest/, so the conventional src/ boundary between the product and its tooling isn't drawn.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) — even for a small library, every public type is a stability contract.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1938 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- 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
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
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
- `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — utest/src/utest/runner/BaseRunner.scala:84
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 56 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 | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 50% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — ~2867 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 — no .scala test runner
- D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
- D14 License Compliance — No dependency manifest found — no declared dependency closure to grade for licences
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- 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) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — no manifest declares this repository's modules, and its source holds 1 production component(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production components are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 27 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (1 module(s), 66 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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 3,643 production line(s), 0 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: 57 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- 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 — 5 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 17 finding(s)
- MyersDiff.diff (cyclomatic 23) utest/src/utest/shaded/stringdiff/MyersDiff.scala:5
- MyersInterpret.apply (cyclomatic 21) utest/src/utest/shaded/stringdiff/MyersInterpret.scala:12
- AssertsPlatformSpecific.assertGoldenFolder (cyclomatic 16) utest/src-jvm/utest/asserts/AssertsPlatformSpecific.scala:73
- Hotspot: utest/src/utest/Errors.scala utest/src/utest/Errors.scala:42
- FixmeComment utest/src-3/utest/Tests.scala:9
- HackComment utest/src/utest/asserts/Asserts.scala:85
- MyersDiff.diff (cognitive 62) utest/src/utest/shaded/stringdiff/MyersDiff.scala:5
- AssertsPlatformSpecific.assertGoldenFolder (cognitive 32) utest/src-jvm/utest/asserts/AssertsPlatformSpecific.scala:73
- MyersInterpret.apply (cognitive 28) utest/src/utest/shaded/stringdiff/MyersInterpret.scala:12
- Formatter.formatException (cognitive 21) utest/src/utest/framework/Formatter.scala:55
- AssertsCompanionVersionSpecific.assertCompileError (cognitive 20) utest/src-2/utest/asserts/AssertsVersionSpecific.scala:20
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) utest/src-jvm/utest/asserts/AssertsPlatformSpecific.scala:176
- Swallowed exception (caught, then discarded) utest/src/utest/runner/BaseRunner.scala:84
Minor — 30 finding(s)
- Orphaned file utest/src/utest/TestRunner.scala:1
- Orphaned file utest/src/utest/shaded/stringdiff/util/DiffTokenize.scala:1
- Orphaned file utest/src-jvm/utest/asserts/AssertsPlatformSpecific.scala:1
- Orphaned file utest/src/utest/framework/Formatter.scala:1
- Orphaned file utest/src/utest/Errors.scala:1
- Orphaned file utest/src/utest/runner/BaseRunner.scala:1
- Orphaned file utest/src-3/utest/TestBuilder.scala:1
- Orphaned file utest/src-3/utest/asserts/Tracer.scala:1
- Orphaned file utest/src/utest/TestQueryParser.scala:1
- Orphaned file utest/src-3-jvm/utest/framework/PortableScalaReflectExcerpts.scala:1
- Orphaned file utest/src-jvm/utest/framework/GoldenFix.scala:1
- Orphaned file utest/src-2/utest/asserts/Tracer.scala:1
- Orphaned file utest/src/utest/runner/MasterRunner.scala:1
- Orphaned file utest/src-3/utest/asserts/AssertsVersionSpecific.scala:1
- Orphaned file utest/src/utest/shaded/stringdiff/MyersInterpret.scala:1
- Orphaned file utest/src/utest/asserts/Asserts.scala:1
- Orphaned file utest/src/utest/shaded/stringdiff/MyersDiff.scala:1
- Orphaned file utest/src/utest/runner/Framework.scala:1
- Off-boarding risk: anonymized user #1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No SAST REDACTED:9
- No release approval gate
- No changelog
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch utest/src/utest/runner/BaseRunner.scala:84
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-d110da4c2a2e42eb98c44d5d19de754f/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d110da4c2a2e42eb98c44d5d19de754f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |
| 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. | 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 | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |