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

VirtusLab/scala-cli

Measured 14 November 2026, 14:58 UTC, at code version 8c90e2f

CAI score 62out of 100 Adequate
CriticalWeakAdequateStrongExemplary
No change since the last survey

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

A medium codebase: 52,369 lines of product code in 18 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Maturity, 55

Findings by how serious they are

408 critical 335 serious 70 minor

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

This survey was produced by

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

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

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

54of 54 dimensions measured by tools.
800of 813 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
54dimensions across 6 lenses, read from 52,369 lines of product code in 18 projects.
Chapters

Executive summary

VirtusLab/scala-cli falls short of our standard for production, in part because the project keeps no record of its design decisions. It scores 62 out of 100 and is rated Adequate, and 406 of its 408 critical findings are security problems.

Maturity, at 55, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Having someone learn and document the file no active contributor knows comes next, worth about 3 points. Raising Maturity to 70 would lift the score to about 67.

379 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen secrets can leak from the build pipeline, and seven settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Fixing the weaknesses the scanner points to would fix the three security weaknesses in the code, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The set of files in separate parts that keep changing together needs that dependency made explicit.

The product code is 52,369 lines, about €110,000 to rebuild.

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

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

If Maturity rose from 55 to 70, the lowest score rated Strong, the score would rise from 62 to about 67.

Code composition: what the lines of code are
Product code 54%Tests 46%
New since the last survey: 111 findings

These 111 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

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

Fixed since the last survey: 12 findings

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

  • Code Duplication · Duplicated block (23–27 lines × 2) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala
  • Code Duplication · Duplicated block (24 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala
  • Code Duplication · Duplicated block (7 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala
  • Churn × Complexity Hotspots · Hotspot: modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala
  • Churn × Complexity Hotspots · Hotspot: modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala
  • Churn × Complexity Hotspots · Hotspot: modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala
  • Churn × Complexity Hotspots · Hotspot: modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala
  • Explicit Debt · TodoComment modules/integration/src/test/scala/scala/cli/integration/GitHubTests.scala
  • Explicit Debt · TodoComment modules/integration/src/test/scala/scala/cli/integration/GitHubTests.scala
  • Explicit Debt · TodoComment modules/integration/src/test/scala/scala/cli/integration/GitHubTests.scala
  • Explicit Debt · FixmeComment modules/cli/src/main/scala/scala/cli/commands/github/LibSodiumJni.scala
  • Explicit Debt · FixmeComment modules/cli/src/main/scala/scala/cli/commands/github/LibSodiumJni.scala
Rebuild cost: about €110,000 · Estimate
Cost to rebuild€35,000 to €180,000, for 591 to 1,876 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 52,369 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.mill.
Raises the score by about 6 points · Low effort · ADR Quality
2
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Licenses.scala.
Raises the score by about 3 points · Low effort · Knowledge Freshness
3
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.
Raises the score by about 5 points · Medium effort · Architecture documentation

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Maturity, at 55 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch build-macros build-macros build-module build-module directives directives build-module->directives options options build-module->options scala-cli-bsp scala-cli-bsp build-module->scala-cli-bsp tasty-lib tasty-lib build-module->tasty-lib test-runner test-runner build-module->test-runner cli cli cli->build-module config config cli->config specification-level specification-level cli->specification-level config->specification-level core core core->build-macros core->config directives->build-macros directives->core directives->options directives->specification-level docs-tests docs-tests dummy.scalafmt scalafmt generate-reference-doc generate-reference-doc generate-reference-doc->cli integration integration integration.docker docker java-test-runner java-test-runner options->build-macros options->core runner runner

Architecture: which parts of the code depend on which

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

184 modules, with 368 dependencies between them. One loop runs through 23 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 build.options.publish2 build.errors.Diagnostic3 build.internal4 build.internals5 cli.launcher6 build.options7 build.compiler8 build.input9 build.preprocessing10 cli.commands.shared11 cli.commands.util12 cli.commands.repl13 cli.commands.run14 cli.commands.default15 cli.commands16 build.directives17 cli.config18 build.preprocessing.directives19 build.errors20 build.internal.util21 build22 build.actionable.ActionableDiagnostic23 build.bsp24 build.preprocessing.directives.PublishContextual25 cli.commands.bsp26 cli.commands.compile27 cli.commands.doc28 cli.commands.fix29 cli.commands.fmt30 cli.commands.github31 cli.commands.package032 cli.commands.pgp33 cli.commands.setupide34 cli.commands.shebang35 cli.commands.uninstall36 cli.exportCmd37 cli.commands.config38 cli.commands.export039 cli.commands.publish40 cli.internal
1 build.options.publish
2 build.errors.Diagnostic21
3 build.internal85
4 build.internals1
5 cli.launcher1
6 build.options51711
7 build.compiler3314
8 build.input111
9 build.preprocessing3141571110
10 cli.commands.shared231337
11 cli.commands.util1232
12 cli.commands.repl161124
13 cli.commands.run111101211
14 cli.commands.default151123
15 cli.commands2133114
16 build.directives4114
17 cli.config1
18 build.preprocessing.directives5151364128
19 build.errors116
20 build.internal.util11112
21 build121728
22 build.actionable.ActionableDiagnostic121
23 build.bsp51729
24 build.preprocessing.directives.PublishContextual22222
25 cli.commands.bsp11311
26 cli.commands.compile17121
27 cli.commands.doc141212
28 cli.commands.fix3141421324
29 cli.commands.fmt14112
30 cli.commands.github54213
31 cli.commands.package0141101123
32 cli.commands.pgp1162337
33 cli.commands.setupide115112
34 cli.commands.shebang13121
35 cli.commands.uninstall211
36 cli.exportCmd1157
37 cli.commands.config623221
38 cli.commands.export02142114
39 cli.commands.publish32124153475
40 cli.internal1451
Uses a module listed above itPart of a loopThe module itself
1 build.options.publish2 build.errors.Diagnostic3 build.internal4 build.internals5 cli.launcher6 build.options7 build.compiler8 build.input9 build.preprocessing10 cli.commands.shared11 cli.commands.util12 cli.commands.repl13 cli.commands.run14 cli.commands.default15 cli.commands16 build.directives17 cli.config18 build.preprocessing.directives19 build.errors20 build.internal.util21 build22 build.actionable.ActionableDiagnostic23 build.bsp24 build.preprocessing.directives.PublishContextual25 cli.commands.bsp26 cli.commands.compile27 cli.commands.doc28 cli.commands.fix29 cli.commands.fmt30 cli.commands.github31 cli.commands.package032 cli.commands.pgp33 cli.commands.setupide34 cli.commands.shebang35 cli.commands.uninstall36 cli.exportCmd37 cli.commands.config38 cli.commands.export039 cli.commands.publish40 cli.internalbuild.options.publish1build.errors.Diagnostic2build.internal3build.internals4cli.launcher5build.options6build.compiler7build.input8build.preprocessing9cli.commands.shared10cli.commands.util11cli.commands.repl12cli.commands.run13cli.commands.default14cli.commands15build.directives16cli.config17build.preprocessing.directives18build.errors19build.internal.util20build21build.actionable.ActionableDiagnostic22build.bsp23build.preprocessing.directives.PublishContextual24cli.commands.bsp25cli.commands.compile26cli.commands.doc27cli.commands.fix28cli.commands.fmt29cli.commands.github30cli.commands.package031cli.commands.pgp32cli.commands.setupide33cli.commands.shebang34cli.commands.uninstall35cli.exportCmd36cli.commands.config37cli.commands.export038cli.commands.publish39cli.internal4021851151711331411131415711102313371232161124111101211151123213311441141515136412811611112121728121517292222211311171211412123141421324141125421314110112311623371151121312121111576232212142114321241534751451+144 more modules (most-connected shown)

At a glance — Code Health · 61% · Adequate · gated by X5 ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 55% · Adequate · gated by M2 ·

At a glance — Readiness · 70% · Strong ·

At a glance — Security · 66% · Adequate · gated by D29 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection401High / Critical
A02:2025 — Security Misconfiguration15High / Critical
A03:2025 — Software Supply Chain Failures8Medium

Roadmap

Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.mill; 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; Reconcile the README with reality: website/docs/guides/advanced/scala-wasm.md names Node.js 24, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 25, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 23, but the repository declares pinned 12.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.mill.+6.2 ptsLowADR Quality
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Licenses.scala.+3.1 ptsLowKnowledge 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.+5.2 ptsMediumArchitecture documentation
Reconcile the README with reality: website/docs/guides/advanced/scala-wasm.md names Node.js 24, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 25, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 23, but the repository declares pinned 12.+4.5 ptsMediumDocumentation accuracy
Resolve the 43 Orphaned file finding(s) in Knowledge Freshness — start with PgpSecretKeyCheck.scala, DirectiveHandler.scala, CliLogger.scala.+3.8 ptsMediumKnowledge Freshness
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor.+1.9 ptsLowBus Factor
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.+1.9 ptsLowBus 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.6 ptsMediumNullable reference types

File quality

Per-file score 0–10 — a quality signature. Of 154 files carrying findings, judged against the Production bar: 5% slop · 53% mixed · 42% near-clean.

FileScoreBandWorst signal
REDACTED1.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.9SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.5SlopIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.6MixedCyclomatic Complexity: Config.runCommand (cyclomatic 40)
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala6.0MixedExplicit Debt: FixmeComment
modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala6.0MixedExplicit Debt: TodoComment

How the grades work

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

Critical — 408

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 335

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 70

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

Could not be resolved — 14

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.

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

What we checked — 54 dimensions across the health lenses
D1D2D3D4D5D6D13D15D16D17D19D20D21D28D29D30D31D34D35D36D43AX10AX3AX4AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P6PF3S1X1X12X13X16X18X19X21X23X25X27X28X29X3X5

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

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 800 of 813 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1da91-346e-7f82-8f8f-546c3351acba.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) 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. This repository's dependency manifest (package.json) was found, but this pass cannot parse it for hygiene, 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 — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (package.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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 (project/settings/package.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. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — 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.
  • D26 Project Cohesion — 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. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
  • 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. `modules/cli/src/main/scala/scala/cli/commands/RestrictableCommand.scala`, `modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala`, `modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/ScalafixRules.scala`, … (+9 more) 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.
  • 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 REDACTED) is simply not read here yet.
  • AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • 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 (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / 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.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • 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.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • 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 Complexity6.2 / 10Adequate✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 6.2 / 10 · rule-coverage 100% · ceiling Prevented

36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Package.doPackage at 86.

Package.doPackage (cyclomatic 86)modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268
Publish.prepareFilesAndUpload (cyclomatic 60)modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:802
Run.runOnce (cyclomatic 49)modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460
Inputs.validateArgs (cyclomatic 43)modules/build/src/main/scala/scala/build/input/Inputs.scala:233
Config.runCommand (cyclomatic 40)REDACTED:26

+ 31 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with Package.doPackage (cyclomatic 86). — Refactoring it lifts Cyclomatic Complexity from 6.2 to about 6.5/10.

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

D2 · Cognitive Complexity5.1 / 10Adequate✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 5.1 / 10 · rule-coverage 100% · ceiling Prevented

65 method(s) exceeded the cognitive complexity threshold of 15; the worst was Config.runCommand at 154.

Config.runCommand (cognitive 154)REDACTED:26
Package.doPackage (cognitive 113)modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268
Publish.prepareFilesAndUpload (cognitive 100)modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:802
Run.runOnce (cognitive 94)modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460
PublishSetup.runCommand (cognitive 85)modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:38

+ 60 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with Config.runCommand (cognitive 154). — Refactoring it lifts Cognitive Complexity from 5.1 to about 5.4/10.

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

D3 · God Classes8.9 / 10Strong✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Prevented

16 over-large unit(s) detected — types, modules or files that carry too much.

FileTooLong: package0/Package.scala · ×7modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala
FunctionTooLong: index.SearchPageContent · ×5REDACTED:54
MethodTooLong: Artifacts.apply · ×4modules/options/src/main/scala/scala/build/Artifacts.scala:197

What to do

  1. Resolve the 7 FileTooLong finding(s) in God Classes — start with Package.scala, Publish.scala, Artifacts.scala. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 5 FunctionTooLong finding(s) in God Classes — start with REDACTED (2), FeaturesStickyNav.tsx, InstallStickyNav.tsx. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 4 MethodTooLong finding(s) in God Classes — start with Run.scala (2), Artifacts.scala, Publish.scala. — One of this dimension's main actionable groups (4 warning-level).

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

D4 · Code Duplication9.4 / 10Stronggated by 36 serious findings✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Verified

20 duplicated block group(s) detected. 1.6 % of the production lines (843 of 52,369) are in a reported copy. A further 16 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 3 of the 36 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (8 lines × 2) · ×3modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:150
Edited copy of a member (15 corresponding lines) · ×2modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:35
Duplicated block (13 lines × 2) · ×2modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:247
Duplicated block (12 lines × 2) · ×2modules/cli/src/main/scala/scala/cli/commands/pgp/PgpPull.scala:18
Duplicated block (10 lines × 2) · ×2modules/cli/src/main/scala/scala/cli/commands/bloop/BloopExit.scala:33

+ 24 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Package.scala, Update.scala, AsmTestRunner.scala. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with DirectiveHandler.scala, WrappedSourcesParams.java. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Publish.scala, PasswordCheck.scala. — One of this dimension's main actionable groups (2 warning-level).

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

D5 · Coupling7.8 / 10Strong✓ Tool-verified

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

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

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

Maturity: Documented → Verified → Prevented · effective 7.8 / 10 · rule-coverage 100% · ceiling Prevented

18 production modules (Mill), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a Mill module a helper method defines, a moduleDeps a function computes, and a module directory computed other than as a path over super.moduleDir are not visible there; 5 module(s) off the main sequence, with abstractness counted on 17 of the 18 (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).

Off the main sequence: build-macros · ×5

What to do

  1. Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).

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

