scala-cli — Watchdog Audit

Executive summary

The system holds an adequate standing with an overall health score of 70%, indicating a workable asset that carries real operational risk. While the code is clean and the architecture is robust, the organization lacks the institutional memory to sustain it safely over time. This gap creates a fragile foundation for future delivery, where changes may introduce unexpected defects or delays due to unclear historical context.

The value at stake is significant, with nearly 50,000 lines of production code and a rebuild cost of approximately €140,000. This represents a substantial investment that requires careful stewardship. The codebase is composed entirely of complex logic with no boilerplate, meaning every line contributes directly to business function. Protecting this investment requires ensuring that new teams can understand and maintain the system without relying on tribal knowledge or extensive retraining.

The primary risk lies in Maturity, which scores only 63%. This lens measures whether a new team can pick up the work and understand the rationale behind past choices. Without documented decision records, the organization faces high costs in delay and defects as engineers waste time reverse-engineering intent or making uninformed changes. This lack of clarity exposes the business to reliability issues and slows down feature delivery, as every modification requires careful, manual verification rather than confident iteration.

Conversely, the system’s Architecture is a genuine strength, scoring 97%. The code is well-structured and modular, meaning changes are less likely to ripple unexpectedly through the system. This technical solidity provides a stable platform for growth, but it is undermined by the lack of documentation. The best leverage for improvement is to record significant decisions in a centralized, discoverable format. This single action will bridge the maturity gap, reduce onboarding time, and protect the architectural integrity, making it the highest-return investment for the leadership team.

Code Health 84% Strong Architecture 97% ★ Exemplary Maturity 63% Adequate · gated by M2 Readiness 74% Strong Security 71% Adequate · gated by D29

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Maturity 63% · 47% weightSecurity 71% · 26% weightReadiness 74% · 14% weightCode Health 84% · 8% weightArchitecture 97% · 4% weight

Raise Maturity 63 → 70 (the Healthy floor) ⇒ headline 70 → ~73.

Code composition — where the lines go

Tests 100%

New since the last scan (6+)

6 finding(s) are new versus the previous scan (2026-09-11) — surfaced by this scheduled scan itself, no pull request required.

D2 · MavenProjectDescriptor.dependencySettings (cognitive 18) modules/cli/src/main/scala/scala/cli/exportCmd/MavenProjectDescriptor.scala
D15 · Hotspot: modules/options/src/main/scala/scala/build/options/BuildOptions.scala modules/options/src/main/scala/scala/build/options/BuildOptions.scala
D15 · Hotspot: modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala
D17 · FixmeComment modules/options/src/main/scala/scala/build/Artifacts.scala
D34 · Orphaned knowledge modules/core/src/main/scala/scala/build/internals/Licenses.scala
D35 · Boundary-crossing change coupling: ScalaJsOptions.scala ↔ ScalaJsLinkerConfig.scala modules/cli/src/main/scala/scala/cli/commands/shared/ScalaJsOptions.scala

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €47,000–€230,000

Cost to rebuild	€47,000–€230,000 (0.5–1.5 person-years (776–2,462 h), ~1–2 engineers)
Domain complexity	Standard — harder problems cost more per line
Quality factor	1.0× (at 70% quality) — the last 20% of quality is most of the work
Size & shape	Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~1.0 person-years of build effort (about ~€140,000 to rebuild). Its weakest lens is Maturity at 63% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — CQRS × a 1.0× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Resolve the 1 No ADRs found finding(s) in ADR Quality.

+7.0 pts · Low effort · ADR Quality

Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

+7.2 pts · Medium effort · Architecture documentation

Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Licenses.scala.

+3.2 pts · Low effort · Knowledge Freshness

Diagnosis — what's actually going on

Value concentrated against a weak lens · Medium · Value at risk

This is a Medium asset (~1.0 person-years to rebuild), and its weakest lens is Maturity at 63%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Medium, ~1.0 person-years rebuild (48,808 LoC) · weakest lens: Maturity 63%

→ Direct remediation budget at Maturity first — highest risk-reduction per euro on an asset this size.

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form). The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

179 modules, 479 dependencies. 3 dependency cycles across 45 modules, marked above the diagonal.

Showing the 40 most-connected modules; 139 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	1 (global)	2 scala.build.options.publish	3 scala.cli.commands.github.GitHubApi	4 scala.build.compiler	5 scala.build.internals	6 scala.cli.commands.shared	7 scala.build.preprocessing	8 scala.cli.commands.util	9 scala.build.input	10 scala.cli.commands.repl	11 scala.cli.commands.run	12 scala.cli.commands.default	13 scala.cli.commands	14 scala.cli.commands.pgp	15 scala.cli.config	16 scala.cli.config.PasswordOption	17 scala.build.internal	18 scala.cli.commands.package0	19 scala.cli.commands.publish	20 scala.build.options	21 scala.build.directives	22 scala.build.preprocessing.directives	23 scala.build.errors	24 scala.build.Build	25 scala.build	27 scala.build.bsp.BspImpl	36 scala.cli.exportCmd	37 scala.cli.internal.ScalaJsLinker	38 scala.build.bsp
1 (global)
2 scala.build.options.publish
3 scala.cli.commands.github.GitHubApi
4 scala.build.compiler																				3			3		14
5 scala.build.internals																									1
6 scala.cli.commands.shared				1					3											3			3		7
7 scala.build.preprocessing						10			15							2	3			4		7	11		10
8 scala.cli.commands.util						2														1		1	3	2	2
9 scala.build.input							1													1					1
10 scala.cli.commands.repl						6		1					1							1			2	1	4
11 scala.cli.commands.run						10		1	1				2				1			1		1	1	1	1
12 scala.cli.commands.default						5			1	1	1		2												3
13 scala.cli.commands						3		1	3			1					1			1					4
14 scala.cli.commands.pgp						16		2	1				3							4			3		7
15 scala.cli.config			2										1
16 scala.cli.config.PasswordOption			4												4
17 scala.build.internal																1						1	8		5
18 scala.cli.commands.package0				1		10		1					1				1			4			2	1	3
19 scala.cli.commands.publish		2	1	2		24		1	1				5	5	4		1			3			4	1	7
20 scala.build.options		4				5				1					1		2	1	1			9	7		11
21 scala.build.directives							1						1							4			4
22 scala.build.preprocessing.directives							5						1		1	3				51	36		41		28
23 scala.build.errors																						1			6
24 scala.build.Build									3											6			1		12
25 scala.build	2				2				2							2	1			16		2	9	2
26 scala.build.actionable.ActionableDiagnostic																							2		1
27 scala.build.bsp.BspImpl																				2			1		6				2
28 scala.cli.commands.config			1			6							2	1	3					1			2		2
29 scala.cli.commands.doc						4		1					2							1			1	1	2
30 scala.cli.commands.fix				1		5	1	2	4				1			1				2		1	2		4
31 scala.cli.commands.fmt						4							1							1			1		2
32 scala.cli.commands.github			7			5							4		1								1		3
33 scala.cli.commands.publish.checks		1													1				23				11		12
34 scala.cli.commands.setupide						5			1				1							1			1		2
35 scala.cli.commands.update			1			2							2		1								1		1
36 scala.cli.exportCmd						4														7		1	5		14
37 scala.cli.internal.ScalaJsLinker																	1								1
38 scala.build.bsp				1					7											5			3	1	9	1
39 scala.cli.commands.export0						4			1				2							2			1		1		4
40 scala.cli.internal					1									1									4	1	5			1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 84% · Strong ·

The Good

D3 · Scala God Classes 9.3 D4 · Scala Code Duplication 9.8 D17 · Scala Explicit Debt 9.4

The Bad

D1 · Scala Cyclomatic Complexity 6.2 D2 · Scala Cognitive Complexity 5.3

At a glance — Architecture · 97% · Exemplary ·

The Good

D6 · Scala Cohesion (LCOM4) 9.4 D35 · Scala Change Coupling 9.9 AX10 · Repo Code composition 9.5 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0

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

The Good

D15 · Scala Churn × Complexity Hotspots 9.7 D16 · Scala Bus Factor 8.1 D19 · Scala Documentation Quality 9.3 D21 · Scala Naming Consistency 10.0 M1 · Repo Documentation (README) 8.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 8.0

The Bad

D34 · Scala Knowledge Freshness 6.8

The Ugly

D20 · Scala ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 74% · Strong ·

The Good

D12 · Scala Dependency Hygiene 9.9 D13 · Scala Secret Scanning 10.0 D14 · Scala License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 7.0 P3 · Repo Security & performance tooling 7.0 P6 · Repo Release Hygiene 10.0