D6 · Cohesion (LCOM4)9.4 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Verified

1 of 21 classes have LCOM4 above 3.

Low cohesion: BspServer (LCOM4 8)modules/build/src/main/scala/scala/build/bsp/BspServer.scala:19

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with BspServer.scala. — One of this dimension's main actionable groups (1 warning-level).

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

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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

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

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 5 serious findings✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: modules/cli/src/main/scala/scala/cli/commands/run/Run.scala (4×49=196); modules/options/src/main/scala/scala/build/options/BuildOptions.scala (5×36=180); modules/options/src/main/scala/scala/build/Artifacts.scala (5×35=175)

Hotspot: modules/cli/src/main/scala/scala/cli/commands/run/Run.scala · ×5modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460

What to do

  1. Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with Run.scala, BuildOptions.scala, Artifacts.scala. — One of this dimension's main actionable groups (5 warning-level).

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

D16 · Bus Factor7.6 / 10Strong✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 100% · ceiling Documented

35 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is modules/options/src/main/scala/scala/build/options/ScalaVersionUtil.scala. Counted over 145 of the 512 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

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

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt9.5 / 10Stronggated by 139 serious findings✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Prevented

139 deducted task-comment markers across 52369 LoC (0.3/KLoC) → score 9.5. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×80modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:382
FixmeComment · ×59modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:130

What to do

  1. Resolve the 80 TodoComment finding(s) in Explicit Debt — start with SbtProjectDescriptor.scala (9), RunWithWatchTestDefinitions.scala (6), JmhTests.scala (4). — One of this dimension's main actionable groups (80 warning-level).
  2. Resolve the 59 FixmeComment finding(s) in Explicit Debt — start with NativePackagerTests.scala (3), CustomWindowsEnvVarUpdater.scala (3), Artifacts.scala (2). — One of this dimension's main actionable groups (59 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

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

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundbuild.mill:103

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.mill. — One of this dimension's main actionable groups (1 recommendation-level).

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

D21 · Naming Consistency8.3 / 10Strong✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

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

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Verified

4 naming inconsistencies among 231 declarations measured against a convention their peers follow.

`isScalaCLIInstalledByInstallationScript` spells `CLI` where 55 names in the project spell it `Cli`modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:185
`findApplicationPathsOnPATH` spells `PATH` where 162 names in the project spell it `Path`modules/cli/src/main/scala/scala/cli/internal/ProcUtil.scala:72
`LinkJSInput` spells `JS` where 40 names in the project spell it `Js`modules/cli/src/main/scala/scala/cli/internal/ScalaJsLinker.scala:22
`UnrecognizedJSRuntimeError` spells `JS` where 40 names in the project spell it `Js`modules/core/src/main/scala/scala/build/errors/UnrecognizedJSRuntimeError.scala:3

What to do

  1. Resolve the 1 `isScalaCLIInstalledByInstallationScript` spells `CLI` where 55 names in… finding(s) in Naming Consistency — start with Update.scala. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `findApplicationPathsOnPATH` spells `PATH` where 162 names in the… finding(s) in Naming Consistency — start with ProcUtil.scala. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `LinkJSInput` spells `JS` where 40 names in the project spell it `Js` finding(s) in Naming Consistency — start with ScalaJsLinker.scala. — One of this dimension's main actionable groups (1 recommendation-level).

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.3 / 10Critical✓ Tool-verified

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

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

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

Maturity: Documented → Verified → Prevented · effective 0.3 / 10 · rule-coverage 100% · ceiling Documented

401 finding(s): 0 critical, 399 high, 0 medium, 2 low. 379 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 15 file(s) — `.github/scripts/verify_old_cpus.sh` (line 7), `gifs/demo-magic.sh` (line 106), `modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala`, `modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala`, … (+10 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
  3. No action in Static Analysis (SAST) — all 379 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 (379 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

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

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

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D31 · IaC & Container Security6.9 / 10Adequate✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 6.9 / 10 · rule-coverage 100% · ceiling Documented

15 finding(s): 0 critical, 7 high, 7 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D34 · Knowledge Freshness7.0 / 10Adequate✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Documented

44 of 145 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is modules/core/src/main/scala/scala/build/internals/Licenses.scala. Counted over 145 of the 512 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledgemodules/core/src/main/scala/scala/build/internals/Licenses.scala:1
Orphaned file · ×43modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:1
Further orphaned files (smaller)

What to do

  1. Resolve the 43 Orphaned file finding(s) in Knowledge Freshness — start with PgpSecretKeyCheck.scala, DirectiveHandler.scala, CliLogger.scala. — One of this dimension's main actionable groups (43 recommendation-level).
  2. Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Licenses.scala. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.8 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: ScalaJsOptions.scala↔ScalaJsLinkerConfig.scala 67%; DependencyUpdate.scala↔Export.scala 60%; RestrictedCommandsParser.scala↔ScalaCommand.scala 57%

Boundary-crossing change coupling: ScalaJsOptions.scala ↔ ScalaJsLinkerConfig.scalamodules/cli/src/main/scala/scala/cli/commands/shared/ScalaJsOptions.scala:1
Change coupling: DependencyUpdate.scala ↔ Export.scala · ×5modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala:1

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ScalaJsOptions.scala. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 5 Change coupling finding(s) in Change Coupling — start with DependencyUpdate.scala (2), RestrictedCommandsParser.scala, REDACTED. — One of this dimension's main actionable groups (5 warning-level).

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

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.6 / 10Exemplary✓ Tool-verified

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

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

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

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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

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

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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

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

  • `Logger` declares 20 abstract members: `error`, `message`, `log`, `log`, `debug`, `log`, `log`, `debug`, `exit`, `coursierLogger`, `bloopRifleLogger`, `scalaJsLogger`, `scalaNativeTestLogger`, `scalaNativeCliInternalLoggerOptions`, `compilerOutputStream`, `verbosity`, `experimentalWarning`, `flushExperimentalWarnings`, `deprecationWarning`, `flushDeprecationWarnings`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 20 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — modules/core/src/main/scala/scala/build/Logger.scala:13

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

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

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

  • A placeholder string ("//> using publish.description \"Lorem ip…") is still in shipped code — typical of generated boilerplate that was never filled in. — modules/directives/src/main/scala/scala/build/preprocessing/directives/Publish.scala:22

What to do

  • Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

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

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

  • `noArgs` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — modules/options/src/main/scala/scala/build/CoursierUtils.scala:9
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×2) — modules/integration/src/test/scala/scala/cli/integration/RunTestDefinitions.scala:462, modules/integration/src/test/scala/scala/cli/integration/RunTestsDefault.scala:356

What to do

  • Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
  • Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)9.3 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

M4 · Documentation accuracy4.0 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

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

  • website/docs/guides/advanced/scala-wasm.md names Node.js 24, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — website/docs/guides/advanced/scala-wasm.md:61
  • website/docs/guides/advanced/scala-wasm.md names Node.js 25, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — website/docs/guides/advanced/scala-wasm.md:74
  • website/docs/guides/advanced/scala-wasm.md names Node.js 23, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — website/docs/guides/advanced/scala-wasm.md:76

What to do

  • Reconcile the README with reality: website/docs/guides/advanced/scala-wasm.md names Node.js 24, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 25, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 23, but the repository declares pinned 12.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

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

P10 · Library API & versioning6.8 / 10Adequate✓ Tool-verified

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

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

  • 4 public types in `scala.cli.internal` are marked as implementation by their own namespace, folder or name: `PgpProxyMakerSubst` (modules/cli/src/main/java/scala/cli/commands/publish/PgpProxyMakerSubst.java:12, `internal`), `BouncycastleSignerMakerSubst` (modules/cli/src/main/java/scala/cli/internal/BouncycastleSignerMakerSubst.java:19, `internal`), `CsJniUtilsFeature` (modules/cli/src/main/java/scala/cli/internal/CsJniUtilsFeature.java:11, `internal`), `LibsodiumjniFeature` (modules/cli/src/main/java/scala/cli/internal/LibsodiumjniFeature.java:11, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — modules/cli/src/main/java/scala/cli/commands/publish/PgpProxyMakerSubst.java:12

What to do

  • Hide `scala.cli.internal` (`PgpProxyMakerSubst`, `BouncycastleSignerMakerSubst`, `CsJniUtilsFeature`, `LibsodiumjniFeature`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

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

P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2

What to do

  • Dependabot is configured but does not watch `gitsubmodule` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

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 Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

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

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's Scala source and the Java beside it: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves 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.

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

  • MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×9) — modules/build/src/main/scala/scala/build/input/ElementsUtils.scala:82, modules/build/src/main/scala/scala/build/input/Inputs.scala:117, modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:117, …

What to do

  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 9 sites, not one: `modules/build/src/main/scala/scala/build/input/ElementsUtils.scala:82` (MessageDigest.getInstance("SHA-1")), `modules/build/src/main/scala/scala/build/input/Inputs.scala:117` (MessageDigest.getInstance("SHA-1")), `modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:117` (MessageDigest.getInstance("MD5")), `modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:321` (MessageDigest.getInstance("SHA-1")), `modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:608` (MessageDigest.getInstance("SHA-1")), `modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:19` (MessageDigest.getInstance("SHA-1")), `modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:29` (MessageDigest.getInstance("SHA-1")), `modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:64` (MessageDigest.getInstance("SHA-1")), and 1 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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

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

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

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

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

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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

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

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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

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

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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

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

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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

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

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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

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

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.

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

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:124, modules/cli/src/main/scala/scala/cli/commands/shared/SharedCompilationServerOptions.scala:160
  • `case NonFatal(_)` 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. — modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:156

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

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

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

  • No build over this repository's 605 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

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

LensScoreRatingImpact
Code Health61%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96%ExemplarySolid.
Maturity55%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness70%StrongSolid.
Security66%Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

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

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's 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 (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / 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 — ~43805 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 — dependency manifest found but not parsed for hygiene
  • D14 License Compliance — Package manifest not parsed for licence data — analyzer language-coverage gap
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • 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
  • D26 Project Cohesion — D26 measured no build unit over this repository's .java, .scala source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 14 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • 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): 281 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'.
  • 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's 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
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's 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)

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

Critical — 408 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 354 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×1
  • Orphaned knowledge modules/core/src/main/scala/scala/build/internals/Licenses.scala:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: ScalaJsOptions.scala ↔ ScalaJsLinkerConfig.scala modules/cli/src/main/scala/scala/cli/commands/shared/ScalaJsOptions.scala:1 — `modules/cli/src/main/scala/scala/cli/commands/shared/ScalaJsOptions.scala` (context cli) and `modules/options/src/main/scala/scala/build/internal/ScalaJsLinkerConfig.scala` (context options) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `3e8a3708` Add --js-wasm-jspi and //> using wasmJspi to enable JSPI on Wasm (#4550); `bbe65037` refactor how ES version is validated (#4484); `53cd950d` Support newer `esVersion` strings; hard error on unkwnown `esVersion`… — run `git show` on any of them.
Serious — 335 finding(s)
D17 · Explicit Debt · TodoComment · ×80
  • TodoComment modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:382 — // TODO handle multiple — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/options/src/main/scala/scala/build/CoursierUtils.scala:9 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala:157 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/options/src/main/scala/scala/build/internals/Util.scala:157 — // TODO: Add support for Gradle Module variants — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/BloopTests.scala:141 — // TODO make this pass reliably on Mac CI — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/RunWithWatchTestDefinitions.scala:10 — // TODO make this pass reliably on Mac CI — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/RunWithWatchTestDefinitions.scala:337 — // TODO make this pass reliably on Mac CI — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/RunWithWatchTestDefinitions.scala:443 — // TODO make this pass reliably on Mac CI — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/RunWithWatchTestDefinitions.scala:481 — // TODO make this pass reliably on Mac CI — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/BspTestDefinitions.scala:1436 — // TODO This test only checks if the native launcher of Scala CLI is able to parse cancel params, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/BspTestDefinitions.scala:2177 — // TODO: test for nightly, too — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/BspTestDefinitions.scala:2203 — // TODO: test for nightly, too — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/CompileTestDefinitions.scala:819 — // TODO: make this work on Windows: https://github.com/VirtusLab/scala-cli/issues/2973
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/CompilerPluginTestDefinitions.scala:71 — // TODO: this shouldn't require running with --server=false — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/ExportSbtTestDefinitions.scala:55 — // TODO: enable when available — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/ExportSbtTestDefinitions.scala:56 — // TODO: enable when available — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/ExportScalaOrientedBuildToolsTestDefinitions.scala:30 — // todo: remove this hack after the PR https://github.com/VirtusLab/scala-cli/pull/3046 is merged
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/JmhTests.scala:28 — // TODO extract running benchmarks to a separate scope, or a separate sub-command — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/JmhTests.scala:53 — // TODO fix setting jmh via a reload & add tests for it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/JmhTests.scala:111 — // TODO make package with --jmh build an artifact that actually runs benchmarks — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/JmhTests.scala:141 — // TODO add proper support for JMH export, we're checking if it doesn't fail the command for now — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/NativePackagerTests.scala:410 — // TODO: restore this test when `registry-1.docker.io` is stable again — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/PackageTestDefinitions.scala:1270 — // TODO: restore this test when `registry-1.docker.io` is stable again — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/PackageTestDefinitions.scala:1277 — // TODO: restore this test when `registry-1.docker.io` is stable again — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment modules/integration/src/test/scala/scala/cli/integration/PackageTestDefinitions.scala:1284 — // TODO: restore this test when `registry-1.docker.io` is stable again — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 55 more in this group — see findings.md.
D17 · Explicit Debt · FixmeComment · ×59
  • FixmeComment modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:130 — // FIXME Check if these are files too — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/test-runner/src/main/scala/scala/build/testrunner/FrameworkUtils.scala:262 — // FIXME Check if these are files too — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/options/src/main/scala/scala/build/Artifacts.scala:826 — // FIXME Shouldn't we force the scala-library version too? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/options/src/main/scala/scala/build/Artifacts.scala:840 — // FIXME Many parameters that we could allow to customize here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/options/src/main/scala/scala/build/TemporaryInMemoryRepository.scala:57 — // FIXME Escaping / de-escaping needed here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/options/src/main/scala/scala/build/options/InternalOptions.scala:17 — // FIXME Should be removed, not a real option (not meant to be set from using directives) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/options/src/main/scala/scala/build/options/JavaOptions.scala:101 — // FIXME Workaround, until this is automatically handled by coursier-jvm — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/options/src/main/scala/scala/build/options/scalajs/ScalaJsLinkerOptions.scala:22 — // FIXME Log error? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/options/src/main/scala/scala/build/internal/FetchExternalBinary.scala:78 — // FIXME Log the whole stack trace of nf — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/NativePackagerTests.scala:121 — // FIXME: building dmg package sometimes fails with: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/NativePackagerTests.scala:417 — // FIXME for some reason, this test became flaky on the CI — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/NativePackagerTests.scala:432 — // FIXME this got flaky on the CI again — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/PackageTestDefinitions.scala:1005 — // FIXME Check that dest is indeed a binary? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/TestNativeImageOnScala3.scala:36 — // FIXME Check that dest is indeed a binary? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/RunScalaJsTestDefinitions.scala:252 — // FIXME: figure out why this started failing on the CI: https://github.com/VirtusLab/scala-cli/issues/3335
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/TestTestDefinitions.scala:1038 — // FIXME: figure out why this started failing on the CI: https://github.com/VirtusLab/scala-cli/issues/3335
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/RunScalacCompatTestDefinitions.scala:79 — // FIXME We don't really use the run command here, in spite of being in RunTests… — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/RunScalacCompatTestDefinitions.scala:449 — // FIXME this shouldn't be flaky on Mac — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/RunTestDefinitions.scala:278 — // FIXME We need to have the pretty-stacktraces stuff take scala.colored-stack-traces into account — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/SparkTestDefinitions.scala:117 — // FIXME Maybe Scala CLI should handle that itself, when on Windows, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/integration/src/test/scala/scala/cli/integration/TestTestDefinitions.scala:808 — // FIXME: revert to using default Scala Native version when scalatest supports 0.5.x — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/directives/src/main/scala/scala/build/directives/DirectiveValueParser.scala:59 — // FIXME: handle similar parsing errors in the directive declaration instead of hacks like this one — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:190 — // FIXME Likely a 404 Not found, that should be taken into account by the cache — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/core/src/main/scala/scala/build/internals/OsLibc.scala:56 — // FIXME These values should be the default ones in coursier-jvm — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment modules/config/src/main/scala/scala/cli/config/ConfigDb.scala:97 — // FIXME We're copying / moving arrays around quite a bit here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 34 more in this group — see findings.md.
S1 · Web-Security Posture · Weak hash algorithm · ×9
  • Weak hash algorithm modules/build/src/main/scala/scala/build/input/ElementsUtils.scala:82 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm modules/build/src/main/scala/scala/build/input/Inputs.scala:117 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:117 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:321 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:608 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:19 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:29 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:64 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm modules/options/src/main/scala/scala/build/options/BuildOptions.scala:614 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
D3 · God Classes · FileTooLong · ×7
  • FileTooLong: package0/Package.scala modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala — FileTooLong — 1112 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 612 over it, 2.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: publish/Publish.scala modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala — FileTooLong — 943 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 443 over it, 1.89× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: build/Artifacts.scala modules/options/src/main/scala/scala/build/Artifacts.scala — FileTooLong — 827 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 327 over it, 1.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: shared/SharedOptions.scala modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala — FileTooLong — 761 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 261 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: run/Run.scala modules/cli/src/main/scala/scala/cli/commands/run/Run.scala — FileTooLong — 734 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 234 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: doc/GenerateReferenceDoc.scala modules/generate-reference-doc/src/main/scala/scala/cli/doc/GenerateReferenceDoc.scala — FileTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 59 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: options/BuildOptions.scala modules/options/src/main/scala/scala/build/options/BuildOptions.scala — FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D31 · IaC & Container Security · Medium IaC · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D15 · Churn × Complexity Hotspots · Hotspot · ×5
  • Hotspot: modules/cli/src/main/scala/scala/cli/commands/run/Run.scala modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460 — modules/cli/src/main/scala/scala/cli/commands/run/Run.scala changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in Run.runOnce at line 460. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:19:14 +01:00' --until='2026-11-13 16:19:14 +01:00' --full-history --no-merges -- modules/cli/src/main/scala/scala/cli/commands/run/Run.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: modules/options/src/main/scala/scala/build/options/BuildOptions.scala modules/options/src/main/scala/scala/build/options/BuildOptions.scala:353 — modules/options/src/main/scala/scala/build/options/BuildOptions.scala changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in BuildOptions.computeScalaParams at line 353. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:19:14 +01:00' --until='2026-11-13 16:19:14 +01:00' --full-history --no-merges -- modules/options/src/main/scala/scala/build/options/BuildOptions.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: modules/options/src/main/scala/scala/build/Artifacts.scala modules/options/src/main/scala/scala/build/Artifacts.scala:197 — modules/options/src/main/scala/scala/build/Artifacts.scala changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in Artifacts.apply at line 197. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:19:14 +01:00' --until='2026-11-13 16:19:14 +01:00' --full-history --no-merges -- modules/options/src/main/scala/scala/build/Artifacts.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: modules/build/src/main/scala/scala/build/CrossSources.scala modules/build/src/main/scala/scala/build/CrossSources.scala:165 — modules/build/src/main/scala/scala/build/CrossSources.scala changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in CrossSources.forInputs at line 165. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:19:14 +01:00' --until='2026-11-13 16:19:14 +01:00' --full-history --no-merges -- modules/build/src/main/scala/scala/build/CrossSources.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:38 — modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in PublishSetup.runCommand at line 38. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:19:14 +01:00' --until='2026-11-13 16:19:14 +01:00' --full-history --no-merges -- modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D3 · God Classes · FunctionTooLong · ×5
  • FunctionTooLong: index.SearchPageContent REDACTED:54 — FunctionTooLong — SearchPageContent runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: FeaturesStickyNav.FeaturesStickyNav website/src/components/FeaturesStickyNav.tsx:35 — FunctionTooLong — FeaturesStickyNav runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: InstallStickyNav.InstallStickyNav website/src/components/InstallStickyNav.tsx:36 — FunctionTooLong — InstallStickyNav runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ScalaCliWordmark.ScalaCliWordmark website/src/components/ScalaCliWordmark.tsx:10 — FunctionTooLong — ScalaCliWordmark runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.Index website/src/pages/index.tsx:14 — FunctionTooLong — Index runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D35 · Change Coupling · Change coupling · ×5
  • Change coupling: DependencyUpdate.scala ↔ Export.scala modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala:1 — `modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala` and `modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala` change together 60% of the time (12 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `34a3a93c` Support links in using file directive (implements #1328) (#3681); `653b2f1c` chore: make `--test` an `Option[Boolean]`; `0e44882b` Move `ScopeOptions` to `SharedOptions` (#3612) — run `git show` on any of them.
  • Change coupling: RestrictedCommandsParser.scala ↔ ScalaCommand.scala modules/cli/src/main/scala/scala/cli/commands/RestrictedCommandsParser.scala:1 — `modules/cli/src/main/scala/scala/cli/commands/RestrictedCommandsParser.scala` and `modules/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `f5639233` Add deprecation mechanism for CLI options, directives, sub-commands, …; `66c2d356` Add a global flag to suppress deprecation warnings (#3406); `16f321d2` Accumulate exp warnings with logger (#2376) — run `git show` on any of them.
  • Change coupling: DependencyUpdate.scala ↔ SetupIde.scala modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala:1 — `modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala` and `modules/cli/src/main/scala/scala/cli/commands/setupide/SetupIde.scala` change together 50% of the time (10 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `34a3a93c` Support links in using file directive (implements #1328) (#3681); `88870450` Make object wrapper extend App (#2556); `f562c0da` Add computing version for BuildInfo — run `git show` on any of them.
  • Change coupling: REDACTED ↔ PgpSecretKeyCheck.scala REDACTED:1 — `REDACTED` and `modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `6f7eebb0` Remove unused imports (#2916); `74f07070` Make pgp external command download java 17 if needed Add tests; `4fd13e03` Use ASCII armored secret key — run `git show` on any of them.
  • Change coupling: ScalaCommand.scala ↔ HelpGroupOptions.scala modules/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala:1 — `modules/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala` and `modules/cli/src/main/scala/scala/cli/commands/shared/HelpGroupOptions.scala` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `ea6155c0` Add `--envs-help` to print available environment variables; `394fb2de` Add help for repl, scalafmt and scaladoc (at that commit the file was still `modules/cli-options/src/main/scala/scala/cli/commands/HelpGroupOptions.scala`); `748128a8` Fix printing help for js and native (#985) (at that commit the file was still `modules/cli-options/src/main/scala/scala/cli/commands/HelpGroupOptions.scala`) — run `git show` on any of them.
D5 · Coupling · Off the main sequence · ×5
  • Off the main sequence: build-macros — build-macros: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: tasty-lib — tasty-lib: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: specification-level — specification-level: abstractness 0.13, instability 0.00, distance 0.88 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: test-runner — test-runner: abstractness 0.18, instability 0.00, distance 0.82 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
  • Off the main sequence: scala-cli-bsp — scala-cli-bsp: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
D3 · God Classes · MethodTooLong · ×4
  • MethodTooLong: Artifacts.apply modules/options/src/main/scala/scala/build/Artifacts.scala:197 — MethodTooLong — apply runs 348 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 248 over it, 3.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Publish.prepareFilesAndUpload modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:802 — MethodTooLong — prepareFilesAndUpload runs 305 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 205 over it, 3.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Run.runOnce modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460 — MethodTooLong — runOnce runs 294 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 194 over it, 2.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Run.runCommand modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:117 — MethodTooLong — runCommand runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:150 — modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:150-157 | modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:353-360 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:150` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:195 — modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:195-202 | modules/options/src/main/scala/scala/build/TemporaryInMemoryRepository.scala:23-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:98 — modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:98-105 | modules/test-runner/src/main/scala/scala/build/testrunner/FrameworkUtils.scala:231-238 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×2
  • Edited copy of a member (15 corresponding lines) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:35 — modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:35-50 | modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:52-66 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) modules/scala-cli-bsp/src/main/java/scala/build/bsp/WrappedSourcesParams.java:33 — modules/scala-cli-bsp/src/main/java/scala/build/bsp/WrappedSourcesParams.java:33-47 | modules/scala-cli-bsp/src/main/java/scala/build/bsp/WrappedSourcesResult.java:38-52 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:247 — modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:247-259 | modules/cli/src/main/scala/scala/cli/commands/publish/PublishLocal.scala:65-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:245` calls `orExit` and `modules/cli/src/main/scala/scala/cli/commands/publish/PublishLocal.scala:63` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:22 — modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:22-34 | modules/cli/src/main/scala/scala/cli/commands/publish/checks/UserCheck.scala:22-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) modules/cli/src/main/scala/scala/cli/commands/pgp/PgpPull.scala:18 — modules/cli/src/main/scala/scala/cli/commands/pgp/PgpPull.scala:18-29 | modules/cli/src/main/scala/scala/cli/commands/pgp/PgpPush.scala:18-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:112 — modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:112-123 | modules/test-runner/src/main/scala/scala/build/testrunner/FrameworkUtils.scala:245-256 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `logger` to `Logger` in one and `Logger): Iterator[String] = if (Files.isDirectory(classPathEntry)` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) modules/cli/src/main/scala/scala/cli/commands/bloop/BloopExit.scala:33 — modules/cli/src/main/scala/scala/cli/commands/bloop/BloopExit.scala:33-42 | modules/cli/src/main/scala/scala/cli/commands/bloop/BloopStart.scala:45-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/commands/bloop/BloopExit.scala:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) modules/cli/src/main/scala/scala/cli/commands/new/New.scala:40 — modules/cli/src/main/scala/scala/cli/commands/new/New.scala:40-49 | modules/cli/src/main/scala/scala/cli/launcher/LauncherCli.scala:61-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/commands/new/New.scala:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:175 — modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:175-183 | modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:187-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:132 — modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:132-141 | modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:190-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
X3 · Exception handling · Swallowed exception (empty catch) · ×2
  • Swallowed exception (empty catch) modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:124 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) modules/cli/src/main/scala/scala/cli/commands/shared/SharedCompilationServerOptions.scala:160 — 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.
D1 · Cyclomatic Complexity · Package.doPackage (cyclomatic 86) · ×1
  • Package.doPackage (cyclomatic 86) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268 — Package.doPackage has cyclomatic complexity 86 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Publish.prepareFilesAndUpload (cyclomatic 60) · ×1
  • Publish.prepareFilesAndUpload (cyclomatic 60) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:802 — Publish.prepareFilesAndUpload has cyclomatic complexity 60 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Run.runOnce (cyclomatic 49) · ×1
  • Run.runOnce (cyclomatic 49) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460 — Run.runOnce has cyclomatic complexity 49 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Inputs.validateArgs (cyclomatic 43) · ×1
  • Inputs.validateArgs (cyclomatic 43) modules/build/src/main/scala/scala/build/input/Inputs.scala:233 — Inputs.validateArgs has cyclomatic complexity 43 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Config.runCommand (cyclomatic 40) · ×1
  • Config.runCommand (cyclomatic 40) REDACTED:26 — Config.runCommand has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PublishSetup.runCommand (cyclomatic 38) · ×1
  • PublishSetup.runCommand (cyclomatic 38) modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:38 — PublishSetup.runCommand has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BuildOptions.computeScalaParams (cyclomatic 36) · ×1
  • BuildOptions.computeScalaParams (cyclomatic 36) modules/options/src/main/scala/scala/build/options/BuildOptions.scala:353 — BuildOptions.computeScalaParams has cyclomatic complexity 36 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · Artifacts.apply (cyclomatic 35) · ×1
  • Artifacts.apply (cyclomatic 35) modules/options/src/main/scala/scala/build/Artifacts.scala:197 — Artifacts.apply has cyclomatic complexity 35 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Run.runCommand (cyclomatic 32) · ×1
  • Run.runCommand (cyclomatic 32) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:117 — Run.runCommand has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · Export.runCommand (cyclomatic 31) · ×1
  • Export.runCommand (cyclomatic 31) modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala:138 — Export.runCommand has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MillProject.writeTo (cyclomatic 25) · ×1
  • MillProject.writeTo (cyclomatic 25) modules/cli/src/main/scala/scala/cli/exportCmd/MillProject.scala:39 — MillProject.writeTo has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SemanticdbProcessor.postProcess (cyclomatic 23) · ×1
  • SemanticdbProcessor.postProcess (cyclomatic 23) modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:14 — SemanticdbProcessor.postProcess has cyclomatic complexity 23 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D1 · Cyclomatic Complexity · DirectiveHandler.deriveParserImpl (cyclomatic 23) · ×1
  • DirectiveHandler.deriveParserImpl (cyclomatic 23) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:132 — DirectiveHandler.deriveParserImpl has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · CrossSources.forInputs (cyclomatic 21) · ×1
  • CrossSources.forInputs (cyclomatic 21) modules/build/src/main/scala/scala/build/CrossSources.scala:165 — CrossSources.forInputs has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · GenerateReferenceDoc.cliOptionsContent (cyclomatic 21) · ×1
  • GenerateReferenceDoc.cliOptionsContent (cyclomatic 21) modules/generate-reference-doc/src/main/scala/scala/cli/doc/GenerateReferenceDoc.scala:123 — GenerateReferenceDoc.cliOptionsContent has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ScalaCli.main0 (cyclomatic 20) · ×1
  • ScalaCli.main0 (cyclomatic 20) modules/cli/src/main/scala/scala/cli/ScalaCli.scala:242 — ScalaCli.main0 has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · Compile.runCommand (cyclomatic 20) · ×1
  • Compile.runCommand (cyclomatic 20) modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala:44 — Compile.runCommand has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · GitTag.get (cyclomatic 20) · ×1
  • GitTag.get (cyclomatic 20) modules/options/src/main/scala/scala/build/options/ComputeVersion.scala:31 — GitTag.get has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FeaturesStickyNav.FeaturesStickyNav (cyclomatic 20) · ×1
  • FeaturesStickyNav.FeaturesStickyNav (cyclomatic 20) website/src/components/FeaturesStickyNav.tsx:35 — FeaturesStickyNav.FeaturesStickyNav has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 138, 105, 54, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · InstallStickyNav.InstallStickyNav (cyclomatic 20) · ×1
  • InstallStickyNav.InstallStickyNav (cyclomatic 20) website/src/components/InstallStickyNav.tsx:36 — InstallStickyNav.InstallStickyNav has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 137, 104, 54, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · Build.watch (cyclomatic 19) · ×1
  • Build.watch (cyclomatic 19) modules/build/src/main/scala/scala/build/Build.scala:801 — Build.watch has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PgpSecretKeyCheck.defaultValue (cyclomatic 19) · ×1
  • PgpSecretKeyCheck.defaultValue (cyclomatic 19) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:278 — PgpSecretKeyCheck.defaultValue has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Build.buildProject (cyclomatic 18) · ×1
  • Build.buildProject (cyclomatic 18) modules/build/src/main/scala/scala/build/Build.scala:1026 — Build.buildProject has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Publish.maybePublish (cyclomatic 18) · ×1
  • Publish.maybePublish (cyclomatic 18) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:381 — Publish.maybePublish has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Publish.buildFileSet (cyclomatic 18) · ×1
  • Publish.buildFileSet (cyclomatic 18) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:497 — Publish.buildFileSet has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Build.build (cyclomatic 17) · ×1
  • Build.build (cyclomatic 17) modules/build/src/main/scala/scala/build/Build.scala:377 — Build.build has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Inputs.forNonEmptyArgs (cyclomatic 17) · ×1
  • Inputs.forNonEmptyArgs (cyclomatic 17) modules/build/src/main/scala/scala/build/input/Inputs.scala:331 — Inputs.forNonEmptyArgs has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · ExtractedDirectives.from (cyclomatic 17) · ×1
  • ExtractedDirectives.from (cyclomatic 17) modules/build/src/main/scala/scala/build/preprocessing/ExtractedDirectives.scala:25 — ExtractedDirectives.from has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RepositoryParser.repositoryOpt (cyclomatic 17) · ×1
  • RepositoryParser.repositoryOpt (cyclomatic 17) modules/cli/src/main/scala/scala/cli/commands/publish/RepositoryParser.scala:10 — RepositoryParser.repositoryOpt has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CustomProgressBarRefreshDisplay.display (cyclomatic 17) · ×1
  • CustomProgressBarRefreshDisplay.display (cyclomatic 17) modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:153 — CustomProgressBarRefreshDisplay.display has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.SearchPageContent (cyclomatic 17) · ×1
  • index.SearchPageContent (cyclomatic 17) REDACTED:54 — index.SearchPageContent has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Build.scalaNativeSupported (cyclomatic 16) · ×1
  • Build.scalaNativeSupported (cyclomatic 16) modules/build/src/main/scala/scala/build/Build.scala:657 — Build.scalaNativeSupported has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SlothPatcher.patchJar (cyclomatic 16) · ×1
  • SlothPatcher.patchJar (cyclomatic 16) modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:447 — SlothPatcher.patchJar has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SharedOptions.buildOptions (cyclomatic 16) · ×1
  • SharedOptions.buildOptions (cyclomatic 16) modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:364 — SharedOptions.buildOptions has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · WrappedSourceItem.equals (cyclomatic 16) · ×1
  • WrappedSourceItem.equals (cyclomatic 16) modules/scala-cli-bsp/src/main/java/scala/build/bsp/WrappedSourceItem.java:73 — WrappedSourceItem.equals has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.SearchResultItem (cyclomatic 16) · ×1
  • index.SearchResultItem (cyclomatic 16) REDACTED:287 — index.SearchResultItem has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · Config.runCommand (cognitive 154) · ×1
  • Config.runCommand (cognitive 154) REDACTED:26 — Config.runCommand has cognitive complexity 154 (threshold 15). Drivers by points: if/else 31 (95 pts), match/switch 8 (47 pts), loops 1 (7 pts), boolean chains 5 (nesting depth added 109). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · Package.doPackage (cognitive 113) · ×1
  • Package.doPackage (cognitive 113) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268 — Package.doPackage has cognitive complexity 113 (threshold 15). Drivers by points: if/else 49 (85 pts), match/switch 9 (24 pts), boolean chains 4 (nesting depth added 51). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Publish.prepareFilesAndUpload (cognitive 100) · ×1
  • Publish.prepareFilesAndUpload (cognitive 100) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:802 — Publish.prepareFilesAndUpload has cognitive complexity 100 (threshold 15). Drivers by points: if/else 41 (60 pts), loops 7 (15 pts), match/switch 7 (10 pts), boolean chains 8, error handling 5 (7 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Run.runOnce (cognitive 94) · ×1
  • Run.runOnce (cognitive 94) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460 — Run.runOnce has cognitive complexity 94 (threshold 15). Drivers by points: if/else 30 (63 pts), match/switch 5 (15 pts), loops 2 (9 pts), boolean chains 7 (nesting depth added 50). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PublishSetup.runCommand (cognitive 85) · ×1
  • PublishSetup.runCommand (cognitive 85) modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:38 — PublishSetup.runCommand has cognitive complexity 85 (threshold 15). Drivers by points: if/else 38 (71 pts), match/switch 4 (8 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Run.runCommand (cognitive 60) · ×1
  • Run.runCommand (cognitive 60) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:117 — Run.runCommand has cognitive complexity 60 (threshold 15). Drivers by points: if/else 18 (23 pts), loops 6 (19 pts), match/switch 6 (15 pts), boolean chains 3 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GenerateReferenceDoc.cliOptionsContent (cognitive 58) · ×1
  • GenerateReferenceDoc.cliOptionsContent (cognitive 58) modules/generate-reference-doc/src/main/scala/scala/cli/doc/GenerateReferenceDoc.scala:123 — GenerateReferenceDoc.cliOptionsContent has cognitive complexity 58 (threshold 15). Drivers by points: if/else 17 (35 pts), loops 5 (13 pts), match/switch 1 (6 pts), boolean chains 4 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Inputs.validateArgs (cognitive 57) · ×1
  • Inputs.validateArgs (cognitive 57) modules/build/src/main/scala/scala/build/input/Inputs.scala:233 — Inputs.validateArgs has cognitive complexity 57 (threshold 15). Drivers by points: if/else 34 (40 pts), boolean chains 14, match/switch 1 (3 pts) (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Artifacts.apply (cognitive 48) · ×1
  • Artifacts.apply (cognitive 48) modules/options/src/main/scala/scala/build/Artifacts.scala:197 — Artifacts.apply has cognitive complexity 48 (threshold 15). Drivers by points: if/else 23 (27 pts), match/switch 10 (15 pts), boolean chains 5, loops 1 (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Export.runCommand (cognitive 45) · ×1
  • Export.runCommand (cognitive 45) modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala:138 — Export.runCommand has cognitive complexity 45 (threshold 15). Drivers by points: if/else 27 (33 pts), boolean chains 6, loops 4 (6 pts) (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MillProject.writeTo (cognitive 41) · ×1
  • MillProject.writeTo (cognitive 41) modules/cli/src/main/scala/scala/cli/exportCmd/MillProject.scala:39 — MillProject.writeTo has cognitive complexity 41 (threshold 15). Drivers by points: if/else 28 (32 pts), match/switch 3 (5 pts), loops 4 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SlothPatcher.patchJar (cognitive 40) · ×1
  • SlothPatcher.patchJar (cognitive 40) modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:447 — SlothPatcher.patchJar has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (31 pts), error handling 1 (5 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · PgpSecretKeyCheck.defaultValue (cognitive 40) · ×1
  • PgpSecretKeyCheck.defaultValue (cognitive 40) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:278 — PgpSecretKeyCheck.defaultValue has cognitive complexity 40 (threshold 15). Drivers by points: if/else 21 (30 pts), match/switch 4 (8 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitTag.get (cognitive 37) · ×1
  • GitTag.get (cognitive 37) modules/options/src/main/scala/scala/build/options/ComputeVersion.scala:31 — GitTag.get has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (22 pts), match/switch 2 (7 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Compile.runCommand (cognitive 36) · ×1
  • Compile.runCommand (cognitive 36) modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala:44 — Compile.runCommand has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 6 (15 pts), match/switch 3 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Build.buildProject (cognitive 32) · ×1
  • Build.buildProject (cognitive 32) modules/build/src/main/scala/scala/build/Build.scala:1026 — Build.buildProject has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (25 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Build.watch (cognitive 31) · ×1
  • Build.watch (cognitive 31) modules/build/src/main/scala/scala/build/Build.scala:801 — Build.watch has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 4 (7 pts), boolean chains 3, loops 3, error handling 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DefaultFile.runCommand (cognitive 30) · ×1
  • DefaultFile.runCommand (cognitive 30) modules/cli/src/main/scala/scala/cli/commands/default/DefaultFile.scala:58 — DefaultFile.runCommand has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (4 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Build.build (cognitive 29) · ×1
  • Build.build (cognitive 29) modules/build/src/main/scala/scala/build/Build.scala:377 — Build.build has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 4 (7 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SemanticdbProcessor.postProcess (cognitive 29) · ×1
  • SemanticdbProcessor.postProcess (cognitive 29) modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:14 — SemanticdbProcessor.postProcess has cognitive complexity 29 (threshold 15). Drivers by points: loops 11 (22 pts), if/else 5 (6 pts), match/switch 1 (nesting depth added 12). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D2 · Cognitive Complexity · ScalaCli.main0 (cognitive 29) · ×1
  • ScalaCli.main0 (cognitive 29) modules/cli/src/main/scala/scala/cli/ScalaCli.scala:242 — ScalaCli.main0 has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 4 (10 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CustomProgressBarRefreshDisplay.update (cognitive 29) · ×1
  • CustomProgressBarRefreshDisplay.update (cognitive 29) modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:55 — CustomProgressBarRefreshDisplay.update has cognitive complexity 29 (threshold 15). Drivers by points: loops 6 (17 pts), if/else 6 (11 pts), boolean chains 1 (nesting depth added 16). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Publish.buildFileSet (cognitive 28) · ×1
  • Publish.buildFileSet (cognitive 28) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:497 — Publish.buildFileSet has cognitive complexity 28 (threshold 15). Drivers by points: if/else 18 (23 pts), match/switch 3 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · CustomProgressBarRefreshDisplay.display (cognitive 28) · ×1
  • CustomProgressBarRefreshDisplay.display (cognitive 28) modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:153 — CustomProgressBarRefreshDisplay.display has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 4 (9 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · CrossSources.forInputs (cognitive 26) · ×1
  • CrossSources.forInputs (cognitive 26) modules/build/src/main/scala/scala/build/CrossSources.scala:165 — CrossSources.forInputs has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 8 (11 pts), if/else 7, boolean chains 4, loops 3 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BspClient.updatedPublishDiagnosticsParams (cognitive 26) · ×1
  • BspClient.updatedPublishDiagnosticsParams (cognitive 26) modules/build/src/main/scala/scala/build/bsp/BspClient.scala:25 — BspClient.updatedPublishDiagnosticsParams has cognitive complexity 26 (threshold 15). Drivers by points: loops 5 (20 pts), if/else 3 (6 pts) (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Inputs.forNonEmptyArgs (cognitive 26) · ×1
  • Inputs.forNonEmptyArgs (cognitive 26) modules/build/src/main/scala/scala/build/input/Inputs.scala:331 — Inputs.forNonEmptyArgs has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 6 (11 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InstallHome.runCommand (cognitive 26) · ×1
  • InstallHome.runCommand (cognitive 26) modules/cli/src/main/scala/scala/cli/commands/installhome/InstallHome.scala:69 — InstallHome.runCommand has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (26 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NativeImage.buildNativeImage (cognitive 26) · ×1
  • NativeImage.buildNativeImage (cognitive 26) modules/cli/src/main/scala/scala/cli/packaging/NativeImage.scala:83 — NativeImage.buildNativeImage has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DirectiveHandler.deriveParserImpl (cognitive 26) · ×1
  • DirectiveHandler.deriveParserImpl (cognitive 26) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:132 — DirectiveHandler.deriveParserImpl has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 14 (15 pts), if/else 8 (10 pts), boolean chains 1 (nesting depth added 3). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Fix.runCommand (cognitive 25) · ×1
  • Fix.runCommand (cognitive 25) modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala:19 — Fix.runCommand has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Publish.maybePublish (cognitive 25) · ×1
  • Publish.maybePublish (cognitive 25) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:381 — Publish.maybePublish has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (15 pts), match/switch 5 (8 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Build.scalaNativeSupported (cognitive 24) · ×1
  • Build.scalaNativeSupported (cognitive 24) modules/build/src/main/scala/scala/build/Build.scala:657 — Build.scalaNativeSupported has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PgpPush.runCommand (cognitive 24) · ×1
  • PgpPush.runCommand (cognitive 24) modules/cli/src/main/scala/scala/cli/commands/pgp/PgpPush.scala:17 — PgpPush.runCommand has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Repl.runRepl (cognitive 24) · ×1
  • Repl.runRepl (cognitive 24) modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala:284 — Repl.runRepl has cognitive complexity 24 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ExtractedDirectives.from (cognitive 23) · ×1
  • ExtractedDirectives.from (cognitive 23) modules/build/src/main/scala/scala/build/preprocessing/ExtractedDirectives.scala:25 — ExtractedDirectives.from has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BspImpl.compile (cognitive 22) · ×1
  • BspImpl.compile (cognitive 22) modules/build/src/main/scala/scala/build/bsp/BspImpl.scala:289 — BspImpl.compile has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 4 (8 pts), if/else 5 (7 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Doc.generateScaladocDirPath (cognitive 22) · ×1
  • Doc.generateScaladocDirPath (cognitive 22) modules/cli/src/main/scala/scala/cli/commands/doc/Doc.scala:229 — Doc.generateScaladocDirPath has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (21 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · BuiltInRules.migrateDirectives (cognitive 21) · ×1
  • BuiltInRules.migrateDirectives (cognitive 21) modules/cli/src/main/scala/scala/cli/commands/fix/BuiltInRules.scala:153 — BuiltInRules.migrateDirectives has cognitive complexity 21 (threshold 15). Drivers by points: loops 5 (12 pts), if/else 5, boolean chains 2, match/switch 2 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · ScalafixRules.runRules (cognitive 21) · ×1
  • ScalafixRules.runRules (cognitive 21) modules/cli/src/main/scala/scala/cli/commands/fix/ScalafixRules.scala:19 — ScalafixRules.runRules has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 2 (5 pts), match/switch 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CliLogger.printDiagnostic (cognitive 21) · ×1
  • CliLogger.printDiagnostic (cognitive 21) modules/cli/src/main/scala/scala/cli/internal/CliLogger.scala:57 — CliLogger.printDiagnostic has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (8 pts), match/switch 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BuildOptions.artifacts (cognitive 21) · ×1
  • BuildOptions.artifacts (cognitive 21) modules/options/src/main/scala/scala/build/options/BuildOptions.scala:477 — BuildOptions.artifacts has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FeaturesStickyNav.FeaturesStickyNav (cognitive 21) · ×1
  • FeaturesStickyNav.FeaturesStickyNav (cognitive 21) website/src/components/FeaturesStickyNav.tsx:35 — FeaturesStickyNav.FeaturesStickyNav has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, ternaries 4, loops 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 105, 138, 54, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · InstallStickyNav.InstallStickyNav (cognitive 21) · ×1
  • InstallStickyNav.InstallStickyNav (cognitive 21) website/src/components/InstallStickyNav.tsx:36 — InstallStickyNav.InstallStickyNav has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6, ternaries 3, loops 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 104, 137, 54, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · Fmt.runCommand (cognitive 20) · ×1
  • Fmt.runCommand (cognitive 20) modules/cli/src/main/scala/scala/cli/commands/fmt/Fmt.scala:42 — Fmt.runCommand has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · LibSodiumJni.init (cognitive 19) · ×1
  • LibSodiumJni.init (cognitive 19) modules/cli/src/main/scala/scala/cli/commands/github/LibSodiumJni.scala:97 — LibSodiumJni.init has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 4 (7 pts), boolean chains 3 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Package.runCommand (cognitive 19) · ×1
  • Package.runCommand (cognitive 19) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:81 — Package.runCommand has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 4, loops 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · RepositoryParser.repositoryOpt (cognitive 19) · ×1
  • RepositoryParser.repositoryOpt (cognitive 19) modules/cli/src/main/scala/scala/cli/commands/publish/RepositoryParser.scala:10 — RepositoryParser.repositoryOpt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · WrappedSourceItem.equals (cognitive 19) · ×1
  • WrappedSourceItem.equals (cognitive 19) modules/scala-cli-bsp/src/main/java/scala/build/bsp/WrappedSourceItem.java:73 — WrappedSourceItem.equals has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (19 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · index.SearchPageContent (cognitive 19) · ×1
  • index.SearchPageContent (cognitive 19) REDACTED:54 — index.SearchPageContent has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (10 pts), boolean chains 5, if/else 4 (nesting depth added 3). Of this number, 12 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Build.prepareBuild (cognitive 18) · ×1
  • Build.prepareBuild (cognitive 18) modules/build/src/main/scala/scala/build/Build.scala:1196 — Build.prepareBuild has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 2 (6 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ScalaCli.loadJavaProperties (cognitive 18) · ×1
  • ScalaCli.loadJavaProperties (cognitive 18) modules/cli/src/main/scala/scala/cli/ScalaCli.scala:185 — ScalaCli.loadJavaProperties has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), match/switch 3 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Package.resolvePackageType (cognitive 18) · ×1
  • Package.resolvePackageType (cognitive 18) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:1371 — Package.resolvePackageType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 3 (5 pts), loops 2 (4 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · MavenProjectDescriptor.dependencySettings (cognitive 18) · ×1
  • MavenProjectDescriptor.dependencySettings (cognitive 18) modules/cli/src/main/scala/scala/cli/exportCmd/MavenProjectDescriptor.scala:80 — MavenProjectDescriptor.dependencySettings has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ConfigDb.permsString (cognitive 18) · ×1
  • ConfigDb.permsString (cognitive 18) modules/config/src/main/scala/scala/cli/config/ConfigDb.scala:174 — ConfigDb.permsString has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · WrapperUtils.mainObjectInScript (cognitive 17) · ×1
  • WrapperUtils.mainObjectInScript (cognitive 17) modules/build/src/main/scala/scala/build/internal/WrapperUtils.scala:28 — WrapperUtils.mainObjectInScript has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, match/switch 7, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · SlothPatcher.stripSignatures (cognitive 17) · ×1
  • SlothPatcher.stripSignatures (cognitive 17) modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:369 — SlothPatcher.stripSignatures has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ScalaJsLinkerConfig.linkerCliArgs (cognitive 17) · ×1
  • ScalaJsLinkerConfig.linkerCliArgs (cognitive 17) modules/options/src/main/scala/scala/build/internal/ScalaJsLinkerConfig.scala:18 — ScalaJsLinkerConfig.linkerCliArgs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ConsoleBloopBuildClient.printFileDiagnostic (cognitive 16) · ×1
  • ConsoleBloopBuildClient.printFileDiagnostic (cognitive 16) modules/build/src/main/scala/scala/build/ConsoleBloopBuildClient.scala:160 — ConsoleBloopBuildClient.printFileDiagnostic has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (8 pts), error handling 1 (3 pts), if/else 3, boolean chains 1, match/switch 1 (nesting depth added 5). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SlothPatcher.publishCached (cognitive 16) · ×1
  • SlothPatcher.publishCached (cognitive 16) modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:562 — SlothPatcher.publishCached has cognitive complexity 16 (threshold 15). Drivers by points: error handling 3 (10 pts), if/else 3 (4 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SheBang.partitionOnShebangSection (cognitive 16) · ×1
  • SheBang.partitionOnShebangSection (cognitive 16) modules/build/src/main/scala/scala/build/preprocessing/SheBang.scala:6 — SheBang.partitionOnShebangSection has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (7 pts), if/else 5, loops 1 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Ivy.create (cognitive 16) · ×1
  • Ivy.create (cognitive 16) modules/cli/src/main/scala/scala/cli/commands/publish/Ivy.scala:87 — Ivy.create has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 1, match/switch 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · Repl.runCommand (cognitive 16) · ×1
  • Repl.runCommand (cognitive 16) modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala:70 — Repl.runCommand has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · JavaOptions.javaHomeLocationOpt (cognitive 16) · ×1
  • JavaOptions.javaHomeLocationOpt (cognitive 16) modules/options/src/main/scala/scala/build/options/JavaOptions.scala:59 — JavaOptions.javaHomeLocationOpt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, loops 2 (5 pts), boolean chains 4, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.SearchResultItem (cognitive 16) · ×1
  • index.SearchResultItem (cognitive 16) REDACTED:287 — index.SearchResultItem has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 4, if/else 2, loops 1 (2 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (64 corresponding lines) · ×1
  • Edited copy of a member (64 corresponding lines) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:219 — modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:219-282 | modules/cli/src/main/scala/scala/cli/commands/publish/PublishLocal.scala:34-104 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) modules/cli/src/main/scala/scala/cli/internal/ProfileFileUpdater.scala:28 — modules/cli/src/main/scala/scala/cli/internal/ProfileFileUpdater.scala:28-61 | modules/cli/src/main/scala/scala/cli/internal/ProfileFileUpdater.scala:67-89 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) modules/cli/src/main/scala/scala/cli/exportCmd/MillProjectDescriptor.scala:138 — modules/cli/src/main/scala/scala/cli/exportCmd/MillProjectDescriptor.scala:138-161 | modules/cli/src/main/scala/scala/cli/exportCmd/SbtProjectDescriptor.scala:280-305 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) modules/build-macros/src/main/scala/scala/build/Ops.scala:95 — modules/build-macros/src/main/scala/scala/build/Ops.scala:95-107 | modules/build-macros/src/main/scala/scala/build/Ops.scala:132-145 | modules/build-macros/src/main/scala/scala/build/Ops.scala:173-188 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) modules/cli/src/main/scala/scala/cli/commands/github/SecretCreate.scala:50 — modules/cli/src/main/scala/scala/cli/commands/github/SecretCreate.scala:50-75 | modules/cli/src/main/scala/scala/cli/commands/github/SecretList.scala:34-63 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×1
  • Edited copy of a member (11 corresponding lines) modules/build-macros/src/main/scala/scala/build/Ops.scala:50 — modules/build-macros/src/main/scala/scala/build/Ops.scala:50-60 | modules/build-macros/src/main/scala/scala/build/Ops.scala:67-78 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:22 — modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:22-41 | modules/cli/src/main/scala/scala/cli/commands/publish/checks/UserCheck.scala:22-42 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 10+ corresponding lines) modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:31 — modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:31-40 | modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:42-51 | modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:53-62 | modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:64-73 | modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:75-84 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) modules/cli/src/main/scala/scala/cli/commands/bsp/Bsp.scala:27 — modules/cli/src/main/scala/scala/cli/commands/bsp/Bsp.scala:27-33 | modules/cli/src/main/scala/scala/cli/commands/bsp/Bsp.scala:36-42 | modules/cli/src/main/scala/scala/cli/commands/bsp/Bsp.scala:44-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×1
  • Edited copy of a member (9 corresponding lines) modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:194 — modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:194-202 | modules/options/src/main/scala/scala/build/TemporaryInMemoryRepository.scala:22-30 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:44 — modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:44-53 | modules/cli/src/main/scala/scala/cli/commands/publish/checks/UserCheck.scala:45-54 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) modules/cli/src/main/scala/scala/cli/commands/pgp/PgpExternalCommand.scala:38 — modules/cli/src/main/scala/scala/cli/commands/pgp/PgpExternalCommand.scala:38-62 | modules/cli/src/main/scala/scala/cli/commands/pgp/PgpExternalCommand.scala:72-89 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) modules/cli/src/main/scala/scala/cli/exportCmd/MavenProjectDescriptor.scala:52 — modules/cli/src/main/scala/scala/cli/exportCmd/MavenProjectDescriptor.scala:52-67 | modules/cli/src/main/scala/scala/cli/exportCmd/SbtProjectDescriptor.scala:261-278 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) modules/core/src/main/scala/scala/build/internals/OsLibc.scala:89 — modules/core/src/main/scala/scala/build/internals/OsLibc.scala:89-94 | modules/options/src/main/scala/scala/build/options/BuildOptions.scala:697-702 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (20–23 lines × 2) · ×1
  • Duplicated block (20–23 lines × 2) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:405 — modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:405-427 | modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:536-555 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:536` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:309 — modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:309-323 | modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:333-347 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:309` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:884 — modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:884-897 | modules/directives/src/main/scala/scala/build/preprocessing/directives/Toolkit.scala:195-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:884` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:35 — modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:35-48 | modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:52-64 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) modules/cli/src/main/scala/scala/cli/exportCmd/MillProjectDescriptor.scala:139 — modules/cli/src/main/scala/scala/cli/exportCmd/MillProjectDescriptor.scala:139-150 | modules/cli/src/main/scala/scala/cli/exportCmd/SbtProjectDescriptor.scala:282-294 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9–12 lines × 2) · ×1
  • Duplicated block (9–12 lines × 2) modules/cli/src/main/scala/scala/cli/exportCmd/MavenProject.scala:49 — modules/cli/src/main/scala/scala/cli/exportCmd/MavenProject.scala:49-60 | modules/cli/src/main/scala/scala/cli/exportCmd/SbtProject.scala:51-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/exportCmd/MavenProject.scala:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) modules/cli/src/main/scala/scala/cli/internal/ProfileFileUpdater.scala:51 — modules/cli/src/main/scala/scala/cli/internal/ProfileFileUpdater.scala:51-61 | modules/cli/src/main/scala/scala/cli/internal/ProfileFileUpdater.scala:79-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/internal/ProfileFileUpdater.scala:51` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5–6 lines × 2) · ×1
  • Duplicated block (5–6 lines × 2) modules/build-macros/src/main/scala/scala/build/Ops.scala:134 — modules/build-macros/src/main/scala/scala/build/Ops.scala:134-139 | modules/build-macros/src/main/scala/scala/build/Ops.scala:176-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/build-macros/src/main/scala/scala/build/Ops.scala:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:65 — modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:65-70 | modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:76-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: BspServer (LCOM4 8) modules/build/src/main/scala/scala/build/bsp/BspServer.scala:19 — BspServer's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body — does nothing with its inputs modules/options/src/main/scala/scala/build/CoursierUtils.scala:9 — `noArgs` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:156 — `case NonFatal(_)` 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.
Minor — 70 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×43
  • Orphaned file modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/internal/CliLogger.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/config/src/main/scala/scala/cli/config/ConfigDb.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/commands/fmt/FmtUtil.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/options/src/main/scala/scala/build/options/ScalaNativeOptions.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/options/src/main/scala/scala/build/options/ComputeVersion.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/directives/src/main/scala/scala/build/preprocessing/directives/PublishContextual.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/options/src/main/scala/scala/build/options/JavaOptions.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/options/src/main/scala/scala/build/info/BuildInfo.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/build-macros/src/main/scala/scala/build/Ops.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/commands/CustomWindowsEnvVarUpdater.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/commands/installhome/InstallHome.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/commands/util/JvmUtils.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/ScalaCliCommands.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/internal/ProcUtil.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/cli/src/main/scala/scala/cli/commands/publish/checks/UserCheck.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/config/src/main/scala/scala/cli/config/PasswordOption.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/directives/src/main/scala/scala/build/preprocessing/directives/Platform.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/core/src/main/scala/scala/build/Position.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/core/src/main/scala/scala/build/Logger.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/runner/src/main/scala/scala/cli/runner/StackTracePrinter.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 18 more in this group — see findings.md.
M4 · Documentation accuracy · README/code drift · ×3
  • README/code drift website/docs/guides/advanced/scala-wasm.md:61 — website/docs/guides/advanced/scala-wasm.md names Node.js 24, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift website/docs/guides/advanced/scala-wasm.md:74 — website/docs/guides/advanced/scala-wasm.md names Node.js 25, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift website/docs/guides/advanced/scala-wasm.md:76 — website/docs/guides/advanced/scala-wasm.md names Node.js 23, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate website/src/components/FeaturesStickyNav.tsx:150 — `activeRect.left < tabsRect.left + 8 || activeRect.right > tabsRect.right - 8` appears character-identically in 2 files — website/src/components/FeaturesStickyNav.tsx, website/src/components/InstallStickyNav.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate website/src/components/FeaturesStickyNav.tsx:20 — `parseFloat( getComputedStyle(document.documentElement).getPropertyValue( '--ifm-navbar-height', ), ) || 64` appears character-identically in 2 files — website/src/components/FeaturesStickyNav.tsx, website/src/components/InstallStickyNav.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:446 — `notForBloop.sloth || notForBloop.slothAgent` appears character-identically in 2 files — modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala, modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Disabled test · ×2
  • Disabled test modules/integration/src/test/scala/scala/cli/integration/RunTestDefinitions.scala:462 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test modules/integration/src/test/scala/scala/cli/integration/RunTestsDefault.scala:356 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: Logger (20 abstract members) modules/core/src/main/scala/scala/build/Logger.scala:13 — `Logger` declares 20 abstract members: `error`, `message`, `log`, `log`, `debug`, `log`, `log`, `debug`, `exit`, `coursierLogger`, `bloopRifleLogger`, `scalaJsLogger`, `scalaNativeTestLogger`, `scalaNativeCliInternalLoggerOptions`, `compilerOutputStream`, `verbosity`, `experimentalWarning`, `flushExperimentalWarnings`, `deprecationWarning`, `flushDeprecationWarnings`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 20 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 33 significant file(s) lose their only recent owner: modules/options/src/main/scala/scala/build/options/ScalaVersionUtil.scala, REDACTED, modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala, modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala, modules/java-test-runner/src/main/java/scala/build/testrunner/JavaFrameworkUtils.java, modules/cli/src/main/scala/scala/cli/commands/package0/PackageOptions.scala, modules/test-runner/src/main/scala/scala/build/testrunner/FrameworkUtils.scala, modules/cli/src/main/scala/scala/cli/commands/publish/RepoParams.scala (+25 more). Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (35 single-owned of 145 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 145 of the 512 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: modules/options/src/main/scala/scala/build/options/BuildRequirements.scala, modules/cli/src/main/scala/scala/cli/commands/fix/FixOptions.scala.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found build.mill:103 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `build.mill` makes this repository a deployable product (line 103).
D21 · Naming Consistency · `isScalaCLIInstalledByInstallationScript` spells `CLI` where 55 names in the project spell it `Cli` · ×1
  • `isScalaCLIInstalledByInstallationScript` spells `CLI` where 55 names in the project spell it `Cli` modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:185 — 55 of 56 names in project repository spell the token `Cli` (55 of 56; unit: names in project repository containing `Cli`). Peers: Main.build(scalaCli) (gcbenchmark/gcbenchmark.scala:60); PersistentDiagnosticLogger.scalaNativeCliInternalLoggerOptions (modules/build/src/main/scala/scala/build/PersistentDiagnosticLogger.scala:39); scala.build.input.ScalaCliInvokeData (modules/build/src/main/scala/scala/build/input/ScalaCliInvokeData.scala:15); scala.build.input.ScalaCliInvokeData (modules/build/src/main/scala/scala/build/input/ScalaCliInvokeData.scala:29); scala.cli.ScalaCli (modules/cli/src/main/scala/scala/cli/ScalaCli.scala:23). Rename to `isScalaCliInstalledByInstallationScript`. [rule N6]
D21 · Naming Consistency · `findApplicationPathsOnPATH` spells `PATH` where 162 names in the project spell it `Path` · ×1
  • `findApplicationPathsOnPATH` spells `PATH` where 162 names in the project spell it `Path` modules/cli/src/main/scala/scala/cli/internal/ProcUtil.scala:72 — 162 of 163 names in project repository spell the token `Path` (162 of 163; unit: names in project repository containing `Path`). Peers: Bloop.bloopClassPath (modules/build/src/main/scala/scala/build/Bloop.scala:71); Bloop.bloopClassPath (modules/build/src/main/scala/scala/build/Bloop.scala:96); Bloop.bloopClassPath (modules/build/src/main/scala/scala/build/Bloop.scala:102); Successful.dependencyClassPath (modules/build/src/main/scala/scala/build/Build.scala:63); Successful.dependencyCompileClassPath (modules/build/src/main/scala/scala/build/Build.scala:64). Rename to `findApplicationPathsOnPath`. [rule N6]
D21 · Naming Consistency · `LinkJSInput` spells `JS` where 40 names in the project spell it `Js` · ×1
  • `LinkJSInput` spells `JS` where 40 names in the project spell it `Js` modules/cli/src/main/scala/scala/cli/internal/ScalaJsLinker.scala:22 — 40 of 42 names in project repository spell the token `Js` (40 of 42; unit: names in project repository containing `Js`). Peers: PersistentDiagnosticLogger.scalaJsLogger (modules/build/src/main/scala/scala/build/PersistentDiagnosticLogger.scala:37); Runner.runJs (modules/build/src/main/scala/scala/build/internal/Runner.scala:247); Runner.testJs (modules/build/src/main/scala/scala/build/internal/Runner.scala:545); Package.buildJs (modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:860); LinkingDir.getOrCreate(linkJsInput) (modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:1146). Rename to `LinkJsInput`. [rule N6]
D21 · Naming Consistency · `UnrecognizedJSRuntimeError` spells `JS` where 40 names in the project spell it `Js` · ×1
  • `UnrecognizedJSRuntimeError` spells `JS` where 40 names in the project spell it `Js` modules/core/src/main/scala/scala/build/errors/UnrecognizedJSRuntimeError.scala:3 — 40 of 42 names in project repository spell the token `Js` (40 of 42; unit: names in project repository containing `Js`). Peers: PersistentDiagnosticLogger.scalaJsLogger (modules/build/src/main/scala/scala/build/PersistentDiagnosticLogger.scala:37); Runner.runJs (modules/build/src/main/scala/scala/build/internal/Runner.scala:247); Runner.testJs (modules/build/src/main/scala/scala/build/internal/Runner.scala:545); Package.buildJs (modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:860); LinkingDir.getOrCreate(linkJsInput) (modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:1146). Rename to `UnrecognizedJsRuntimeError`. [rule N6]
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 43 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala, modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala, modules/cli/src/main/scala/scala/cli/internal/CliLogger.scala, modules/cli/src/main/scala/scala/cli/commands/fmt/FmtUtil.scala, modules/options/src/main/scala/scala/build/options/ScalaNativeOptions.scala, modules/options/src/main/scala/scala/build/options/ComputeVersion.scala, modules/directives/src/main/scala/scala/build/preprocessing/directives/PublishContextual.scala, modules/options/src/main/scala/scala/build/options/JavaOptions.scala (and 35 more) (44 orphaned of 145 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 145 of the 512 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
GD1 · Unfinished & placeholder code · Placeholder literal left in code · ×1
  • Placeholder literal left in code modules/directives/src/main/scala/scala/build/preprocessing/directives/Publish.scala:22 — A placeholder string ("//> using publish.description \"Lorem ip…") is still in shipped code — typical of generated boilerplate that was never filled in.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning · Implementation type on the public API · ×1
  • Implementation type on the public API modules/cli/src/main/java/scala/cli/commands/publish/PgpProxyMakerSubst.java:12 — 4 public types in `scala.cli.internal` are marked as implementation by their own namespace, folder or name: `PgpProxyMakerSubst` (modules/cli/src/main/java/scala/cli/commands/publish/PgpProxyMakerSubst.java:12, `internal`), `BouncycastleSignerMakerSubst` (modules/cli/src/main/java/scala/cli/internal/BouncycastleSignerMakerSubst.java:19, `internal`), `CsJniUtilsFeature` (modules/cli/src/main/java/scala/cli/internal/CsJniUtilsFeature.java:11, `internal`), `LibsodiumjniFeature` (modules/cli/src/main/java/scala/cli/internal/LibsodiumjniFeature.java:11, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
P3 · Security & performance tooling · Dependabot does not watch gitsubmodule · ×1
  • Dependabot does not watch gitsubmodule REDACTED:2 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
X5 · Nullable reference types · Scala's null is not held to the type system everywhere · ×1
  • Scala's null is not held to the type system everywhere — No build over this repository's 605 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:156 — `getSubstMappings` swallows every exception into `Map.empty` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch case or in the Scaladoc, and the row stops firing.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ab81c2c204a5403fbcf6c34632895202/history.json --exit-code 0 --source .1artifacts/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-ab81c2c204a5403fbcf6c34632895202/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .401artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .15artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 14 file(s) — `modules/cli/src/main/scala/scala/cli/commands/RestrictableCommand.scala`, `modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala`, `modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/ScalafixRules.scala`, … (+9 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1da91-346e-7f82-8f8f-546c3351acba · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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