The Bad

P4 · Repo Deployment & Rollback 5.0

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

The Good

D28 · Scala Secrets (history) 10.0 D30 · Scala Dependency Vulnerabilities 10.0 D43 · Scala Malicious Dependencies 10.0

The Bad

D31 · Scala IaC & Container Security 6.9 D36 · Scala Supply-chain Provenance & Signing 5.0

The Ugly

D29 · Scala Static Analysis (SAST) 0.4

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 category	Findings	Severity
A03:2021 — Injection	306	High / Critical
A05:2021 — Security Misconfiguration	15	High / Critical

Roadmap

Begin by establishing a formal record of architectural decisions in a dedicated directory to capture context and consequences. Simultaneously, update the root README to include a quick-start guide for new contributors and correct any inaccuracies regarding the Scala 3 runner. Finally, resolve orphaned knowledge items, starting with the Licenses file, to ensure all documentation remains current and accurate.

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

Do this	Helps	Effort	Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+7.0 pts	Low	ADR Quality
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).	+7.2 pts	Medium	Architecture documentation
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Licenses.scala.	+3.2 pts	Low	Knowledge Freshness
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.	+5.9 pts	Medium	Documentation (README)
Reconcile the README with reality: README omits the Scala 3 runner (SIP-46) project.	+5.9 pts	Medium	Documentation accuracy
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.	+2.9 pts	Low	Bus Factor
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness.	+2.5 pts	Low	Knowledge Freshness
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8).	+1.3 pts	Low	Static Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 139 files carrying findings, judged against the Production bar: 1% slop · 58% mixed · 41% near-clean.

File	Score	Band	Worst signal
REDACTED	1.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	3.5	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	4.1	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.6	Mixed	Cyclomatic Complexity: Config.runCommand (cyclomatic 40)
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala	6.0	Mixed	Explicit Debt: FixmeComment
modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala	6.0	Mixed	Explicit Debt: TodoComment
modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala	6.0	Mixed	Explicit Debt: FixmeComment
modules/options/src/main/scala/scala/build/Artifacts.scala	6.0	Mixed	Explicit Debt: FixmeComment

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 — 313

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 — 291

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 — 10

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

Could not be resolved — 51

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

Watchdog 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. 31 of 34 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 34 dimensions across the health lenses

D1D2D3D4D6D12D13D14D15D16D17D19D20D21D28D29D30D31D34D35D36D43AX10AX3AX5M1M2M3M4P1P2P3P4P6

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

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, 603 of 614 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.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0e993-0dcf-7bd2-a827-f30bcba44752.

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.

D5 Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog 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.
D22 Internal API Consistency — not measured this run — Watchdog 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 a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D26 Project Cohesion — not measured this run — Watchdog 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 package, a Go module, a Cargo crate, a Python, Composer, Bundler, Mix, rebar3, sbt, SwiftPM or pub package) 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.
D44 Platform End-of-Life — not measured this run — Watchdog 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, 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 (go.mod, a Gemfile's ruby directive, a REDACTED) is simply not read here yet.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX2 Stateful singletons — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
C1 Data Protection — not measured this run — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog 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 audit 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 audit controls.
C4 Data Retention — not measured this run — Watchdog 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 retention 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 retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog 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 data-subject rights 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 data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M3 Folder & project structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
P10 Library API & versioning — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads NuGet packaging and C# public API only, and no .NET project was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
PF1 Benchmark discipline — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF2 Allocation hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF3 Async & latency hygiene — not measured this run — Watchdog 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. Those languages colour their functions async, so blocking inside them is the same defect this card counts elsewhere, but their blocking vocabulary is not modelled yet. That is a gap in this analyzer's language reach — not a finding that the code is free of it.
S1 Web-Security Posture — not measured this run — Watchdog 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 web-security 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 web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X10 Duplicated predicate — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.

The LLM boundary

LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

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

32 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 48)modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460

Inputs.validateArgs (cyclomatic 42)modules/build/src/main/scala/scala/build/input/Inputs.scala:232

Config.runCommand (cyclomatic 40)REDACTED:26

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

What to do

Resolve the 1 Package.doPackage (cyclomatic 86) finding(s) in Cyclomatic Complexity — start with Package.scala. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Publish.prepareFilesAndUpload (cyclomatic 60) finding(s) in Cyclomatic Complexity — start with Publish.scala. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Run.runOnce (cyclomatic 48) finding(s) in Cyclomatic Complexity — start with Run.scala. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity5.3 / 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.3 / 10 · rule-coverage 100% · ceiling Prevented

59 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

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

What to do

Resolve the 1 Config.runCommand (cognitive 154) finding(s) in Cognitive Complexity — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Package.doPackage (cognitive 113) finding(s) in Cognitive Complexity — start with Package.scala. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Publish.prepareFilesAndUpload (cognitive 100) finding(s) in Cognitive Complexity — start with Publish.scala. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes9.3 / 10Stronggated by 11 serious findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Prevented

11 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

MethodTooLong: Artifacts.apply · ×4modules/options/src/main/scala/scala/build/Artifacts.scala:197

What to do

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).
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).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.8 / 10Stronggated by 23 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

23 duplicated block group(s) detected. 3 of the 23 are in trees this repository does not ship — vendored, example/demo, 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 (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

Duplicated block (9 lines × 2) · ×2modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:175

Duplicated block (8 lines × 2) · ×2modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:150

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

What to do

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).
Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with PgpPull.scala, AsmTestRunner.scala. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with BloopExit.scala, New.scala. — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D12 · Dependency Hygiene9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

1 outdated direct production npm dependency(ies) of 19 graded, 0 pinning defect(s), across 1 package.json (0 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded: this dimension grades what SHIPS. Whether any of these packages is DEPRECATED or UNMAINTAINED is not graded — registry.npmjs.org's latest-version answer carries neither, and release age does not stand in for a maintenance status. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Outdated (npm): sass

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 19 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 19 production dependency(ies) this repository's committed lockfile resolves, across 0 product package.json manifest(s). Its 0 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.7 / 10Stronggated by 8 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.7 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala (5×86=430); modules/cli/src/main/scala/scala/cli/commands/run/Run.scala (3×48=144); modules/options/src/main/scala/scala/build/Artifacts.scala (3×35=105)

Hotspot: modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala · ×8modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268

What to do

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

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

Do you agree with this assessment?

D16 · Bus Factor8.1 / 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 8.1 / 10 · rule-coverage 100% · ceiling Documented

27 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 144 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

What to do

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

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

Do you agree with this assessment?

D17 · Explicit Debt9.4 / 10Stronggated by 142 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.4 / 10 · rule-coverage 100% · ceiling Prevented

142 deducted task-comment markers across 48808 LoC (0.3/KLoC) → score 9.4. 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 · ×81modules/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala:69

FixmeComment · ×61modules/cli/src/main/scala/scala/cli/ScalaCliCommands.scala:86

What to do

Resolve the 81 TodoComment finding(s) in Explicit Debt — start with SbtProjectDescriptor.scala (9), RunWithWatchTestDefinitions.scala (6), MavenProjectDescriptor.scala (4). — One of this dimension's main actionable groups (81 warning-level).
Resolve the 61 FixmeComment finding(s) in Explicit Debt — start with CustomWindowsEnvVarUpdater.scala (3), NativePackagerTests.scala (3), ScalaCliCommands.scala (2). — One of this dimension's main actionable groups (61 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README and its subdirectories document the project as a whole (root README plus scala-cli/README.md, agentskills/, gcbenchmark/, gifs/, website/) with an overview of what Scala CLI is and where to find further documentation. The root README also links out to the contributing guide, developer docs, app internals, release procedure, and code of conduct, covering all four contributor-related sections. The architecture/design docs (88 markdown files) are well-organized and describe the project's structure, while the website/README documents a static site built with Docusaurus 2, complete with installation, local development, build, and deployment commands. The documentation is excellent for a CLI tool: each command has an overview (installing completions, getting config, dumping config, creating PGP keys), examples with exact quoted commands, and cross-building notes. The 'Fix' and 'Format' docs are long but complete; the READMEs cover all sub-commands and give usage examples. There is no missing installation/usage section for a root-level document (the only missing one would be an overview of what the project does), so it is judged against its own directory.

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

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

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

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

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.

Do you agree with this assessment?

D29 · Static Analysis (SAST)0.4 / 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.4 / 10 · rule-coverage 100% · ceiling Documented

306 finding(s): 0 critical, 304 high, 0 medium, 2 low. 286 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 14 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`, … (+9 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 2 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

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

What to do

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

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

Do you agree with this assessment?

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/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, Go, Java and Kotlin via Maven/Gradle, 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.

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.

Do you agree with this assessment?

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

What to do

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).
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).
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.

Do you agree with this assessment?

D34 · Knowledge Freshness6.8 / 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 6.8 / 10 · rule-coverage 100% · ceiling Documented

46 of 144 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 144 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

Further orphaned files (smaller)

What to do

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).
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.

Do you agree with this assessment?

D35 · Change Coupling9.9 / 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.9 / 10 · rule-coverage 100% · ceiling Documented

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

Boundary-crossing change coupling: ScalaJsOptions.scala ↔ ScalaJsLinkerConfig.scalamodules/cli/src/main/scala/scala/cli/commands/shared/ScalaJsOptions.scala

Change coupling: RestrictedCommandsParser.scala ↔ ScalaCommand.scala · ×4modules/cli/src/main/scala/scala/cli/commands/RestrictedCommandsParser.scala

What to do

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).
Resolve the 4 Change coupling finding(s) in Change Coupling — start with DependencyUpdate.scala (2), RestrictedCommandsParser.scala, REDACTED. — One of this dimension's main actionable groups (4 warning-level).

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

Do you agree with this assessment?

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

What to do

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

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

Do you agree with this assessment?

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. Scored 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. SCORED, not informational.

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.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.5 / 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.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

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.

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

M1 · Documentation (README)8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.

Do you agree with this assessment?

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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

Do you agree with this assessment?

M4 · Documentation accuracy8.0 / 10Strong◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

README omits the Scala 3 runner (SIP-46) project — reported by the model that read the README against this repository; no term search was run for this one, so nothing here has been checked against the tree. Treat it as a reading to confirm, not as a measured contradiction: verify it against the code before acting on it, and if the footprint it describes does exist, this row is wrong.

What to do

Reconcile the README with reality: README omits the Scala 3 runner (SIP-46) project.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

What to do

Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Lens	Score	Rating	Impact
Code Health	84%	Strong	Solid.
Architecture	97%	Exemplary	Strongest area.
Maturity	63%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	74%	Strong	Solid.
Security	71%	Adequate — gated by D29	Capped at Fair by a Critical contributor — resolve it before relying on this lens.

Not evidenced — 4 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.

C3 Audit Trail — Not assessed: these audit 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 audit 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.
C4 Data Retention — Not assessed: these retention 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 retention 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.
C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 83 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.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~41316 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
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. 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 measured no build unit over this repository's .java, .js, .scala source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D5 Coupling — D5 reads a .NET project-reference graph only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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
D9 Test Distribution — Test source is 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 275 value object(s)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 CQRS handler(s))
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P10 Library API & versioning — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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 — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
PF2 Allocation hygiene — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
PF3 Async & latency hygiene — Sync-over-async was not assessed: this repository's async code is written in Scala, whose blocking calls this check does not model yet. That is a gap in the analyzer's language reach, not a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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 — 313 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
+ 261 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
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 — 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 — `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 64% of the time (7 of the 11 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 7 shared commits counted here, the most recent 3 are `bbe65037` refactor how ES version is validated (#4484); `53cd950d` Support newer `esVersion` strings; hard error on unkwnown `esVersion`…; `72c23a54` Add a `--js-emit-wasm` option and a corresponding `using` directive (… — run `git show` on any of them.

Serious — 291 finding(s)

D17 · Explicit Debt · TodoComment · ×81

TodoComment modules/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala:69 — // TODO Manage to have case-app give use the exact command name that was used instead — 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:158 — // 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/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/fmt/Fmt.scala:51 — // TODO If no input is given, just pass '.' to scalafmt? — 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/package0/Package.scala:299 — // TODO When possible, call alreadyExistsCheck() before compiling stuff — 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/package0/Package.scala:433 — // TODO: the coursier bootstrap launcher (Bootstrap.java in coursier-launcher) — 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/package0/Package.scala:909 — // TODO Generate that in memory — 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/packaging/Spark.scala:29 — // TODO Add more for Hadoop 2, maybe for 3 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/cli/src/main/scala/scala/cli/commands/pgp/PgpCommand.scala:29 — // TODO add handling for scala-cli-signing — 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/pgp/PgpCommand.scala:32 — // TODO add handling for scala-cli-signing — 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/pgp/PgpCommand.scala:34 — // TODO add handling for scala-cli-signing — 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/publish/Publish.scala:755 — // TODO version listings, … — 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/publish/Ivy.scala:95 — // TODO Accept full-fledged coursier.Dependency — 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/shared/SharedOptions.scala:843 — // TODO: remove this state after resolving https://github.com/VirtusLab/scala-cli/issues/2658
TodoComment modules/cli/src/main/scala/scala/cli/commands/shared/ScalaNativeOptions.scala:51 — //TODO does it even work when we default it to true while handling? — 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/shared/ScalaNativeOptions.scala:72 — //TODO does it even work when we default it to true while handling? — 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/shared/MarkdownOptions.scala:14 — // TODO: add a separate scope for Markdown and remove this option once it's stable — 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/exportCmd/SbtProjectDescriptor.scala:80 — // TODO options.dom — 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/exportCmd/SbtProjectDescriptor.scala:144 — // TODO repo.authentication? — 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/exportCmd/SbtProjectDescriptor.scala:148 — // TODO repo.authentication? — 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/exportCmd/MillProjectDescriptor.scala:100 — // TODO repo.authentication? — 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/exportCmd/SbtProjectDescriptor.scala:145 — // TODO repo.metadataPatternOpt — 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/exportCmd/SbtProjectDescriptor.scala:293 — // TODO: handle multiple frameworks 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.
TodoComment modules/cli/src/main/scala/scala/cli/exportCmd/MillProjectDescriptor.scala:149 — // TODO: handle multiple frameworks 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.
TodoComment modules/cli/src/main/scala/scala/cli/exportCmd/SbtProjectDescriptor.scala:315 — // TODO dep.userParams — 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.
+ 56 more in this group — see findings.md.

D17 · Explicit Debt · FixmeComment · ×61

FixmeComment modules/cli/src/main/scala/scala/cli/ScalaCliCommands.scala:86 — // FIXME Report this in case-app default NameFormatter — 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/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala:112 — // FIXME Report this in case-app default NameFormatter — 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/cli/src/main/scala/scala/cli/ScalaCliCommands.scala:104 — // FIXME Charset? — 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/cli/src/main/scala/scala/cli/ScalaCli.scala:88 — // FIXME Print t.getSuppressed 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/cli/src/main/scala/scala/cli/commands/CustomWindowsEnvVarUpdater.scala:18 — // FIXME Should be coursier.paths.Util.useJni(), but it's not available from 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/cli/src/main/scala/scala/cli/commands/CustomWindowsEnvVarUpdater.scala:131 — // FIXME value might need some escaping 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/cli/src/main/scala/scala/cli/commands/CustomWindowsEnvVarUpdater.scala:135 — // FIXME value might need some escaping 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/cli/src/main/scala/scala/cli/commands/bloop/Bloop.scala:24 — // FIXME Basically a tweaked copy of SharedOptions.bloopRifleConfig — 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/cli/src/main/scala/scala/cli/commands/bloop/Bloop.scala:78 — // FIXME Give more details? — 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/cli/src/main/scala/scala/cli/commands/bsp/BspOptions.scala:12 — // FIXME There might be too many options in SharedOptions for the bsp 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.
FixmeComment modules/cli/src/main/scala/scala/cli/commands/export0/ExportOptions.scala:17 — // FIXME There might be too many options for 'scala-cli export' there — 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/cli/src/main/scala/scala/cli/commands/export0/Export.scala:69 — // FIXME Auto-update those — 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/cli/src/main/scala/scala/cli/commands/github/SecretList.scala:52 — // FIXME Paging — 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/cli/src/main/scala/scala/cli/commands/github/SecretList.scala:80 — // FIXME Paging — 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/cli/src/main/scala/scala/cli/commands/github/LibSodiumJni.scala:52 — // FIXME Could this change? — 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/cli/src/main/scala/scala/cli/commands/github/LibSodiumJni.scala:56 — // FIXME These suffixes seem to be hashes, and seem to change at every version… — 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/cli/src/main/scala/scala/cli/commands/package0/Package.scala:85 — // FIXME mainClass encoding has issues with special chars, such as '-' — 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/cli/src/main/scala/scala/cli/commands/package0/Package.scala:1188 — // FIXME Allow users to use another JVM 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/cli/src/main/scala/scala/cli/commands/packaging/Spark.scala:8 — // FIXME Add more? — 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/cli/src/main/scala/scala/cli/commands/pgp/PgpCommand.scala:21 — // FIXME Should be the actual name that was called from the command line — 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/cli/src/main/scala/scala/cli/commands/publish/RepoParams.scala:186 — // FIXME Get via logger — 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/cli/src/main/scala/scala/cli/commands/publish/PublishUtils.scala:188 — // FIXME Allow full cross 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/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:262 — // FIXME Get from dest if it exists? — 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/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:300 — // FIXME Accept more extensions? — 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/cli/src/main/scala/scala/cli/commands/publish/checks/DeveloperCheck.scala:26 — // FIXME No headOption, add all of options.publishParams.developer values… — 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.
+ 36 more in this group — see findings.md.

D15 · Churn × Complexity Hotspots · Hotspot · ×8

Hotspot: modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268 — modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 86 in Package.doPackage at line 268. 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 15:17:33 +02:00' --until='2026-09-28 15:17:33 +02:00' --full-history --no-merges -- modules/cli/src/main/scala/scala/cli/commands/package0/Package.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/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 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 15:17:33 +02:00' --until='2026-09-28 15:17:33 +02: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/Artifacts.scala modules/options/src/main/scala/scala/build/Artifacts.scala:197 — modules/options/src/main/scala/scala/build/Artifacts.scala changed 3 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 15:17:33 +02:00' --until='2026-09-28 15:17:33 +02: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/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:363 — modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SharedOptions.buildOptions at line 363. 1 of those changes was a fix/bug commit, and the other 5 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 15:17:33 +02:00' --until='2026-09-28 15:17:33 +02:00' --full-history --no-merges -- modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.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:352 — modules/options/src/main/scala/scala/build/options/BuildOptions.scala changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in BuildOptions.computeScalaParams at line 352. 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 15:17:33 +02:00' --until='2026-09-28 15:17:33 +02: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/cli/src/main/scala/scala/cli/commands/publish/Publish.scala modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:497 — modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in Publish.buildFileSet at line 497. 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 15:17:33 +02:00' --until='2026-09-28 15:17:33 +02:00' --full-history --no-merges -- modules/cli/src/main/scala/scala/cli/commands/publish/Publish.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 3 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 15:17:33 +02:00' --until='2026-09-28 15:17:33 +02: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/repl/Repl.scala modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala:284 — modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Repl.runRepl at line 284. 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 15:17:33 +02:00' --until='2026-09-28 15:17:33 +02:00' --full-history --no-merges -- modules/cli/src/main/scala/scala/cli/commands/repl/Repl.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 · FileTooLong · ×7

FileTooLong: package0/Package.scala modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala — FileTooLong — 1106 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 606 over it, 2.21× 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 — 760 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 260 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 — 732 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 232 over it, 1.46× 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 — 560 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 60 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 — 549 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 49 over it, 1.10× 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

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 292 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 192 over it, 2.92× 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.

D35 · Change Coupling · Change coupling · ×4

Change coupling: RestrictedCommandsParser.scala ↔ ScalaCommand.scala modules/cli/src/main/scala/scala/cli/commands/RestrictedCommandsParser.scala — `modules/cli/src/main/scala/scala/cli/commands/RestrictedCommandsParser.scala` and `modules/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala` change together 62% of the time (8 of the 13 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 ↔ Export.scala modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala — `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: DependencyUpdate.scala ↔ SetupIde.scala modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala — `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 — `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.

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.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2

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/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 · Duplicated block (7 lines × 2) · ×2

Duplicated block (7 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:325 — modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:325-331 | modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:347-353 — 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/checks/PgpSecretKeyCheck.scala:325` 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 (7 lines × 2) modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:196 — modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:196-202 | modules/options/src/main/scala/scala/build/TemporaryInMemoryRepository.scala:24-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. Read the line range as the matched WINDOW rather than a finished unit: at `modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:196` 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.

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 48) · ×1

Run.runOnce (cyclomatic 48) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460 — Run.runOnce has cyclomatic complexity 48 (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 42) · ×1

Inputs.validateArgs (cyclomatic 42) modules/build/src/main/scala/scala/build/input/Inputs.scala:232 — Inputs.validateArgs has cyclomatic complexity 42 (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 37) · ×1

BuildOptions.computeScalaParams (cyclomatic 37) modules/options/src/main/scala/scala/build/options/BuildOptions.scala:352 — BuildOptions.computeScalaParams has cyclomatic complexity 37 (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:124 — 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:238 — 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 · Build.watch (cyclomatic 19) · ×1

Build.watch (cyclomatic 19) modules/build/src/main/scala/scala/build/Build.scala:771 — 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:996 — 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:347 — 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:329 — 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 · Build.scalaNativeSupported (cyclomatic 16) · ×1

Build.scalaNativeSupported (cyclomatic 16) modules/build/src/main/scala/scala/build/Build.scala:627 — 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:363 — 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.

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:124 — 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 56) · ×1

Inputs.validateArgs (cognitive 56) modules/build/src/main/scala/scala/build/input/Inputs.scala:232 — Inputs.validateArgs has cognitive complexity 56 (threshold 15). Drivers by points: if/else 33 (39 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:996 — 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:771 — 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:347 — 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:238 — 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:329 — 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 · 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:627 — 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 · Fix.runCommand (cognitive 24) · ×1

Fix.runCommand (cognitive 24) modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala:19 — Fix.runCommand has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (22 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 · 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:288 — 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:65 — 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:481 — 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 · 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 · 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 · ScalaCli.loadJavaProperties (cognitive 18) · ×1

ScalaCli.loadJavaProperties (cognitive 18) modules/cli/src/main/scala/scala/cli/ScalaCli.scala:181 — 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:1352 — 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 · Build.prepareBuild (cognitive 17) · ×1

Build.prepareBuild (cognitive 17) modules/build/src/main/scala/scala/build/Build.scala:1166 — Build.prepareBuild has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 2 (6 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 · 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 · 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:61 — 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.

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 · Duplicated block (23–27 lines × 2) · ×1

Duplicated block (23–27 lines × 2) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:302 — modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:302-324 | modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:327-353 — 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/package0/Package.scala:302` 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 (24 lines × 2) · ×1

Duplicated block (24 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:101 — modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:101-124 | modules/cli/src/main/scala/scala/cli/commands/publish/checks/UserCheck.scala:101-124 — 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:101` 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 (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:308 — modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:308-322 | modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:332-346 — 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:308` 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:881 — modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:881-894 | 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:881` 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 (5 lines × 2) · ×1

Duplicated block (5 lines × 2) modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:66 — modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:66-70 | modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:77-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:66` 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.

Minor — 9 finding(s)

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 27 significant file(s) lose their only recent owner: REDACTED, modules/options/src/main/scala/scala/build/options/ScalaVersionUtil.scala, modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala, modules/java-test-runner/src/main/java/scala/build/testrunner/JavaFrameworkUtils.java, modules/test-runner/src/main/scala/scala/build/testrunner/FrameworkUtils.scala, modules/cli/src/main/scala/scala/cli/commands/package0/PackageOptions.scala, modules/cli/src/main/scala/scala/cli/commands/publish/RepoParams.scala, modules/cli/src/main/scala/scala/cli/commands/shared/ScalacOptions.scala (+19 more). Pair on, review, or document these before any departure.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — 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/`.

D31 · IaC & Container Security · Low IaC · ×1

REDACTED

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 45 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/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, modules/options/src/main/scala/scala/build/info/BuildInfo.scala (and 37 more) (46 orphaned of 144 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 144 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

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.

M4 · Documentation accuracy · README/code drift · ×1

README/code drift — README omits the Scala 3 runner (SIP-46) project — reported by the model that read the README against this repository; no term search was run for this one, so nothing here has been checked against the tree. Treat it as a reading to confirm, not as a measured contradiction: verify it against the code before acting on it, and if the footprint it describes does exist, this row is wrong.

Minor — 1 finding(s)

D12 · Dependency Hygiene · Outdated (npm) · ×1

Outdated (npm): sass — sass is pinned at 1.104.1; registry.npmjs.org publishes 1.105.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-64b074d414f94e62ac52bfc824e4e77a/history.json --exit-code 0 --source .	1	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-64b074d414f94e62ac52bfc824e4e77a/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	306	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	15	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a0e993-0dcf-7bd2-a827-f30bcba44752 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

VirtusLab/scala-Cli

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency matrix

At a glance — Code Health · 84% · Strong ·

At a glance — Architecture · 97% · Exemplary ·

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

At a glance — Readiness · 74% · Strong ·

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

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts